Chromebook OS runs Scratch 3 EFFORTLESSLY on Pi 3B. Can we improve chromium?

[Botspot]

I tried out Scratch 3 on the latest image of chromebook OS for Raspberry Pi, to see if Scratch 3 would work better than it currently does on Raspbian.
Well, it does! In fact, the graphics performance was equivalent to my $400 windows laptop!

On Raspbian: (slow and laggy)


On Chromebook OS: video link Perfectly smooth, not slow or laggy.

What made the difference? If I understand correctly, Chromebook OS is hardware accelerated, Chromium in Raspbian is not.
Below is a screenshot of chrome://gpu in Raspbian Stretch:


Doesn't look too good.
Now what does chrome://gpu look like on chromebook OS?


Less red, more green. I think WebGL and WebGL2 are make the most difference in terms of Scratch 3.

So we know chromebook OS runs Scratch 3 better than Chromium in Raspbian. And we think that it is due to WebGL being hardware accelerated.
Here is my question: Can we figure out how chromebook OS's hardware acceleration works, and then take that knowledge and apply it to chromium-browser in Raspbian?

[jamesh]

Has already been done. Minor bug fix to Chromium in the offing and all will work fine.

[Botspot]

Has already been done.

Uhh, what has been done?

Minor bug fix to Chromium in the offing and all will work fine.

Really? What kind of bug fix? I'm sure many folks in the scratch forum would like to hear about this.

[jamesh]

Scratch 3 on the Pi4 runs very well, we've been testing for some time. Once the GPU acceleration fix is released it will be even quicker.

[Botspot]

Scratch 3 on the Pi4 runs very well, we've been testing for some time. Once the GPU acceleration fix is released it will be even quicker.

OK, but is there any plan to GPU accelerate WebGL for the Pi3?

[jamesh]

Scratch 3 on the Pi4 runs very well, we've been testing for some time. Once the GPU acceleration fix is released it will be even quicker.

OK, but is there any plan to GPU accelerate WebGL for the Pi3?

Try turning on the FKMS driver which will turn on WebGL in Chromium on the Pi3 as well as the Ppi4. Obviously, the Pi4 is faster!

[Botspot]

Scratch 3 on the Pi4 runs very well, we've been testing for some time. Once the GPU acceleration fix is released it will be even quicker.

OK, but is there any plan to GPU accelerate WebGL for the Pi3?

Try turning on the FKMS driver which will turn on WebGL in Chromium on the Pi3 as well as the Ppi4. Obviously, the Pi4 is faster!

Couldn't find much information on the FKMS driver, but I did these two things:

• enabled "OpenGL desktop driver with full KMS" in raspi-config.

  

  2019-07-05-082351_1280x1024_scrot.png (14.25 KiB) Viewed 8591 times

• added this line

  Code: Select all

  dtoverlay=vc4-kms-v3d

  to /boot/config.txt

Rebooted and now Scratch 3 runs *almost* as fast as it did on chromebook OS.
Now, are there any disadvantages to using dtoverlay=vc4-kms-v3d?

[jamesh]

You really need the fake KMS option, that the one where a load of work has been done. However, if something works for you, go for it until it doesn't work for you!

[sits]

I tried using the "Fake KMS" (and the full one) on my RPi3 but after a reboot I get this error from chromium. Any ideas? I done an update already.

bootstrap_helper: /usr/lib/chromium-browser/nacl_helper: Cannot open ELF file! errno=2
[1:1:0715/201124.275136:ERROR:nacl_fork_delegate_linux.cc(315)] Bad NaCl helper startup ack (0 bytes)
[2065:2065:0715/201125.233912:ERROR:gl_surface_glx.cc(411)] GLX 1.3 or later is required.
[2065:2065:0715/201125.234092:ERROR:gl_initializer_x11.cc(130)] GLSurfaceGLX::InitializeOneOff failed.
[2065:2065:0715/201125.322335:ERROR:gpu_child_thread.cc(327)] Exiting GPU process due to errors during initialization

[Botspot]

I tried using the "Fake KMS" (and the full one) on my RPi3 but after a reboot I get this error from chromium. Any ideas? I done an update already.

bootstrap_helper: /usr/lib/chromium-browser/nacl_helper: Cannot open ELF file! errno=2
[1:1:0715/201124.275136:ERROR:nacl_fork_delegate_linux.cc(315)] Bad NaCl helper startup ack (0 bytes)
[2065:2065:0715/201125.233912:ERROR:gl_surface_glx.cc(411)] GLX 1.3 or later is required.
[2065:2065:0715/201125.234092:ERROR:gl_initializer_x11.cc(130)] GLSurfaceGLX::InitializeOneOff failed.
[2065:2065:0715/201125.322335:ERROR:gpu_child_thread.cc(327)] Exiting GPU process due to errors during initialization

OK so you got some errors from chromium. Does Chromium start?

What version of Raspbian? Buster or Stretch?
Try using fake KMS on a fresh image and see if the result is different or not.