Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#59423 - Kernel modules not loaded after Linux update
Attached to Project:
Arch Linux
Opened by Anonymous Submitter - Monday, 23 July 2018, 08:17 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 23 July 2018, 16:10 GMT
Opened by Anonymous Submitter - Monday, 23 July 2018, 08:17 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 23 July 2018, 16:10 GMT
|
DetailsDescription:
After an update to linux-4.17.8-1, modules loading is rejected (Failure in systemd-modules-load.service, crypto_user not found). Not even the mouse worked in the terminal window (Xfce starting manually, so being happy this time ...). After downgrading the kernel to 4.17.2-1 module loading works again. Additional info: - crypto_user is probably only used with bluez. - If the kernel is built with linux-headers-4.17.8-1, there's most probably an entry missing in .config: "CONFIG_CRYPTO_SALSA20_X86_64=m". Found no other related difference in config files. - For above, I compared /proc/config.gz from running 4.17.2 with those I manually downloaded for 4.17.8 (don't have a DKMS system, so no dependency on the headers). - I'm mostly just a linux user, so I cannot provide much helpful information, sorry. - A discussion about the same topic can be found on arch-general. Steps to reproduce: Run linux-4.17.8 with bluetooth (bluez). |
This task depends upon
CONFIG_CRYPTO_USER=m , CONFIG_CRYPTO_USER_API=m and CONFIG_CRYPTO_SALSA20_X86_64=m were present in all the config's of all the mentioned releases.
Last chance, what is `uname -a` when you update and reboot.
You only asked once, just for this "uname -a" after update. I won't update again to 4.17.8, as it corrupted my Linux installation completely, because modules didn't load, sorry. When sth. goes wrong, and especially if internet isn't working, I'm in "panic mode": I'm not using my PC only for playing, its use is essential for me for different purposes. Sticking now on 4.17.6.
BTW, I've been told in the thread that CONFIG_CRYPTO_SALSA20_X86_64 has been removed from the kernel. And when looking shortly at the source tree of bluez, I've noticed many module names with x86 - probably there's a direct dependency, but I cannot check it further. So this may be an upstream issue, but still I don't know and I'm not able to investigate this in deep.