geninitrd: --with-bootsplash causes kernel panic with initramfs
Bug #368264 reported by
vip
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PLD Linux |
New
|
Undecided
|
Elan Ruusamäe |
Bug Description
When generating initramfs geninitrd with bootsplash the kernel is in panic with unknown rootfs.
Same initrd without --with-bootsplash works well.
Following <shadzik>, with initramfs (default in pld):
bootsplash should be generated, named bootsplash, copied to initramfs' rootdir and finally, generated initramfs
e.g.
/bin/splash.bin -s -f /etc/bootsplash
and then find . | cpio stuff
To post a comment you must log in.
dude, where's the version?!
anyway in mod-bootsplash.sh there are lines:
for res in $BOOT_SPLASH_ RESOLUTIONS; do h/themes/ $THEME/ config/ bootsplash- $res.cfg" ]; then
/bin/ splash. bin -s -f "/etc/bootsplas h/themes/ $THEME/ config/ bootsplash- $res.cfg" >> "$target" && \ h/themes/ $THEME/ config/ bootsplash- $res.cfg doesn't exist, skipped"
if [ -f "/etc/bootsplas
debug "Added $res $THEME theme to initrd."
else
warn "/etc/bootsplas
fi
done
and $target being the final .gz file.
nevertheless, regenerate initrd with -v option and show the output.