I successfully built Firefox v135 from source for the RISC-V architecture and created a .deb package. After installing the package, Firefox launches correctly, but perfor… (Lesen Sie mehr)
I successfully built Firefox v135 from source for the RISC-V architecture and created a .deb package. After installing the package, Firefox launches correctly, but performance is significantly degraded—especially during video playback, where it becomes very laggy.
Upon inspecting about:support, I noticed that under the "Compositing" section, it shows WebRender (software), and CPU usage is extremely high. Additionally, WebGL 1 and WebGL 2 are not available, despite the presence of a dedicated GPU Hardware and its driver.
During the build process, Firefox required LLVM v14 as a dependency. It appears that this setup defaults to using LLVMpipe, which results in software rendering and prevents the OpenGLES driver from being utilized, leading to the fallback to software WebRender.
In contrast, I tested another .deb package of Firefox built specifically for the VisionFive2 (JH7110) board. In that case, the "Compositing" section correctly shows WebRender (without the "software" tag), and both WebGL 1 and WebGL 2 are available, indicating proper GPU Hardware acceleration.
Could anyone guide me on how to enable hardware-accelerated WebRender and ensure that Firefox uses the GPU instead of falling back to software rendering?
Please find the "about:support" page in the attached Troubleshooting Information.xhtml file. Kindly do let us know if there's any further information needed.
Thanks in advance,
Saiteja