Search Criteria
Package Details: plymouth-zfs 3-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/plymouth-zfs.git (read-only, click to copy) |
---|---|
Package Base: | plymouth-zfs |
Description: | initcpio hook to support native zfs encryption for plymouth |
Upstream URL: | None |
Licenses: | MIT |
Submitter: | minextu |
Maintainer: | raze_lighter777c |
Last Packager: | raze_lighter777c |
Votes: | 3 |
Popularity: | 0.000000 |
First Submitted: | 2017-07-10 23:52 (UTC) |
Last Updated: | 2021-07-21 21:59 (UTC) |
Dependencies (7)
- plymouth (plymouth-gitAUR)
- ttf-dejavu (ttf-dejavu-ibAUR, ttf-dejavu-emojilessAUR)
- zfs-dkms-gitAUR (optional) – support for all kernels using dkms
- zfs-linux-gitAUR (optional) – support for the default linux kernel
- zfs-linux-hardened-git (optional) – support for the hardened kernel
- zfs-linux-lts-git (optional) – support for the lts kernel
- zfs-linux-zen-git (optional) – support for the zen kernel
Latest Comments
« First ‹ Previous 1 2
W00PIE commented on 2019-11-02 15:39 (UTC)
@ColinMT: That fixed it, thanks!
ColinMT commented on 2019-11-02 15:09 (UTC)
@WOOPIE, I think you need to add the regular plymouth hook before the plymouth-zfs hook in order for plymouth itself to be included in the initramfs. Change your hooks line to this: HOOKS=(base udev autodetect modconf block keyboard plymouth plymouth-zfs filesystems fsck) and see if it works. Hope this helps.
W00PIE commented on 2019-11-02 14:37 (UTC) (edited on 2019-11-02 14:38 (UTC) by W00PIE)
I've just set up a fresh system running 5.3.8-arch1-1 with native ZFS encryption and systemd-boot. Without plymouth, I can enter my passphrase on boot and everything works. Following https://wiki.archlinux.org/index.php/plymouth, I then installed plymouth-zfs, changed the zfs hook to plymouth-zfs, added "quiet splash loglevel=3 rd.udev.log_priority=3 vt.global_cursor_default=0" to my boot loader entry in /boot/loader/entries/archcrypt.conf and ran "mkinitcpio -p linux", which threw an error (see ColinMT's comment below). I also enable lightdm-plymouth.
On reboot, I ended up in an error loop and kernel panic just as jpbd writes: init: line 44: plymouth:not found. I'm using zfs-dkms and have an integrated Intel graphics (works flawlessly with lightdm/mate). Pure UEFI boot selected in my BIOS.
What can I do to make plymouth.zfs work? Do I have to change the order of my mkinitcpio hooks? Here's my current config: HOOKS=(base udev autodetect modconf block keyboard plymouth-zfs filesystems fsck).
ColinMT commented on 2019-06-23 21:10 (UTC)
@minextu please change arcstat.py and dbufstat.py to simply arcstat and dbufstat in the map add_binary section of the plymouth-zfs.initcpio.install file to prevent initcpio errors when generating the boot image using this hook.
Thank you.
patrickh commented on 2017-11-12 01:46 (UTC)
minextu commented on 2017-11-10 15:40 (UTC)
patrickh commented on 2017-11-10 15:26 (UTC)
minextu commented on 2017-08-29 12:52 (UTC)
jpbd commented on 2017-08-29 12:47 (UTC)
« First ‹ Previous 1 2