Hardware Acceleration in Firefox Stopped Working after Kernel Upgrade

After upgrading to the latest kernel (5.6 from 5.5), hardware acceleration in Firefox stopped working (although I'm not sure if that's causal). Specifically, a website which requires WebGL says it's disabled. I have in the Firefox settings specified to use hardware acceleration. The same site does work in Chromium.

My laptop has a discrete graphics card (NVIDIA GeForce MX150), but now am unsure if it's being used by the system at all.

So I have a question in two parts:

  1. How can I get hardware acceleration working in Firefox again?
  2. How can I confirm that the system is using my discrete graphics card, ideally with the hardware switching?

Hardware and Software:

System:
  Kernel: 5.6.3-2-MANJARO x86_64 bits: 64 compiler: gcc v: 9.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.6-x86_64 
  root=UUID=0bf7f3a7-bdca-49b7-adc4-e687b5efd359 rw quiet 
  cryptdevice=UUID=735885d8-6f67-4baa-b19a-1edd22f47eca:luks-735885d8-6f67-4baa-b19a-1edd22f47eca 
  root=/dev/mapper/luks-735885d8-6f67-4baa-b19a-1edd22f47eca 
  resume=/dev/mapper/luks-735885d8-6f67-4baa-b19a-1edd22f47eca 
  Desktop: Cinnamon 4.4.8 dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: HUAWEI product: MACH-WX9 v: M14 serial: <filter> 
  Mobo: HUAWEI model: MACH-WX9 v: M14 serial: <filter> UEFI: HUAWEI v: 1.28 
  date: 03/15/2019 
Battery:
  ID-1: BAT0 charge: 51.0 Wh condition: 51.3/56.3 Wh (91%) volts: 8.5/7.6 
  model: DYNAPACK HB4593R1ECW type: Li-ion serial: <filter> 
  status: Discharging cycles: 138 
CPU:
  Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP 
  arch: Kaby Lake family: 6 model-id: 8E (142) stepping: A (10) 
  microcode: CA L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 32012 
  Speed: 800 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Huawei driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:5917 
  Device-2: NVIDIA GP108M [GeForce MX150] driver: N/A bus ID: 01:00.0 
  chip ID: 10de:1d12 
  Display: x11 server: X.Org 1.20.8 driver: intel resolution: 3000x2000~60Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.4 
  direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Huawei 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71 
  Sound Server: ALSA v: k5.6.3-2-MANJARO 
Network:
  Device-1: Intel Wireless 8265 / 8275 vendor: Huawei driver: iwlwifi 
  v: kernel port: 4040 bus ID: 3c:00.0 chip ID: 8086:24fd 
  IF: wlp60s0 state: up mac: <filter> 
  IF-ID-1: virbr0 state: down mac: <filter> 
  IF-ID-2: virbr0-nic state: down mac: <filter> 
Drives:
  Local Storage: total: 476.94 GiB used: 315.68 GiB (66.2%) 
  ID-1: /dev/nvme0n1 vendor: Toshiba model: N/A size: 476.94 GiB block size: 
  physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter> 
  rev: AAXA4103 scheme: GPT 
Partition:
  ID-1: / raw size: 476.64 GiB size: 468.16 GiB (98.22%) 
  used: 315.68 GiB (67.4%) fs: ext4 dev: /dev/dm-0 
Sensors:
  System Temperatures: cpu: 44.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 280 Uptime: 14m Memory: 15.40 GiB used: 2.93 GiB (19.0%) 
  Init: systemd v: 244 Compilers: gcc: 9.3.0 alt: 8 clang: 9.0.1 Shell: bash 
  v: 5.0.16 running in: gnome-terminal inxi: 3.0.37 

check under firefox
Help > information and repair
you will see all infos

Take a look here:

1 Like

Thank you for the quick responses.

I did check Mozilla's support page, and found this, which suggests I update the graphics drivers. As far as I know they are updated (but this may be my problem). Hardware acceleration is already enabled as per those instructions.

Under about:support, it says "OpenGL" under compositing, and layers.acceleration.force-enabled is already set to true.

This is probably not related to the kernel upgrade. The current version of Firefox is not compatible with the new version of libdrm. This will need to be fixed by Mozilla.

1 Like

The site was still working after Firefox and libdrm were last upgraded (April 6th). I strongly suspect it may be a graphics card driver issue. Is there any way I can rule that out?

Why?

... though from the looks of it you are using the (olderish?) intel instead of modesetting (and which might mean you are using the inferior bumblebee) .. so those are things worth looking into.

mhwd -li
1 Like

No, the new version of libdrm is not whitelisted in Firefox's sandbox. I've read the bug reports on mozilla.org and archlinux.org.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by