plymouth working for anybody with F-11?
Is plymouth working for anyone with F-11 right now?
In my case it seems to fail to load the KMS kernel module (intel.ko in my case) prior to plymouth splash is executed.
Warren
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 5 lines · Warren Togami
Is plymouth working for anyone with F-11 right now?
In my case it seems to fail to load the KMS kernel module (intel.ko in my case) prior to plymouth splash is executed.
Another problem is it seems to still use default.so.
[[ -f ${LIBDIR}/plymouth/default.so ]] && inst ${LIBDIR}/plymouth/default.so
The plymouth in F-11 seems to no longer use the default.so symlink. It seems to be copying the default "charge" theme into the image, but without the required two-step.so plugin.
BTW, why are we using our own plymouth-populate-initrd instead of using plymouth's own /usr/libexec/plymouth/plymouth-populate-initrd, which presumably would do the right thing for its own version of plymouth? (Didn't try it yet.)
Warren Togami
[email protected]
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 12 lines · Warren Togami
Quoted 5 lines · Warren Togami
Is plymouth working for anyone with F-11 right now?
In my case it seems to fail to load the KMS kernel module (intel.ko in my case) prior to plymouth splash is executed.
Another problem is it seems to still use default.so.
[[ -f ${LIBDIR}/plymouth/default.so ]] && inst
${LIBDIR}/plymouth/default.so
Quoted 8 lines
The plymouth in F-11 seems to no longer use the default.so symlink. It seems to be copying the default "charge" theme into the image, but without the required two-step.so plugin.
BTW, why are we using our own plymouth-populate-initrd instead of using plymouth's own
/usr/libexec/plymouth/plymouth-populate-initrd, which presumably would do the right thing for its own version of plymouth? (Didn't try it yet.)
/usr/libexec/plymouth/plymouth-populate-initrd should/will be fixed to use dracut syntax and will be used, as soon as dracut replaces mkinitrd. --
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 11 lines · Warren Togami
Quoted 5 lines · Warren Togami
Is plymouth working for anyone with F-11 right now?
In my case it seems to fail to load the KMS kernel module (intel.ko in my case) prior to plymouth splash is executed.
Another problem is it seems to still use default.so.
[[ -f ${LIBDIR}/plymouth/default.so ]] && inst ${LIBDIR}/plymouth/default.so
Quoted 8 lines
The plymouth in F-11 seems to no longer use the default.so symlink. It seems to be copying the default "charge" theme into the image, but without the required two-step.so plugin.
BTW, why are we using our own plymouth-populate-initrd instead of using plymouth's own
/usr/libexec/plymouth/plymouth-populate-initrd, which presumably would do the right thing for its own version of plymouth? (Didn't try it yet.)
Because the original plymouth-populate-initrd script was full of useless (to dracut) code that our internal inst functions handled better and in a more generic fashion, so I trimmed it down to its essentials.
Quoted 6 lines
Warren Togami
[email protected]
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 8 lines
Victor Lowther RHCE# 805008539634727 LPIC-2# LPI000140019 -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html