Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document uninstalling #11

Open
besendorf opened this issue Jan 10, 2020 · 4 comments
Open

Document uninstalling #11

besendorf opened this issue Jan 10, 2020 · 4 comments

Comments

@besendorf
Copy link

Hi,
I uninstalled go-luks-suspend with yay -R go-luks-suspend but when I try to update the kernel now the suspend module cant be found

(6/9) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.4.10-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
  -> Running build hook: [shutdown]
==> ERROR: Hook 'suspend' cannot be found
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.4.10-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
  -> Running build hook: [shutdown]
==> ERROR: Hook 'suspend' cannot be found
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
Fehler: Befehl konnte nicht korrekt ausgeführt werden
@Maryse47
Copy link

suspend module is part of go-luks-suspend so obviously you can't use it after package removal.

@Patola
Copy link

Patola commented Mar 28, 2022

suspend module is part of go-luks-suspend so obviously you can't use it after package removal.

I think his point is that the hook should be removed in the post-uninstall scripts, no?

@Maryse47
Copy link

As long as there is post-install script that adds this hook, yes. But there is no such script. Adding the hook is manual process done by user therefore removing hook manually is logical and consistent step. keep in mind that manipulating mkinitcpio.conf automatically would be error prone with risk of locking out user from system on next boot. No tool in Arch does this.

@Patola
Copy link

Patola commented Mar 29, 2022

Indeed, it's sensible that it's this way then. Thanks for the explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants