[SOLVED] Failed to start Load Kernel Modules.

furycd001 · 2022-08-24 10:03:15

HI guys..

This morning I updated my system with pacman -Syyu. There was a kernel update installed & after the update had finished I found that the usb ports on the front of my computer had stopped working so decided to reboot. Upon rebooting I am greeted with a Failed to start Load Kernel Modules. error. I can login to other ttys & have tried reinstalling both linux & linux-firmware, but I'm still unable to access my desktop. I have the standard linux kernel installed along with nvidia-470 drivers. Here is the out for journalctl -b. Someone please help me please....

Last edited by furycd001 (2022-08-24 12:00:23)

furycd001 · 2022-08-24 10:08:38

Here is the output for systemctl status systemd-modules-load

Last edited by furycd001 (2022-08-24 10:24:26)

furycd001 · 2022-08-24 10:22:41

Thank you in advanced for reading & or replying it my thread....

Last edited by furycd001 (2022-08-24 10:24:18)

V1del · 2022-08-24 10:52:57

Please edit and ammend to the existing post if no one has replied yet to not unnecessarily bump the thread.

On kernel updates you need to rebuild your nvidia-470xx package against the new kernel, did you do that? This is easiest done by using nvidia-470xx-dkms which should automate this. if you think this to be the case what's your output for

sudo dkms status
pacman -Q linux linux-headers gcc nvidia-470xx
sudo lsinitcpio /boot/initramfs-linux.img | grep nvidia

Last edited by V1del (2022-08-24 11:02:52)

furycd001 · 2022-08-24 11:02:59

V1del wrote:

Please edit and ammend to the existing post if no one has replied yet to not unnecessarily bump the thread.
On kernel updates you need to rebuild your nvidia-470xx package against the new kernel, did you do that? This is easiest done by using nvidia-470xx-dkms which should automate this. if you think this to be the case what's your output for
sudo dkms status
pacman -Q linux linux-headers gcc nvidia-470xx

Sorry about that. I was just freaking out a little. I'm pretty sure that the nvidia package was rebuilt, because I have the nvidia-470xx-dkms installed & I also have the hook set up. Kernel updates have never been a problem until this morning. Whenever I run sudo dkms status I can see the following....

nvidia 470.141.03, 5.19.3-arch1-1, x86-64: installedError! Could not locate dkms.conf file.

Last edited by furycd001 (2022-08-24 11:03:40)

dogknowsnx · 2022-08-24 11:03:44

btw

furycd001 · 2022-08-24 11:06:40

dogknowsnx wrote:

btw

Thanks for the link. I usually just run -syu but occasionally add the extra y....

Here is the output for sudo lsinitcpio /boot/initramfs-linux.img | grep nvidia

Last edited by furycd001 (2022-08-24 11:27:50)

Scimmia · 2022-08-24 11:31:35

"failed to validate module [nvidia] BTF: -22"

We did some troubleshooting on this last night. Best we could come up with is there's a toolchain issue, possibly building on older systems. What CPU do you have?

Only workaround we came up with was using binary modules built on a newer system. With nvidia-dkms, that meant switching to nvidia/nvidia-lts. One other guy using nvidia 470 was able to copy the modules from another, newer system onto the older one that wasn't working.

furycd001 · 2022-08-24 11:37:18

Scimmia wrote:

"failed to validate module [nvidia] BTF: -22"
We did some troubleshooting on this last night. Best we could come up with is there's a toolchain issue, possibly building on older systems. What CPU do you have?
Only workaround we came up with was using binary modules built on a newer system. With nvidia-dkms, that meant switching to nvidia/nvidia-lts. One other guy using nvidia 470 was able to copy the modules from another, newer system onto the older one that wasn't working.

Here is my cpuinfo. I'm running on a Dell optiplex 7010. I don't have access to any other computers that are running either Linux or Nvidia. Is there anything I can do without having to switch to another distro like Debian or Fedora ?? Could I maybe even rollback the necessary packages & then hold them to stop them from being updated ??

Last edited by furycd001 (2022-08-24 11:39:48)

Scimmia · 2022-08-24 11:42:33

i5-3470 is significantly newer than the systems we were troubleshooting, but still older than the Haswell the one person used to build good modules. The age of the system was a theory, don't know if it'll hold up or not.

There's someone on reddit that says that stripping out the BTF info works, you can try that. https://www.reddit.com/r/archlinux/comm … x_gcc_122/

furycd001 · 2022-08-24 11:44:30

Scimmia wrote:

i5-3470 is significantly newer than the systems we were troubleshooting, but still older than the Haswell the one person used to build good modules. The age of the system was a theory, don't know if it'll hold up or not.
There's someone on reddit that says that stripping out the BTF info works, you can try that. https://www.reddit.com/r/archlinux/comm … x_gcc_122/

Thank you so much for replying with all of this info. I'm going to try stripping out the BTF info now, because I'd like to get my system booting again. Will let you know if it works or not....

Last edited by furycd001 (2022-08-24 11:44:48)

furycd001 · 2022-08-24 11:57:49

Ok so OMFG I'm so unbelievably happy right now. Stripping out the BTF info actually worked. I'm now booted back into my desktop once again. Thank you so, so, so much for helping me. One final question before I mark the thread as solved. I take it that going forward from here I need to strip out the BTF info every time I update the nvidia package ??

Scimmia · 2022-08-24 11:58:54

Until the bug is found and fixed, you'd have to do it every time the modules are rebuilt; that's every kernel update and every nvidia update.

furycd001 · 2022-08-24 12:00:07

Scimmia wrote:

Until the bug is found and fixed, you'd have to do it every time the modules are rebuilt; that's every kernel update and every nvidia update.

Ok I thought as much. Thank you again for helping....

9numbernine9 · 2022-08-24 12:01:36

Scimmia wrote:

i5-3470 is significantly newer than the systems we were troubleshooting, but still older than the Haswell the one person used to build good modules. The age of the system was a theory, don't know if it'll hold up or not.
There's someone on reddit that says that stripping out the BTF info works, you can try that. https://www.reddit.com/r/archlinux/comm … x_gcc_122/

Heya! That was me. I made this account just to follow along and see if anyone else was running into this issue.

furycd001 wrote:

Ok so OMFG I'm so unbelievably happy right now. Stripping out the BTF info actually worked. I'm now booted back into my desktop once again. Thank you so, so, so much for helping me.

Glad my silly hack was able to help someone! I'm going to raise an official bug about this because I think something is going on.

furycd001 · 2022-08-24 12:06:04

9numbernine9 wrote:

Scimmia wrote:
i5-3470 is significantly newer than the systems we were troubleshooting, but still older than the Haswell the one person used to build good modules. The age of the system was a theory, don't know if it'll hold up or not.
There's someone on reddit that says that stripping out the BTF info works, you can try that. https://www.reddit.com/r/archlinux/comm … x_gcc_122/
Heya! That was me. I made this account just to follow along and see if anyone else was running into this issue.
furycd001 wrote:
Ok so OMFG I'm so unbelievably happy right now. Stripping out the BTF info actually worked. I'm now booted back into my desktop once again. Thank you so, so, so much for helping me.
Glad my silly hack was able to help someone! I'm going to raise an official bug about this because I think something is going on.

You are a frikin genius my friend. I can't thank you enough for this hack or whatever it is. It got my computer booting again & I'm literally so happy. Yes, yes you should definitely open up a bug report because I'm sure I'm not the only person who will encounter whatever this is....

9numbernine9 · 2022-08-24 12:24:04

furycd001 wrote:

You are a frikin genius my friend. I can't thank you enough for this hack or whatever it is. It got my computer booting again & I'm literally so happy. Yes, yes you should definitely open up a bug report because I'm sure I'm not the only person who will encounter whatever this is....

Not a genius, just extremely stubborn.

I've raised this bug to see if it gets any traction: https://bugs.archlinux.org/task/75685

Ashren · 2022-08-24 12:24:37

@9numbernine9
Thanks for the workaround!

I'd like report that I am also seeing the problem with nvidia-470xx-dkms.

Scimmia · 2022-08-24 12:50:09

heftig seems sure this is related to the pahole update and has rolled it back. Testing would be very welome.

9numbernine9 · 2022-08-24 12:51:35

Scimmia wrote:

heftig seems sure this is related to the pahole update and has rolled it back. Testing would be very welome.

I can confirm that rolling back pahole does seem to at least work around the issue for now.

Ashren · 2022-08-24 13:00:10

I can confirm that downgrading pahole fixes the problem.

9numbernine9 · 2022-08-24 13:02:54

Update: It looks like pahole 1.24-1 has been replaced with 1:1.23-1 in some mirrors so far, so everyone should automatically get a working version in the near future.

Last edited by 9numbernine9 (2022-08-24 13:06:26)

peppetunz · 2022-08-24 13:03:17

Hello,
I kinda am in the same situation, I updated kernel and nvidia drivers as always but this time nvidia kernel module does not load and I'm not able to startx anymore.
Here are some logs:
Pkgs versions:

linux-lts 5.15.62-1
linux-lts-headers 5.15.62-1
nvidia-470xx-dkms 470.141.03-1
gcc 12.2.0-1

Output of sudo dkms status:

nvidia/470.141.03, 5.15.62-1-lts, x86_64: installed

Output of sudo lsinitcpio /boot/initramfs-linux.img | grep nvidia:

usr/lib/modprobe.d/nvidia-470xx-utils.conf

Xorg.0.log:

[    63.557] 
X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
[    63.557] Current Operating System: Linux fisso-arch 5.15.62-1-lts #1 SMP Sun, 21 Aug 2022 18:43:48 +0000 x86_64
[    63.557] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=2d9b8549-aa5f-4593-9b59-99af2016bb56 rw loglevel=3 quiet lsm=landlock,lockdown,yama,apparmor,bpf
[    63.557]  
[    63.557] Current version of pixman: 0.40.0
[    63.557] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    63.557] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    63.557] (==) Log file: "/home/marco/.local/share/xorg/Xorg.0.log", Time: Wed Aug 24 13:57:56 2022
[    63.560] (==) Using config file: "/etc/X11/xorg.conf"
[    63.560] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    63.560] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    63.561] (==) No Layout section.  Using the first Screen section.
[    63.561] (==) No screen section available. Using defaults.
[    63.561] (**) |-->Screen "Default Screen Section" (0)
[    63.561] (**) |   |-->Monitor "<default monitor>"
[    63.561] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[    63.561] (**) |   |-->Device "Device0"
[    63.561] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    63.561] (==) Automatically adding devices
[    63.561] (==) Automatically enabling devices
[    63.561] (==) Automatically adding GPU devices
[    63.561] (==) Automatically binding GPU devices
[    63.561] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    63.562] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    63.562] 	Entry deleted from font path.
[    63.563] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF,
	/usr/share/fonts/OTF,
	/usr/share/fonts/100dpi,
	/usr/share/fonts/75dpi
[    63.563] (==) ModulePath set to "/usr/lib/xorg/modules"
[    63.563] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    63.563] (II) Module ABI versions:
[    63.563] 	X.Org ANSI C Emulation: 0.4
[    63.563] 	X.Org Video Driver: 25.2
[    63.563] 	X.Org XInput driver : 24.4
[    63.563] 	X.Org Server Extension : 10.0
[    63.564] (++) using VT number 1

[    63.564] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    63.565] (II) xfree86: Adding drm device (/dev/dri/card0)
[    63.565] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[    63.565] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0
[    63.567] (--) PCI: (0@0:2:0) 8086:0412:1849:0412 rev 6, Mem @ 0xeb400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
[    63.567] (--) PCI:*(1@0:0:0) 10de:1184:1458:3603 rev 161, Mem @ 0xea000000/16777216, 0xe0000000/134217728, 0xe8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[    63.567] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    63.567] (II) LoadModule: "glx"
[    63.567] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    63.573] (II) Module glx: vendor="X.Org Foundation"
[    63.573] 	compiled for 1.21.1.4, module version = 1.0.0
[    63.573] 	ABI class: X.Org Server Extension, version 10.0
[    63.573] (II) LoadModule: "nvidia"
[    63.573] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    63.577] (II) Module nvidia: vendor="NVIDIA Corporation"
[    63.577] 	compiled for 1.6.99.901, module version = 1.0.0
[    63.577] 	Module class: X.Org Video Driver
[    63.577] (II) NVIDIA dlloader X Driver  470.141.03  Thu Jun 30 18:40:44 UTC 2022
[    63.577] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    63.578] xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted)
[    63.578] (II) Loading sub module "fb"
[    63.578] (II) LoadModule: "fb"
[    63.578] (II) Module "fb" already built-in
[    63.578] (II) Loading sub module "wfb"
[    63.578] (II) LoadModule: "wfb"
[    63.578] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    63.579] (II) Module wfb: vendor="X.Org Foundation"
[    63.579] 	compiled for 1.21.1.4, module version = 1.0.0
[    63.579] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    63.579] (II) Loading sub module "ramdac"
[    63.579] (II) LoadModule: "ramdac"
[    63.579] (II) Module "ramdac" already built-in
[    63.917] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[    63.917] (EE) NVIDIA:     system's kernel log for additional error messages and
[    63.917] (EE) NVIDIA:     consult the NVIDIA README for details.
[    63.917] (EE) No devices detected.
[    63.917] (EE) 
Fatal server error:
[    63.917] (EE) no screens found(EE) 
[    63.917] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    63.917] (EE) Please also check the log file at "/home/marco/.local/share/xorg/Xorg.0.log" for additional information.
[    63.917] (EE) 
[    63.923] (EE) Server terminated with error (1). Closing log file.

Scimmia wrote:

There's someone on reddit that says that stripping out the BTF info works, you can try that. https://www.reddit.com/r/archlinux/comm … x_gcc_122/

Should I try the same workaround?

Scimmia · 2022-08-24 13:11:48

No, you update pahole, which downgrades it and appears to fix the problem.

peppetunz · 2022-08-24 13:25:17

Scimmia wrote:

No, you update pahole, which downgrades it and appears to fix the problem.

Yep, working.

Arch Linux

#1 2022-08-24 10:03:15

[SOLVED] Failed to start Load Kernel Modules.

#2 2022-08-24 10:08:38

Re: [SOLVED] Failed to start Load Kernel Modules.

#3 2022-08-24 10:22:41

Re: [SOLVED] Failed to start Load Kernel Modules.

#4 2022-08-24 10:52:57

Re: [SOLVED] Failed to start Load Kernel Modules.

#5 2022-08-24 11:02:59

Re: [SOLVED] Failed to start Load Kernel Modules.

#6 2022-08-24 11:03:44

Re: [SOLVED] Failed to start Load Kernel Modules.

#7 2022-08-24 11:06:40

Re: [SOLVED] Failed to start Load Kernel Modules.

#8 2022-08-24 11:31:35

Re: [SOLVED] Failed to start Load Kernel Modules.

#9 2022-08-24 11:37:18

Re: [SOLVED] Failed to start Load Kernel Modules.

#10 2022-08-24 11:42:33

Re: [SOLVED] Failed to start Load Kernel Modules.

#11 2022-08-24 11:44:30

Re: [SOLVED] Failed to start Load Kernel Modules.

#12 2022-08-24 11:57:49

Re: [SOLVED] Failed to start Load Kernel Modules.

#13 2022-08-24 11:58:54

Re: [SOLVED] Failed to start Load Kernel Modules.

#14 2022-08-24 12:00:07

Re: [SOLVED] Failed to start Load Kernel Modules.

#15 2022-08-24 12:01:36

Re: [SOLVED] Failed to start Load Kernel Modules.

#16 2022-08-24 12:06:04

Re: [SOLVED] Failed to start Load Kernel Modules.

#17 2022-08-24 12:24:04

Re: [SOLVED] Failed to start Load Kernel Modules.

#18 2022-08-24 12:24:37

Re: [SOLVED] Failed to start Load Kernel Modules.

#19 2022-08-24 12:50:09

Re: [SOLVED] Failed to start Load Kernel Modules.

#20 2022-08-24 12:51:35

Re: [SOLVED] Failed to start Load Kernel Modules.

#21 2022-08-24 13:00:10

Re: [SOLVED] Failed to start Load Kernel Modules.

#22 2022-08-24 13:02:54

Re: [SOLVED] Failed to start Load Kernel Modules.

#23 2022-08-24 13:03:17

Re: [SOLVED] Failed to start Load Kernel Modules.

#24 2022-08-24 13:11:48

Re: [SOLVED] Failed to start Load Kernel Modules.

#25 2022-08-24 13:25:17

Re: [SOLVED] Failed to start Load Kernel Modules.

Board footer