Don't expect too much from the new OpenGL driver for browsers. The only acceleration which it might provide is for WebGL.kusti8 wrote:With the current GPU driver, no, but with the new OpenGL driver, yes there is hardware acceleration.Sandros94 wrote:Hi, can you tell me if I'm wrong about chromium (v49 and next coming v50) doesn't have hardware acceleration?
Yes, WebGL works with it and the actual page rendering as well I think, but video does not work.gkreidl wrote:Don't expect too much from the new OpenGL driver for browsers. The only acceleration which it might provide is for WebGL.kusti8 wrote:With the current GPU driver, no, but with the new OpenGL driver, yes there is hardware acceleration.Sandros94 wrote:Hi, can you tell me if I'm wrong about chromium (v49 and next coming v50) doesn't have hardware acceleration?
It will NOT accelerate web video.
Ooooooooo...looking forward to it!kusti8 wrote:Just saw that v50 was released. Going to start the compile today and start testing once that is done.
Yeah. I just saw that so I installed it from there and I'm keeping it like this until you finish compiling.kusti8 wrote:Just saw that v50 was released. Going to start the compile today and start testing once that is done.
It's going to take maybe 4 or 5 days because I'm running it on a Pi2. A Pi3 didn't work because it overheated and failed the compile and I'm still looking at cross compile.Ben_is_best wrote:How's the compile coming along?
OK. Thank you.kusti8 wrote:It's going to take maybe 4 or 5 days because I'm running it on a Pi2. A Pi3 didn't work because it overheated and failed the compile and I'm still looking at cross compile.Ben_is_best wrote:How's the compile coming along?
If the OS runs from a HDD compiling is much faster. Using make -j3 or -j4 I can compile even large packages in decent time (kodi takes about an hour, for example, VLC with -j4 13 minutes).kusti8 wrote:It's going to take maybe 4 or 5 days because I'm running it on a Pi2. A Pi3 didn't work because it overheated and failed the compile and I'm still looking at cross compile.Ben_is_best wrote:How's the compile coming along?
I'm running the entire build on a HDD because its so big. The problem is it needs swap and a lot of it, more than 2GB which slows it down. It automatically uses all cores. The Pi3 had a heatsink which was open to the elements and it still did not work. GCC reported that it was a hardware or OS problem. I'm guessing I need a fan for that. Temps when monitored went over 80 easily. I'll see if I can find a nice fan.gkreidl wrote:If the OS runs from a HDD compiling is much faster. Using make -j3 or -j4 I can compile even large packages in decent time (kodi takes about an hour, for example, VLC with -j4 13 minutes).kusti8 wrote:It's going to take maybe 4 or 5 days because I'm running it on a Pi2. A Pi3 didn't work because it overheated and failed the compile and I'm still looking at cross compile.Ben_is_best wrote:How's the compile coming along?
On the RPi 3 you need a heat sink and a good airflow. I use a case with open sides. For a large compile job with all 4 cores running at 100% the temperature does still stay below 80 deg. (no throttling).
Ok. But I used a Launchpad builders and it successfully compiled in 9 hours so I'll start testing later today.gkreidl wrote:Use less cores, if it starts swapping, and reduce the GPU-memory for compiling. To compile kodi, I had to reduce GPU memory to 64 MB and use 3 processes only.
Code: Select all
deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi
deb http://dl.bintray.com/kusti8/chromium-rpi jessie main devCode: Select all
sudo apt-get update
sudo apt-get dist-upgradeOk, good. I've just done some regular browsing and it's seems to work fine so I'm going to release it today.cjan wrote:test 50
1. disable "Use hardware acceleration where available" in chrome://settings --> p2 youtube 360p OK.
2. Rpi2 4.4.11-v7+ #888 drm-vc4-next, enable "Use hardware acceleration where available" in chrome://settings --> p2 youtube 360p OK.
btw, youtube can not forward play.kusti8 wrote:Ok, good. I've just done some regular browsing and it's seems to work fine so I'm going to release it today.cjan wrote:test 50
1. disable "Use hardware acceleration where available" in chrome://settings --> p2 youtube 360p OK.
2. Rpi2 4.4.11-v7+ #888 drm-vc4-next, enable "Use hardware acceleration where available" in chrome://settings --> p2 youtube 360p OK.
This used to work with 49, so maybe there's a bug in this version/build.cjan wrote:[
btw, youtube can not forward play.
I just installed the chromium 50 version from the Ubuntu 14.04 ports (I still have libass4 on my system), just for testing. HW acceleration must be disabled to display web video and I also disabled the media-source flag (to get rid of the stop and go effect when playing web video). Moving in the video is possible as it used to be.gkreidl wrote:This used to work with 49, so maybe there's a bug in this version/build.cjan wrote:[
btw, youtube can not forward play.
Which youtube bug?Kratos wrote:Nothing to report other than the YouTube bug. Cheers!
Kratos
The needing to disable hardware acceleration in Chromium settings.gkreidl wrote:Which youtube bug?Kratos wrote:Nothing to report other than the YouTube bug. Cheers!
Kratos
Obviously they use OpenGL calls now for compositing by default. On the RPi this is emulated by software which is far too slow (when it comes to video). Disabling this should also speed up any page display. With the new GL driver it should work (but everything else won't work at the moment like playing videos with omxplayer).kusti8 wrote:The needing to disable hardware acceleration in Chromium settings.gkreidl wrote:Which youtube bug?Kratos wrote:Nothing to report other than the YouTube bug. Cheers!
Kratos