Tiny Core Linux
Tiny Core Extensions => TCE Corepure64 => Topic started by: tinycorelinux on November 22, 2020, 02:19:39 AM
-
I found that neither Chromium-Browser nor chromium-based browsers could enable hardware acceleration mode, and there were a lot of error messages on the terminal.
I haven't found this problem with Firefox yet (maybe I just don't know), but I just don't like using Firefox.
[12026:12026:1122/102351.873626:ERROR:browser_dm_token_storage_linux.cc(94)] Error: /etc/machine-id contains 0 characters (32 were expected).
Fontconfig error: Cannot load default config file: No such file: (null)
[12026:12042:1122/102351.975736:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[12055:12055:1122/102352.127785:ERROR:angle_platform_impl.cc(43)] Display.cpp:805 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
[12055:12055:1122/102352.127972:ERROR:gl_surface_egl.cc(773)] EGL Driver message (Critical) eglInitialize: GLX is not present.
[12055:12055:1122/102352.128029:ERROR:gl_surface_egl.cc(1322)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[12055:12055:1122/102352.128152:ERROR:angle_platform_impl.cc(43)] Display.cpp:805 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
[12055:12055:1122/102352.128240:ERROR:gl_surface_egl.cc(773)] EGL Driver message (Critical) eglInitialize: GLX is not present.
[12055:12055:1122/102352.128295:ERROR:gl_surface_egl.cc(1322)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[12055:12055:1122/102352.128348:ERROR:gl_initializer_linux_x11.cc(160)] GLSurfaceEGL::InitializeOneOff failed.
[12055:12055:1122/102352.143616:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
...... ......
The following error message is repeated throughout the browser. What's wrong with it? I merged the duplicate information
[13685:13778:1122/103337.926470:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[13721:13735:1122/103400.039014:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -101
(xxx:13685): Gdk-WARNING **: 10:34:03.112: gdk_window_set_user_time called on non-toplevel
...... ......
-
[12026:12026:1122/102351.873626:ERROR:browser_dm_token_storage_linux.cc(94)] Error: /etc/machine-id contains 0 characters (32 were expected). You could symlink /etc/machine-id -> /var/lib/dbus/machine-id
Fontconfig error: Cannot load default config file: No such file: (null) Is there a symlink present such that /etc/fonts -> /usr/local/etc/fonts?
Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory This indicates that the dbus daemon has not been started.
[12055:12055:1122/102352.128029:ERROR:gl_surface_egl.cc(1322)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
Is graphics-KERNEL loaded and Xorg-7.7-3d running?
-
Is graphics-KERNEL loaded and Xorg-7.7-3d running?
Yes. but now, as soon as hardware acceleration is enabled, the browser will have a flat screen, nothing to see, and nothing to use.
-
Hello,
Does that simply mean they are ineffectively functioning..?...Iridium and such like on Tcl 64?
(they are not correctly using the hardware?)
i did ask about graphics hardware earlier (Tcl drivers and why Xorg etc) but there hasn't been any reply.....(it was regarding Radeon or Intel drivers)
dam
v
-
(they are not correctly using the hardware?)
There should be no problem with my hardware and driver, but the browser's GPU acceleration function is not normal.
i did ask about graphics hardware earlier (Tcl drivers and why Xorg etc) but there hasn't been any reply.....(it was regarding Radeon or Intel drivers)
Have you solved your problem now?
-
After a few attempts to debug the browser, the display still seems to be a problem.
-
This indicates that the dbus daemon has not been started.
It seems that dbus still cannot be started.
cd /usr/local/chromium-browser/chrome
dbus-run-session ./chrome
[19254:19270:1122/144934.533238:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[19254:19290:1122/144934.739940:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
(chrome:19254): Gdk-WARNING **: 14:49:36.896: gdk_window_set_user_time called on non-toplevel
[19285:19300:1122/145015.376721:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -101
-
Boot to a console prompt and then:
$ tce-load -i graphics-KERNEL Xorg-7.7-3d alsa-config flwm aterm wbar
$ sudo /usr/local/etc/init.d/dbus start
$ sudo ln -s /var/lib/dbus/machine-id /etc/machine-id
$ sudo ln -s /usr/local/etc/fonts /etc/fonts
$ sudo ln -s /usr/local/etc/ssl /etc/ssl
$ startx
..and then try the browser.
-
ONE,
well my forum question about graphics drives on tcl was not so much of a problem....but i just wondered how your hardware knows that's it's got the best TCL drivers from the repo for it.
there are lots of repo files concerning graphics frimware and drivers......radeon and intel and vulkan and wayland and weston....never mind frame buffer which is what TCL 64 uses by default.
i realize that a user loads Xorg for 3d performance and accelerations in graphics etc..........should a user LOAD IT or not?....... and does tcl know to also grab the specific Intel drivers it lists for my chip ontop of Xorg drivers?
thx
vin...
i imagine some of this stuff above may pertain to that Chromium GPU issue you mention....i would likely also suffer that issue too...... and so will all users
-
I get this:
$ dbus-run-session chromium-browser
Fontconfig warning: "/etc/fonts/fonts.conf", line 5: unknown element "its:rules"
...
[30175:30219:1122/195830.919703:ERROR:object_proxy.cc(626)] Failed to call method: org.freedesktop.Notifications.GetCapabilities: object_path= /org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files
[30225:30225:1122/195830.999801:ERROR:sandbox_linux.cc(375)] InitializeSandbox() called with multiple threads in process gpu-process
..but the browser works as expected.
-
how your hardware knows that's it's got the best TCL drivers from the repo for it.
First of all, the hardware itself does not have the ability to automatically get the drivers from the repo.
Most of the drivers in addition to the built-in drivers of the kernel, you need to get them yourself.
The repository only provides common drivers (usually from hardware vendors), and some closed-source drivers require you to download them from a third party and then compile them yourself.Of course there are some newer hardware or older hardware that Linux generally doesn't support, so you'll have to figure it out yourself.
should a user LOAD IT or not?....... and does tcl know to also grab the specific Intel drivers it lists for my chip ontop of Xorg drivers?
It depends on your needs.
-
..but the browser works as expected.
Ok, I'll try again tomorrow.
-
..and does tcl know to also grab the specific Intel drivers it lists for my chip ontop of Xorg drivers?
What specific intel drivers are you speaking of?
-
juanto,
the specific drivers are radeon based ones in the repo and they cover the model issue number of my graphics chip ....
(1)firmware-radeon.tcz
(2)firmware-video.tcz (what is that & how?)
(3)firmware-amdgpu.tcz (what is that & how?)
(4)firmware-amd-ucode.tcz (what is that and how?)
(5)xf86-video-amdgpu.tcz (what is that and how?)
i think the description page about (1) above mentions chip models which match my graphics chip model number
i think i tried loading (1) above after Xorg was loaded....... but the screen went black and the os crashed.
thx
V
Amd Radeon hd 7570M graphics...........THAMES PRO edition chip......
(As in the river "Thames" London UK........... where the chip may have been co-developed .........along with Santa Clara's Amd)
-
..and then try the browser.
[11573:11611:1123/022500.550408:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[11604:11604:1123/022500.632294:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[11573:11665:1123/022500.808031:ERROR:object_proxy.cc(621)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
(chrome:11573): Gdk-WARNING **: 02:25:07.933: gdk_window_set_user_time called on non-toplevel
[11608:11615:1123/022511.409364:ERROR:ssl_client_socket_impl.cc(960)] handshake failed; returned -1, SSL error code 1, net_error -101
-
The main problem is as shown in the figure: address bar, menu bar, right-click menu can not be
displayed normally, are black, nothing can be seen.
-
I'd guess that some local customisation you've done is causing this - see attached
-
I'd guess that some local customisation you've done is causing this - see attached
Yes, the last two screenshots you see show the effect after I did some configuration on the browser, while the first two screenshots show the effect without any configuration on the browser, which is simply unusable.
my guess is that my graphics card doesn't support Chrome's GPU acceleration mode. As far as I know, Chrome has removed most graphics support, and only the graphics card models listed in Chrome are fully GPU accelerated.
However, GPU acceleration is very important for me in Linux, especially in Chrome. I found that with GPU acceleration enabled, web pages opened and loaded so fast that I could hardly believe my eyes. Moreover, the CPU load was so low that the CPU indicator light almost went out.
-
We both get the same message:
InitializeSandbox() called with multiple threads in process gpu-process..so I'm not sure that the gpu is the problem.
-
..so I'm not sure that the gpu is the problem.
hmm...Does your browser work properly with GPU acceleration enabled?
-
I find that almost everyone on the web has only one answer to chrome GPU acceleration problems, and that's to tell you to turn it off...
If it can't be solved, I have to give up. You have tried your best.
Thank you , Juanito.
-
hello,
well judging by what you say, in chromium & derivatives at least, the GPU acceleration (if possible) makes a huge difference to browsing.
Is this type of difference (good performance) reflected in other browsers where they see the machines GPU correctly?.... like say FF........?
or what browsers realy shine in this area?.....MsoftEdge?
thx
V
i was messing around with browsers on an old Msoft machine here...... (winXP sp2).
The latest version of a certain browser just would not run, .........so after rooting around in their forum, there was a final trick to patch an sp3 version of "kernnel32.dll" file into the OS instead of it's sp2 version.
I did the patch and the browser works fine on a 20 year old laptop....it surfs all todays modern web sites pretty good.........youtube etc....facebook...
(Goanna engine) kmeleon76.
i also had to patch the browser itself with 2 DLL files for doing html5 viideo and they are lean-trimnmed DLL's for sp2....(it works)
i will run this same browser on the same machine under TCL and WINE .......and it should work fine.
This machine only has an SSE cpu chip and only supports FF 45 from TCL.....which isn't that great of a browser on performance here......................compared to KMeleon under wine and the same hardware
-
....could there be a flag that you need to set in the CHromium browser?
chrome://flags (into the address bar)
There are lots of flags to set on Chromium concerning GPU's
thx
V
-
Here's what I see from chrome://gpu/
Graphics Feature Status
Canvas: Hardware accelerated
CheckerImaging: Enabled
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only. Hardware acceleration disabled
Video Decode: Unavailable
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
...
Problems Detected
Accelerated video decode is unavailable on Linux: 137247
Disabled Features: accelerated_video_decode
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
...
Chrome version Chrome/66.0.3343.0
Operating system Linux 5.4.3-tinycore64
GPU0 VENDOR = 0x8086, DEVICE= 0x0a16 *ACTIVE*
...
GL_RENDERER Mesa DRI Intel(R) Haswell Mobile
..apparently chromium-browser needs to be patched for va-api (accelerated video decode) to work.
-
..apparently chromium-browser needs to be patched for va-api (accelerated video decode) to work.
Are you saying that this may be related to a problem I have?
-
I don't know - you'd need intel graphics hardware for intel-vaapi-driver to work anyway - what do you get for chrome://gpu?
-
I get this in firefox:
GPU #1
Active: Yes
Description: Mesa DRI Intel(R) Haswell Mobile x86/MMX/SSE2
Vendor ID: 0x8086
Device ID: 0x0a16
Driver Vendor: mesa/i965
Driver Version: 19.2.3.0
RAM: 1536
..which suggests the problem is with chromium-browser
-
which suggests the problem is with chromium-browser
All right -_-||
-
It seems you are well on the way to nailing down the issue concerning Chromium browser on Linux....
(at least)
so is it saying that accelerated video decode is a problem in ANY graphics chips set ...e.g. (amd or intel set)?
i wonder *how* one is suppossed to actually patch chromium--on--Linux to get accelerated video decode...... then?
wonder if accelerated vid decode (chromium) is okay on other platforms?( no names mentioned)?
---
---
unrelated stuff below
------------------------------------
On Intel GPUs MSAA performance is not acceptable for GPU rasterization: 527565
Native GpuMemoryBuffers have been disabled, either via about:flags or command line.
-----------------------------------
those lines above could mean that dev's just don't find it acceptable regarding MSAA but users could enable the flags if they wished....just to see and perhaps gain some ground. (about:flags )written into address bar
thx
V
-
Hi vinceASPECT
wonder if accelerated vid decode (chromium) is okay on other platforms?( no names mentioned)?
We have a lot of Chrome based browsers in Mainland China, but they only support Windows platforms. As far as I know, these browsers turn off GPU acceleration by default, so I don't know if they will have the same problem at first, but they do perform very well.
I feel the browser's performance is not only the GPU, because behind the GPU is video card drive and graphics library, both on different operating systems have different implementation,different performance, such as in Windows is the main use of graphics library Direct3D, and under Linux using OPENGL, the difference is largely determines the rendering performance of the browser.
I may not be able to say this much, but I just want to say that browser performance is not a one-way decision. There are many factors, and I only try various ways to improve my performance based on the resources I have, such as GPU acceleration, which we are discussing here.
-
so how do you plan to get "advanced video decoding" working on chromium
Linux?
V
-
I've now tried firefox and chromium-browser on x11 and wayland.
firefox
gpu acceleration seems to work
va-api acceleration does not work (apparently it will work in wayland with the latest firefox/libva)
chromium-browser
gpu acceleration might be working partially
va-api acceleration does not work (apparently there is a patch available)
-
firefox
gpu acceleration seems to work
chromium-browser
gpu acceleration might be working partially
Well, there should be no problem when Firefox is enabled with GPU acceleration.
After chrome/ Chromium is enabled with GPU acceleration, it needs to do some proper configuration.
it can display web pages normally with good performance, which indicates that GPU acceleration is successful...
The only GTK controls used by Chrome that don't display properly, such as the entire area of the address bar, right-click menus, etc., are still able to handle user events, which is a bit of a surprise.
-
(a) After chrome/ Chromium is enabled with GPU acceleration, it needs to do some proper configuration......
(b) and there is a patch for va-api acceleration in Chromium Linux.
......so what must a typical Linux user actually need to DO to Chromium to achieve (a) above? ....... OR is (a) above just the default state of Linux chromium anyhow on x11?
..................& where is (b) above...?
--------------------------------------------------------------------------------------
(c) Well, there should be no problem when Firefox is enabled with GPU acceleration.
........what must a typical Linux user actually DO to FF to achieve (c) above?........ or is (c) the default state of FF on x11 anyhow?
thanks
v
-
In CorePure64, both firefox-ESR and a recent firefox_getLatest seem to use gpu acceleration by default.
I've no plans to update chromium-browser, but the build notes are here if anybody else would like to try.
http://tinycorelinux.net/9.x/x86_64/tcz/src/chromium-browser/compile_chromium-browser
-
i see Juanto...
so Chromium Linux would need a rebuild to achieve my last posts goals?
(i suppose in that ninth line of build instructions you mention you would put "enable_gpu=true"?)
what about that Iridium browser on tcl64?
thx
v
-
....so what must a typical Linux user actually need to DO to Chromium to achieve ...
I've no plans to update chromium-browser, but the build notes are here if anybody else would like to try.
In fact, the latest version of Chromium/Chrome has GPU acceleration enabled by default.
hat must a typical Linux user actually DO to FF to achieve (c) above?.......
See Juanito.
-
(i suppose in that ninth line of build instructions you mention you would put "enable_gpu=true"?)
There is no such simple thing.
what about that Iridium browser on tcl64?
I think most but not all browsers based on Chromium will have the same problem.
When you ask questions about Chromium GPU on the Internet, the most you'll ever get is a call to turn it off...
-
ONE
In fact, the latest version of Chromium/Chrome has GPU acceleration enabled by default.
you are referring to Chrome /chromium on general Linux right?
version 87.0.4280.66?
......but this is a TCL forum and the repo's don't contain the latest Chromium for Linux.
(where is a Chromium 87 build for tcL?)
thanks
(in any event, where exactly is the Linux chromium flag to switch on Chromium's GPU compatibility in any version?)......if you could remind me
v
-
you are referring to Chrome /chromium on general Linux right?
version 87.0.4280.66?
Yeah.
......but this is a TCL forum and the repo's don't contain the latest Chromium for Linux.
(where is a Chromium 87 build for tcL?)
http://tinycorelinux.net/9.x/x86_64/tcz/src/chromium-browser/compile_chromium-browser
.....if you could remind me
chrome://flags/
[/quote]
-
hello forum,
This topic (thread) here .......it could be helpful for many user
experiences with computers and the "Chromium" free world wide
web browser.
By that i mean, my comments refer to Chromium on win64 which
here
In essence, such users of that hardware and platform
can simply go into "chrome://flags" settings by typing it into the addr
bar of the web browser and set...."software over=ride" setting regarding the GPU
to........ " over-ride"........ it.......ENABLE it.
This results in a correct list of results when you study "chrome://gpu" command typed into the addr
bar of the web browser showing .......all of the top entries show
that "all hardware items" are properly fully accelerated & functioning correct.
(.....it seems......this method above is therefore using all of the PC' computers chips "properly" and directly)
thx
vin
ps. Latest Chromium on win64 worke(d)......maybe there is fallback for a while also.
thx
-
hello forum,
There seems to be a bad bug with Chromium......whereby there is loss of the right context menu at "full screen" option.
Onlin , it seems there is knowledge but likely too far drill down for the remedy.
it affects global users usability at prime level.
thx
v