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#59276 - kernel doesn't update itself version after updating to 4.17.4-1
Attached to Project:
Arch Linux
Opened by AskseL (AskseL) - Monday, 09 July 2018, 06:32 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 09 July 2018, 06:48 GMT
Opened by AskseL (AskseL) - Monday, 09 July 2018, 06:32 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 09 July 2018, 06:48 GMT
|
DetailsDescription:
After update linux package to 4.17.4-1 and rebuild kernel images in /boot directory, it didn't update itself. After reboot and executing uname -r i got 4.17.3-1-ARCH, but kernel modules in /lib/modules dir are stored in /lib/modules/4.17.4-1-ARCH directory and error occured. Renaming /lib/modules/4.17.4-1-ARCH into /lib/modules/4.17.3-1-ARCH solves the issue. Steps to reproduce: 1. Update kernel from 4.17.3-1-ARCH to 4.17.4-1-ARCH 2. Reboot 3. Get errors while starting system. kernel refers to wrong dir |
This task depends upon
Comment by Christian Hesse (eworm) -
Monday, 09 July 2018, 06:39 GMT
Something is broken on your system. I guess you updated while /boot partition was not mounted and boot the old kernel from boot partition. (Or vice verse... The kernel was installed to /boot partition and you boot an old kernel from your root partition.)
Снимок экрана от 2018-07-09 0...