Package Details: plymouth-zfs 3-1

Git Clone URL: (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: 2
Popularity: 0.100992
First Submitted: 2017-07-10 23:52
Last Updated: 2021-02-25 20:21

Dependencies (7)

Required by (0)

Sources (3)

Latest Comments

1 2 Next › Last »

tessaracht commented on 2021-06-14 10:12

I definitely just got bit by that mount handler bug. @raze_lighter777c, any chance we could get that fix merged?

vvlad commented on 2021-05-23 10:27

Hi, thanks for updating this.

There's an issue in the hook, however: it doesn't ignore filesystems with canmount=off.

The issue is in function zfs_mount_handler, starting line 83:

I've made a fork of this inspired by the hooks from the base archzfs package, for comparison:

raze_lighter777c commented on 2021-02-25 20:22

Note to all lightdm users: Please disable lightdm.service and enable plymouth-lightdm.service.

This will fix booting and flickering issues.

raze_lighter777c commented on 2021-02-21 19:13

Yo I'm gonna claim this package and submit some fixes.

owendaprile commented on 2020-10-13 00:16

I think ttf-dejavu should be listed as a dependency, as the hook tries to add it to the initramfs, causing an error if not installed.

joshuarubin commented on 2020-07-16 21:59

Has this package been abandoned? The required fix to change to arcstat and to dbufstat still hasn't been included.

W00PIE commented on 2019-11-02 15:39

@ColinMT: That fixed it, thanks!

ColinMT commented on 2019-11-02 15:09

@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

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, 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

@minextu please change and 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.