summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXiao Pan <gky44px1999@gmail.com>2024-02-26 21:33:33 -0800
committerXiao Pan <gky44px1999@gmail.com>2024-02-26 21:33:33 -0800
commit4ac38f592f88e42583b2313892e1b9e7a3f55bd4 (patch)
treec8c4ea588a76197b6cfc0121fc86fc05cdf1e79c
parent6f09dfc8103ca7515d33e9ace140f0265fd71aa7 (diff)
dirty workaround to mkinitcpio when linux-megi upgrade
-rw-r--r--etc/pacman.d/hooks/linux-megi-mkinitcpio.hook16
1 files changed, 16 insertions, 0 deletions
diff --git a/etc/pacman.d/hooks/linux-megi-mkinitcpio.hook b/etc/pacman.d/hooks/linux-megi-mkinitcpio.hook
new file mode 100644
index 00000000..24d44ab7
--- /dev/null
+++ b/etc/pacman.d/hooks/linux-megi-mkinitcpio.hook
@@ -0,0 +1,16 @@
+# Sometimes after linux-megi upgrade, reboot results into osk-sdl errors so I can't decrypt FDE.
+# Maybe it is because linux-megi does not have `/usr/lib/modules/*/vmlinuz`, this cause /usr/share/libalpm/hooks/90-mkinitcpio-install.hook to not run when linux-megi upgrade, which cause mkinitcpio not run.
+# Also, 90-linux-megi.hook does not set linux-megi as target and it seems cause it not running when linux-megi upgrade.
+# I'm not sure what's the cause of the issue. This pacman hook is just a dirty workaround, because it may cause mkinitcpio run twice.
+[Trigger]
+Type = Package
+Operation = Install
+Operation = Upgrade
+Target = linux-megi
+
+[Action]
+Description = My workaround to mkinitcpio after linux-megi upgrade...
+When = PostTransaction
+Exec = /usr/bin/mkinitcpio -P
+Depends = linux-megi
+