The NVIDIA driver is not loaded

You have to start it with

prime-run nvidia-settings
1 Like

The same error:

Check your bios

And see if it has gpu switching options

Try changing them
The check

1 Like

Hmm it looks odd

Have you upgraded your system ?
If not upgrade your system first

sudo pacman -Syyuu
1 Like

Yes, I have upgraded the system to the latest before install the NVIDIA Driver.

And i checked the bios, There is no switch for GPU.

Do i need to try this?

Check logs

journalctl -b -p3 --no-pager --no-hostname
bash -c 'for Xlog in $(ls /var/log/Xorg.?.log); do echo -e "\n" $Xlog ; grep -E "(EE)|(WW)|failed|Time" $Xlog ; done'

Also post this file's contents to bin.garudalinux.org

/var/log/Xorg.0.log
1 Like

Could you try:

sudo modprobe -v nvidia

and paste the output (as text!).

1 Like
sudo modprobe -v nvidia

modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.11.2-zen1-1-zen
journalctl -b -p3 --no-pager --no-hostname
-- Journal begins at Sun 2021-03-07 00:36:14 CST, ends at Sun 2021-03-07 00:37:48 CST. --
3月 07 00:36:14 systemd[1]: Failed to start Setup Virtual Console.
3月 07 00:36:14 systemd-vconsole-setup[324]: /usr/bin/loadkeys failed with exit status 1.
3月 07 00:36:14 systemd-modules-load[321]: Failed to find module 'nvidia-drm'
3月 07 00:36:14 systemd-modules-load[321]: Failed to find module 'nvidia-uvm'
3月 07 00:36:16 kernel: psmouse serio1: synaptics: Advanced gesture mode init failed: -5
3月 07 00:36:16 kernel: psmouse serio1: synaptics: Unable to initialize device.
3月 07 00:36:20 nmbd[3309]: [2021/03/07 00:36:20.191917,  0] ../../lib/util/become_daemon.c:147(daemon_status)
3月 07 00:36:20 nmbd[3309]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
3月 07 00:36:20 nmbd[3309]: [2021/03/07 00:36:20.191988,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
3月 07 00:36:20 nmbd[3309]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
3月 07 00:36:23 sddm-helper[3328]: gkr-pam: unable to locate daemon control file
3月 07 00:36:25 kwin_x11[3618]: kwin_xkbcommon: XKB: Couldn't process include statement for 'cn(\0)'
3月 07 00:36:25 kwin_x11[3618]: kwin_xkbcommon: XKB: Abandoning symbols file "(unnamed)"
3月 07 00:36:25 kwin_x11[3618]: kwin_xkbcommon: XKB: Failed to compile xkb_symbols
3月 07 00:36:25 kwin_x11[3618]: kwin_xkbcommon: XKB: Failed to compile keymap
3月 07 00:36:25 systemd-coredump[3796]: [🡕] Process 3771 (paleofetch) of user 1000 dumped core.
                                         
                                         Stack trace of thread 3771:
                                         #0  0x00007f656bc8005e __strncpy_avx2 (libc.so.6 + 0x16305e)
                                         #1  0x000055de3ea28537 n/a (paleofetch + 0x3537)
                                         #2  0x000055de3ea2719f n/a (paleofetch + 0x219f)
                                         #3  0x00007f656bb44b25 __libc_start_main (libc.so.6 + 0x27b25)
                                         #4  0x000055de3ea273ce n/a (paleofetch + 0x23ce)
3月 07 00:36:25 kup-daemon[3777]: kup.daemon: "Kup未启用,请从系统设置模块中启用。可以运行kcmshell5 kup以进行此操作。"
3月 07 00:36:27 bluetoothd[568]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info
3月 07 00:36:27 bluetoothd[568]: profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info
3月 07 00:36:30 nmbd[3309]: [2021/03/07 00:36:30.192668,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
3月 07 00:36:30 nmbd[3309]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
3月 07 00:36:30 smbd[5432]: [2021/03/07 00:36:30.381509,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
3月 07 00:36:30 smbd[5432]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
3月 07 00:36:32 bluetoothd[568]: profiles/input/device.c:control_connect_cb() connect to 34:88:5D:6F:7D:71: Host is down (112)
3月 07 00:36:37 bluetoothd[568]: profiles/input/device.c:control_connect_cb() connect to 34:88:5D:86:99:65: Host is down (112)
3月 07 00:36:53 nmbd[3309]: [2021/03/07 00:36:53.409961,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
3月 07 00:36:53 nmbd[3309]:   *****
3月 07 00:36:53 nmbd[3309]: 
3月 07 00:36:53 nmbd[3309]:   Samba name server XJ-GARUDA is now a local master browser for workgroup WORKGROUP on subnet 192.168.3.114
3月 07 00:36:53 nmbd[3309]: 
3月 07 00:36:53 nmbd[3309]:   *****

The file`s contents:

/var/log/Xorg.0.log

Next, output of:

sudo dkms autoinstall
2 Likes

Evidence is the same as other issues where BIOS is auto hiding dGPU from the system.
I suggest you ask this at your Laptop's vendor Support forum.

How can I disable "auto-enable/disable dGPU"?

2 Likes
sudo dkms autoinstall

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'make' -j12 IGNORE_PREEMPT_RT_PRESENCE=1 NV_EXCLUDE_BUILD_MODULES='__EXCLUDE_MODULES' KERNEL_UNAME=5.11.2-zen1-1-zen IGNORE_CC_MISMATCH='__IGNORE_CC_MISMATCH' modules...........
cleaning build area...
Kernel cleanup unnecessary for this kernel.  Skipping...

DKMS: build completed.

nvidia.ko.xz:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/5.11.2-zen1-1-zen/kernel/drivers/video/

nvidia-uvm.ko.xz:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/5.11.2-zen1-1-zen/kernel/drivers/video/

nvidia-modeset.ko.xz:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/5.11.2-zen1-1-zen/kernel/drivers/video/

nvidia-drm.ko.xz:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /usr/lib/modules/5.11.2-zen1-1-zen/kernel/drivers/video/

depmod.....

DKMS: install completed.
1 Like

@jonathon Thank you very much! The Nvidia Settings can be opend, How to verify that the Nvidia graphics card can work normally, please ? @jonathon @petsam @librewish

Please, don't post images for just text output. It is explained numerous times. :face_with_raised_eyebrow:

Manually, start apps with prime-run <app>.
Else, the system would automatically use nvidia for resource hungry apps.

Check again inxi -Gxxxza

2 Likes

Sorry, I will post text from now on, thanks :slightly_smiling_face:

inxi -Gxxxza
Graphics:  Device-1: Intel UHD Graphics 630 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:3e9b class ID: 0300 
           Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Hewlett-Packard 
           driver: nvidia v: 460.56 alternate: nouveau,nvidia_drm bus ID: 01:00.0 chip ID: 10de:1f91 
           class ID: 0302 
           Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus ID: 1-12:4 
           chip ID: 0c45:6723 class ID: 0e02 
           Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: loaded: intel,nvidia 
           unloaded: modesetting,nouveau alternate: fbdev,nv,vesa display ID: :0 screens: 1 
           Screen-1: 0 s-res: 3840x2160 s-dpi: 240 s-size: 406x228mm (16.0x9.0") 
           s-diag: 466mm (18.3") 
           Monitor-1: eDP1 res: 3840x2160 hz: 60 dpi: 287 size: 340x190mm (13.4x7.5") 
           diag: 389mm (15.3") 
           OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.3.4 
           direct render: Yes

Is this a success ?

prime-run google-chrome-stable

[511428:1:0307/194511.720679:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[511473:1:0307/194511.720739:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[511344:1:0307/194511.720753:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[513190:513190:0307/194511.890799:ERROR:gles2_cmd_decoder_passthrough.cc(1518)]   GLES2DecoderPassthroughImpl: Context reset detected after MakeCurrent.
[513190:513190:0307/194511.890943:ERROR:gpu_service_impl.cc(1177)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[511428:1:0307/194511.894050:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[513273:513273:0307/194512.053069:ERROR:gles2_cmd_decoder_passthrough.cc(1518)]   GLES2DecoderPassthroughImpl: Context reset detected after MakeCurrent.
[513273:513273:0307/194512.053217:ERROR:gpu_service_impl.cc(1177)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[511305:7:0307/194512.055052:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[511305:7:0307/194512.085029:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[511521:1:0307/194513.446015:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[510535:1:0307/194517.689156:ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.

I can't tell...
I think you can check in Chrome info pages about which driver/GPU is being used.

1 Like

Thanks :slightly_smiling_face:

Oh frick, I probably should have gone for this instead of giving up and switching distro. I'll test this out as well and if it works, I'm staying with Garuda again. Thanks m8!

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