Nvidia Drivers issue of when booted, you get stuck on [ok] Reached target Graphical Interface

Hello, so l’m a noobie and l’ve been trying to install Nvidia drivers for my RTX 3060 on Linux kernel version 6.6.63-1-Its.

So like the title says, whenever I’d boot into Linux, l’d go through all the boot logs but would always get stuck on Lok Reached target Graphical Interface. I know that is is my problem because I was messing with the Nvidia graphics setting in my previous attempt to try to update the drivers or to see what drivers were installed. I actually installed EndevourOS yesterday and got it up and working, and I did the Nvidia install, but I’m pretty dumb and I still wanted to update the drivers and check the version, resulting in my rebooting and getting my issue.

The first I did was press ctrl+alt+f2 to get back to the terminal.

My first solution was to use the wiki here https://wiki.archlinux.org/title/NVIDIA

However when I got to the part to run the command:

install - Dt “$builddir/tools/bpf/resolve_btfids” tools/bpf/resolve_btfids/resolve_btfids

It’d result in the error:

install: cannot stat

"tools/bpf/resolve_btfids/resolve_btfids’: No such file or directary.

So instead I tried this other tutorial online and followed it through: https://github.com/korvahannu/arch-nvidia-drivers-installation-guide?tab=readme-ov-file

But it didn’t do anything and I’m still at square one, however I did notice that when I’d run

sudo mkinitcpio -P

It’d come up with the errors:

ERROR: module not found: ‘nvidia’

ERROR: module not found: ‘nvidia_modeset’

ERROR: module not found: ‘nvidia_uvm’

ERROR: module not found: 'nvidia_drm"

But I’m not really sure how to fix those errors. I tried reinstalling the drivers again after I saw the errors, but I’d still didn’t work and give the same 4 errors.

Welcome to the community @planetwool :wave::sunglasses: :enos_flag:

Are you able to test booting with the standard kernel?

Can you also share the output of:

yay -Q | grep -E 'nvidia|headers'

and

inxi -Fx --za

and share the link this produces to share you bootlog:

journalctl -k -b -0 | eos-sendlog

Hi @Bink, thank you so much for replying!

I’m using GRUB so I booted manually into endevourOS from the GRUB menu.

Output of yay -Q | grep -E 'nvidialheaders

linux-api-headers 6.10-1
linux-headers 6.12.1.arch1-1
linux-Its-headers 6.6.63-1
nvidia 565.57.01-8
nvidia-hook 1.5.1-1
nvidia-inst 24.10.2-2
nvidia-settings 565.57.01-1
nvidia utils 565.57.01-2
vulkan-headers 1:1.3.295-1

Output of inxi -Fx --za

API: EGL v: 1.5 drivers: iris, surast platforms: > active: gbm, surfaceless, device inactive: wayland, x11
API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 24.2.7-arch1.1 note: console (EGL sourced)
renderer: Mesa Intel UHD
API: Vulkan Message: No Vulkan data available.
Graphics 770 (ADL-S GT1), 11vmpipe (LLVM 18.1.8 255 bits)
Audio:
Device-1: Intel Alder Lake-S HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus-ID:
00:1f.3
Device-2: NVIDIA GA105 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus-ID: 01:00.1
Device-3: bus-ID:
Sony Wireless Headset driver: hid-generic,snd-usb-audio, usbhid type: USB
1-12:6
API: ALSA
v: k6.6.63-1-1ts status: kernel-api
Server-1: PipeWire v: 1.2.6 status: off
Network:
Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3
IF: wlanD state: up mac:
Device-2: Intel Ethernet 1225-V vendor: Micro-Star MSI driver: igc v: kernel port: N/A
bus-ID: 04:00.0
IF: enp4s0 state: down mac: ‹filter>
Device-3: Sony Wireless Headset driver: hid-generic, snd-usb-audio, usbhid type: USB bus-ID: 1-12:6
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB bus-ID: 1-14:8
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: disabled rfk-block: hardware: no software: no address: N/A
Drives:
Local Storage: total: 931.51 GiB used: 12.01 GiB (1.3%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN850X HS 1000GB size: 931.51 GiB
temp: 43.9 C
Partition:
ID-1: / size: 341.8 GiB used: 11.99 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p5
ID-2: /boot/efi size: 96 MiB used: 27.2 MiB (28.4%) fs: vfat dev: /dev/nvme0n1p1
ID-3: /home size: 341.8 GiB used: 11.99 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p5
ID-4: /var/log size: 341.8 GiB used: 11.99 GiB (3.5%) fs: btrfs dev: /dev/nvme0n1p5
Swap:
Alert: No suap data was found.
Sensors:
System Temperatures: cpu: 32.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 31.13 GiB used: 844.2 MiB (2.6%)
Processes: 337 Uptime: 1h 10m Init: systemd
Packages: 1070 Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.37 inxi: 3.3.36

Output of journalctl -k -b -0 | eos-sendlog: https://0x0.st/XRXu.txt

Thanks again!

The earlier parts of the inxi output are missing there, in particular the initial Graphics section.

Let’s try that part again:

inxi -MGz

As a side note, a number of BIOS updates have been released since your current version (“AF”).

https://www.msi.com/Motherboard/PRO-Z690-A-WIFI/support

For now, I would suggest addressing the Nvidia issue first though. Just something to consider for later.

Ok, I suspect the issue is pretty straight forward.

At the moment you have the nvidia driver installed, which is built specifically for the standard linux kernel.

However, you are running the linux-lts kernel, which would require the nvidia-lts driver, built for it. You don’t have that driver installed.

My recommendation is to instead install the nvidia-dkms driver. This one driver is able to integrate with any kernel, so long as you have the respective kernel headers installed. You’ve been able to confirm already you have your standard and lts kernel headers installed (linux-headers and linux-lts-headers), so all you should need to do now is:

sudo pacman -S nvidia-dkms

Let it complete the install, which will involve kernel integration (can take a bit of time). Then, restart the system. It should prompt you to replace/remove the existing nvidia driver.

3 Likes

Thank you so much you solved my issue! I had tried changing it to Nvidia-dkms before but I must have accidentally changed it back by accident when I was trouble shooting. Your the best!

1 Like

Ah, great news :smiley:

The nvidia-dkms driver will give you a bit more flexibility to switch kernels in case the need arises (kernel regression post update, etc).

The only real downside to the dkms driver, is any update to a kernel, or nvidia-dkms, will require that re-integration step that takes a bit of time as you probably noted.

1 Like

First off Planetwool, welcome to the forums! The people here are awesome! I do more lurking than I do posting, but I’ve really enjoyed the forums here. Friendliest bunch of people I have come across.

1 Like

Thank you! I can defiantly see that, people are very nice on here!