NVIDIA GPU not working, possibly related to latest driver

Maybe you could try to remove the video-hybrid-intel-nvidia-prime driver from MHWD, and try to reinstall it, or install the 470 driver instead.

If inxi still doesn’t show Nvidia driver loaded for your Nvidia card, make sure you don’t have blacklist somewhere forbidding loading the Nvidia module (optimus manager or bumblebee might do that, you said you don’t have it but that doesn’t mean you didn’t install it at some point).

For additional info give output of ls /usr/lib/modprobe.d/ and ls /etc/modprobe.d/

1 Like
qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x5649c9c4e380) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x5649c9c7ede0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents

And where is that warning come from? OBS or GDM?

From OBS .

I removed the video-hybrid-nvidia-prime and try install it, then I got this,

> Installing video-hybrid-intel-nvidia-prime...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-prime/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
:: Synchronizing software package databases...
Core is downloading...
Extra is downloading...
Community is downloading...
Multilib is downloading...
Error: Not found target: Linux513-nvidia
Error: Not found target: Linux514-nvidia
Error: pacman failed!
Error: script failed!
$ ls usr/lib/modproobe.d
bluetooth-usb.conf  nvdimm-security.conf  README  systemd.conf  uvesafb.conf
$ ls etc/modprobe.d
mhwd-gpu.conf
$ cat mhwd-gpu.conf
##
## Generated by mhwd - Manjaro Hardware Detection
##

You have unsupported kernels, this is why it is important to not cut down information you give (like you did with inxi).

Install supported kernel.

mhwd-kernel -i linux515

Reboot, and remove the unsupported kernels

mhwd-kernel -r linux513
mhwd-kernel -r linux514

Before doing that maybe give full list of kernels used with mhwd-kernel -li so we can have a better view. Also a full inxi -Fazy

2 Likes

Oh, my god, I’m using vbox with linux514, I’m not sure if I should reinstall it !

Currently running: 5.14.21-2-MANJARO (linux514)
The following kernels are installed in your system:
   * linux513
   * linux514

Install kernel 5.15, give the command output now.

sudo mhwd-kernel -i linux515

Linux515 has been installed successfully.

Currently running: 5.14.21-2-MANJARO (linux514)
The following kernels are installed in your system:
   * linux513
   * linux514
   * linux515

Give the output of the command I gave in previous post to check your concerns about virtualbox.

Anyway, you should be able to reboot on kernel 5.15 and then you could remove linux513 and linux514, then install Nvidia driver again.

Don’t be mad, Bro, I removed the kernel 513 and 514, and the NVIDIA driver has been installed successfully.

$ inxi -Fazy
PU:
  Info: model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Whiskey Lake
    family: 6 model-id: 0x8E (142) stepping: 0xB (11) microcode: 0xEA
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 685 high: 700 min/max: 400/3900 scaling:
    driver: intel_pstate governor: powersave cores: 1: 700 2: 700 3: 700 4: 700
    5: 700 6: 641 7: 693 8: 651 bogomips: 28808
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush clflushopt
    cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts
    epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu fsgsbase fxsr
    ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid
    invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr mtrr
    nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln
    pni popcnt pse pse36 pts rdrand rdseed rdtscp rep_good sdbg sep smap smep
    ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc
    tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave
    xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown status: Not affected
  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: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
$ inxi -G
Graphics:
  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] driver: i915 v: kernel
  Device-2: NVIDIA GP108M [GeForce MX250] driver: nouveau v: kernel
  Device-3: Realtek USB Camera type: USB driver: uvcvideo
  Display: wayland server: X.org 1.21.1.3 driver: loaded: modesetting
    failed: nvidia resolution: <missing: xdpyinfo>
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
    v: 4.6 Mesa 21.3.5
$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

You once again cut down the inxi output. Give the output as I asked. No need for your other inxi -G output if you give what I asked.

We can also see that the Nvidia driver is still not loaded. Either you’re not installing properly the driver (how do you install it, where are the commands output?), or you have something blacklisting/forbidding the module to load.

You reboot after installing drivers, right?

What do you mean? That is all inxi -fazy's output, I installed the driver by

$ sudo mhwd -i pci video-hybrid-nvidia-prime

and rebooted.

No that’s not, read what you posted. It is missing the beginning and the end, you copied randomly in the middle.

Then that should have installed drivers properly. Come back to command in this post and give the output (but as seen in inxi, Nvidia module is not loaded so that shouldn’t work).

As I suggested, try the 470 hybdrid driver to see if it works.

1 Like

That’s all.

and

$ prime-run glxinfo | grep opengl
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  50
  Current serial number in output stream:  51

That’s not the command I gave inxi -Fazy not inxi -fazy

Anyway, Nvidia module doesn’t load

It is the open source module nouveau that loads.

Check journal journalctl -b0 | grep nvidia

My bad.

System:
  Kernel: 5.15.21-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-5.15-x86_64
    root=UUID=60fbec14-d78f-42e0-a683-08e68b315d7a rw rootflags=subvol=@ quiet
    resume=UUID=c0695da8-f7dd-427b-bb49-3fa699c73a9b udev.log_priority=3
  Desktop: GNOME 41.3 tk: GTK 3.24.31 wm: gnome-shell dm: GDM 41.3
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: MECHREVO product: S1 Pro Series v: N/A
    serial: <superuser required>
  Mobo: N/A model: N/A serial: <superuser required>
    UEFI: American Megatrends v: SW1M.05 date: 05/07/2019
Battery:
  ID-1: BAT0 charge: 50.2 Wh (100.0%) condition: 50.2/50.2 Wh (100.0%)
    volts: 12.3 min: 11.4 model: LENGDA type: Unknown serial: <filter>
    status: Not charging
CPU:
  Info: model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Whiskey Lake
    family: 6 model-id: 0x8E (142) stepping: 0xB (11) microcode: 0xEA
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 700 min/max: 400/3900 scaling: driver: intel_pstate
    governor: powersave cores: 1: 700 2: 700 3: 700 4: 700 5: 700 6: 700 7: 700
    8: 700 bogomips: 28808
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown status: Not affected
  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: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] driver: i915 v: kernel
    bus-ID: 00:02.0 chip-ID: 8086:3ea0 class-ID: 0300
  Device-2: NVIDIA GP108M [GeForce MX250] driver: nouveau v: kernel
    alternate: nvidia_drm,nvidia bus-ID: 01:00.0 chip-ID: 10de:1d13
    class-ID: 0302
  Device-3: Realtek USB Camera type: USB driver: uvcvideo bus-ID: 1-2:2
    chip-ID: 0bda:5830 class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org 1.21.1.3 compositor: gnome-shell driver:
    loaded: modesetting failed: nvidia alternate: fbdev,nouveau,nv,vesa
    display-ID: 0 resolution: <missing: xdpyinfo>
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 21.3.5
    direct render: Yes
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:9dc8 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.21-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.45 running: no
Network:
  Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:9df0 class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169 v: kernel port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB
    driver: btusb v: 0.8 bus-ID: 1-10:5 chip-ID: 8087:0aaa class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 1.38 TiB used: 31.27 GiB (2.2%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD10SPZX-00Z10T0 size: 931.51 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 1A01 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: LITE-ON model: CV8-8E512
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 101 scheme: GPT
Partition:
  ID-1: / raw-size: 922.42 GiB size: 922.42 GiB (100.00%)
    used: 31.25 GiB (3.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 25.8 MiB (8.6%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 922.42 GiB size: 922.42 GiB (100.00%)
    used: 31.25 GiB (3.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 922.42 GiB size: 922.42 GiB (100.00%)
    used: 31.25 GiB (3.4%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda3 maj-min: 8:3
Sensors:
  System Temperatures: cpu: 44.0 C pch: 41.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 297 Uptime: 48m wakeups: 1 Memory: 7.65 GiB
  used: 1.99 GiB (26.0%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 clang: 13.0.1 Packages: pacman: 1248 lib: 318 Shell: Zsh v: 5.8
  running-in: gnome-terminal inxi: 3.3.12

$ journalctl -b0 | grep nvidia
2月 20 13:26:03 s1-pro dbus-daemon[765]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.95' (uid=0 pid=2842 comm="sudo mhwd -i pci video-hybrid-intel-nvidia-prime ")
2月 20 13:26:03 s1-pro sudo[2842]:      sky : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mhwd -i pci video-hybrid-intel-nvidia-prime
2月 20 13:27:39 s1-pro kernel: nvidia: module license 'NVIDIA' taints kernel.
2月 20 13:27:39 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 13:27:39 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508
2月 20 13:27:40 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 13:27:40 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508
2月 20 13:27:46 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 13:27:46 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508
2月 20 13:27:47 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 13:27:47 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508
2月 20 13:28:02 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 13:28:02 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508
2月 20 13:28:41 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 13:28:41 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508
                                                Module libnvidia-egl-gbm.so.1 with build-id e0818354660c8a99ce2f72bda50cf4a2eae7bd7d
                                                Module libnvidia-eglcore.so.510.47.03 with build-id dd2a471b7a7acbc5b02ebce3271a8a7e5c57bb29
                                                Module libnvidia-egl-wayland.so.1 with build-id 7026a2a5082aff391d23ed5af4678c543383f2d9
                                                Module libnvidia-glsi.so.510.47.03 with build-id 495215b6646c229e97412d5e37067e365d9072b1
                                                Module libEGL_nvidia.so.0 with build-id 00c57addfc44db8179398fb3b940fe7954490299
2月 20 13:56:33 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 13:56:33 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508
2月 20 13:58:20 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 13:58:20 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508
2月 20 14:00:49 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 14:00:49 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508
2月 20 14:08:37 s1-pro kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
                                NVRM: nouveau, rivafb, nvidiafb or rivatv 
2月 20 14:08:37 s1-pro kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 508

For a test we could manually blacklist the nouveau driver (I think it should have been when installing the Nvidia driver with MHWD).

What is the output of cat /etc/modprobe.d/mhwd-gpu.conf and/or cat /etc/modprobe.d/mhwd-nvidia.conf before we try to manually blacklist nouveau?

Well, It’s not the same as before

##
## Generated by mhwd - Manjaro Hardware Detection
##
 
blacklist nouveau
blacklist ttm
blacklist drm_kms_helper
blacklist drm
options nvidia "NVreg_DynamicPowerManagement=0x02"

So nouveau is blacklisted but it is loaded instead of Nvidia in your inxi it makes no sense to me. Seems like you didn’t reboot after installing Nvidia driver.