question about kernel update

rican-linux · 2017-06-16 19:33:18

Yesterday I updated my system and my kernel was updated. I rebooted and the kernel will not load. I googled the error (I wish I kept the error) and found that running mkinitcpio -p linux fixed my issue. So my question is should I run this command every time I update the kernel?

loqs · 2017-06-16 19:45:57

No as the pacman hook /usr/share/libalpm/hooks/90-linux.hook should perform that action automatically.

rican-linux · 2017-06-16 21:48:42

ok thanks!

WFV · 2017-06-18 04:31:12

rican-linux wrote:

running mkinitcpio -p linux fixed my issue. So my question is should I run this command every time I update the kernel?

I do it after every kernel update because pacman always complains about dkms permissions. It's probably something I have set up wrong, but haven't taken time to figure out. Quicker to run that command after -Syu completes than having to chroot boot to do it.
EDIT: this seems to resolve the pacman permissions

/usr/share/libalpm/hooks.bin # chmod +x dkms-remove
/usr/share/libalpm/hooks.bin # chmod +x dkms-install

Last edited by WFV (2017-06-18 15:12:20)

eschwartz · 2017-06-18 21:35:23

WFV wrote:

I do it after every kernel update because pacman always complains about dkms permissions. It's probably something I have set up wrong, but haven't taken time to figure out. Quicker to run that command after -Syu completes than having to chroot boot to do it.
EDIT: this seems to resolve the pacman permissions
/usr/share/libalpm/hooks.bin # chmod +x dkms-remove
/usr/share/libalpm/hooks.bin # chmod +x dkms-install

Well, sure. That is a completely different matter entirely, and has nothing to do with this thread; pacman runs dkms before running the mkinitcpio hook, but for some reason the dkms package installed the hooks and helper scripts and then those helper scripts got modified to remove their executable bit. Which caused the dkms hooks to fail, and mkinitcpio ran without adding the dkms-built modules...

Which presumably meant you had to then run dkms by hand, and then update your initcpio by hand to match.

...

"complains about dkms permissions" is a very vague error, I bet if you had posted the error here it would turn out to have an obvious meaning which would not require you to chroot boot in order to debug.

Last edited by eschwartz (2017-06-18 21:36:26)

WFV · 2017-06-19 03:15:51

Eschwartz wrote:

Well, sure. That is a completely different matter entirely, and has nothing to do with this thread; pacman runs dkms before running the mkinitcpio hook, but for some reason the dkms package installed the hooks and helper scripts and then those helper scripts got modified to remove their executable bit. Which caused the dkms hooks to fail, and mkinitcpio ran without adding the dkms-built modules...
Which presumably meant you had to then run dkms by hand, and then update your initcpio by hand to match.
...
"complains about dkms permissions" is a very vague error, I bet if you had posted the error here it would turn out to have an obvious meaning which would not require you to chroot boot in order to debug.

The error message did as you said point to the obvious meaning:

[2017-05-28 16:16] [PACMAN] starting full system upgrade
[2017-05-28 16:16] [ALPM] running '70-dkms-remove.hook'...
[2017-05-28 16:16] [ALPM-SCRIPTLET] ==> dkms remove sysdig/0.16.0 -k 4.9.29-1-lts
[2017-05-28 16:16] [ALPM] running 'dkms-remove.hook'...
[2017-05-28 16:16] [ALPM-SCRIPTLET] call to execv failed (Permission denied)
[2017-05-28 16:16] [ALPM] transaction started
[2017-05-28 16:16] [ALPM] upgraded linux-lts (4.9.29-1 -> 4.9.30-1)
[2017-05-28 16:16] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2017-05-28 16:17] [ALPM] upgraded linux-lts-docs (4.9.29-1 -> 4.9.30-1)
[2017-05-28 16:17] [ALPM] upgraded linux-lts-headers (4.9.29-1 -> 4.9.30-1)
[2017-05-28 16:17] [ALPM] upgraded python2-incremental (16.10.1-2 -> 17.5.0-1)
[2017-05-28 16:17] [ALPM] upgraded vlc (2.2.5.1-1 -> 2.2.6-1)
[2017-05-28 16:17] [ALPM] transaction completed
[2017-05-28 16:17] [ALPM] running '70-dkms-install.hook'...
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> dkms install sysdig/0.16.0 -k 4.9.30-1-lts
[2017-05-28 16:17] [ALPM] running '90-linux-lts.hook'...
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'default'
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Starting build: 4.9.30-1-lts
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts.img
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Image generation successful
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: 'fallback'
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Starting build: 4.9.30-1-lts
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2017-05-28 16:17] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
[2017-05-28 16:17] [ALPM-SCRIPTLET] ==> Image generation successful
[2017-05-28 16:17] [ALPM] running 'dkms-install.hook'...
[2017-05-28 16:17] [ALPM-SCRIPTLET] call to execv failed (Permission denied)

and I hadn't done anything about it until today (which has nothing to do with the thread). Pacman logs show they stopped working 3/6 with a dkms update. So first time this same thing the OP mentioned happened to me (upgrading linux 4.9 to 10 I think it was) and I had to chroot as the OP did, after that until today i ran mkinitcpio -P by hand (linux & linux-lts) as you mentioned.

EDIT: reset them back to 644 as found, is a different problem, not done troubleshooting
EDIT: dkms errors https://bugs.archlinux.org/task/54481 https://github.com/dell/dkms/commit/f5b … a98d4e6aa8 https://www.reddit.com/r/archlinux/comm … _updating/
making the hooks 744 resulted in no dkms errors but stops "systemd-modules-load" which a reboot restores, kernel update needs a reboot anyway, so for now ignoring the error and manual re-running mkinitcpio -P after update and reboot averts having to do what the OP did in #1.

Last edited by WFV (2017-06-25 23:00:23)

Arch Linux

#1 2017-06-16 19:33:18

question about kernel update

#2 2017-06-16 19:45:57

Re: question about kernel update

#3 2017-06-16 21:48:42

Re: question about kernel update

#4 2017-06-18 04:31:12

Re: question about kernel update

#5 2017-06-18 21:35:23

Re: question about kernel update

#6 2017-06-19 03:15:51

Re: question about kernel update

Board footer