It might be more tricky than that. My (possibly incorrect) understanding is that the initial boot stuff is really outside of the install. So you might need to change something in livecd-creator and not just do stuff with the ks file. -- livecd mailing list livecd(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/livecd

> Absolutely, the initramfs needs to be copied to the /boot/ or /boot/isolinux > directory with the new theme that was created. Not sure how the current > livecd-tools does this, but this is true. The LiveCD needs to be able to > mount a SquashFS > filesystem and with that the kernel and initramfs or initrd are outside of > the Squashfiles. Okay, so I just extracted the two initrds (the one from the squashfs in /boot and the other from the actual usb key in /syslinux) and their files out. It looks like the plymouth theme itself is all present in both and also set in /etc/plymouth/plymouthd.conf as default. It's however not in /usr/share/plymouth/plymouthd.defaults, but doing a sed on that in %post didn't change the behaviour at all.

On Mon, Apr 26, 2010 at 4:24 PM, Ray Strode <rstrode(a)redhat.com&gt; wrote: > Hi, > >> > Absolutely, the initramfs needs to be copied to the /boot/ or /boot/isolinux >> > directory with the new theme that was created. Not sure how the current >> > livecd-tools does this, but this is true. The LiveCD needs to be able to >> > mount a SquashFS >> > filesystem and with that the kernel and initramfs or initrd are outside of >> > the Squashfiles. >> >> Okay, so I just extracted the two initrds (the one from the squashfs >> in /boot and the other from the actual usb key in /syslinux) and their >> files out. It looks like the plymouth theme itself is all present in >> both and also set in /etc/plymouth/plymouthd.conf as default. It's >> however not in /usr/share/plymouth/plymouthd.defaults, but doing a sed >> on that in %post didn't change the behaviour at all. > Must not be getting modesetting? > > add plymouth:debug to kernel command line and then look > at /var/log/plymouth-debug.log after boot up. > > --Ray It's getting interesting: http://fpaste.org/SONM/ Apparently, it tries to load the sugar theme first and moves on to charge and text. I'm not sure why this is, but maybe because of this line (69)? # [ply-boot-splash.c] ply_boot_splash_show:can't show splash: No such file or directory --Sebastian

From how I can currently see it, one needs to execute

Hi all, I'm scratching my head about this and have thrown already a good chunk of time into working on this, so I figured it might be reasonable to ask here, in case somebody had any ideas. We're working on getting a modified splash screen as before for Sugar on a Stick in time for the release (which is coming close, so I'm trying to get the done as soon as possible). The required package with the images and the plymouth file has been packaged long ago [1] and we're replacing the original theme in the kickstart file by now [2]. However, on a machine that boots both on F13 Beta and RHEL 6 Beta using the graphical boot screen, SoaS comes only up with the blue bar at the bottom - the %post part of the RPM file fails according to the logs, though [3]. Ray Strode suggested that this might be caused by the fact that the plymouth theme gets installed past the kernel in the build process, and that if this was the case, it'd be required to rebuild the initrd in %post. Turns out that sugar-logos actually gets installed past the kernel. But even after calling dracut in the kickstart's %post part, nothing changes. So. Does anybody have an idea how we can get the sugar-logos package installed *before* the kernel one? Or how we can get a working rebuild of the initrd into the spin? Any help to get this done in time would be really appreciated!

On Sun, Apr 25, 2010 at 8:26 PM, Jerry Vonau <jvonau(a)shaw.ca&gt; wrote: > On Sun, 2010-04-25 at 19:49 +0200, Sebastian Dziallas wrote: >> Hi all, >> >> I'm scratching my head about this and have thrown already a good chunk >> of time into working on this, so I figured it might be reasonable to >> ask here, in case somebody had any ideas. We're working on getting a >> modified splash screen as before for Sugar on a Stick in time for the >> release (which is coming close, so I'm trying to get the done as soon >> as possible). >> >> The required package with the images and the plymouth file has been >> packaged long ago [1] and we're replacing the original theme in the >> kickstart file by now [2]. However, on a machine that boots both on >> F13 Beta and RHEL 6 Beta using the graphical boot screen, SoaS comes >> only up with the blue bar at the bottom - the %post part of the RPM >> file fails according to the logs, though [3]. >> >> Ray Strode suggested that this might be caused by the fact that the >> plymouth theme gets installed past the kernel in the build process, >> and that if this was the case, it'd be required to rebuild the initrd >> in %post. Turns out that sugar-logos actually gets installed past the >> kernel. But even after calling dracut in the kickstart's %post part, >> nothing changes. >> >> So. Does anybody have an idea how we can get the sugar-logos package >> installed *before* the kernel one? Or how we can get a working rebuild >> of the initrd into the spin? Any help to get this done in time would >> be really appreciated! >> > plymouth has Requires: system-logos, perhaps you could provide > system-logos in your rpm, that should get it installed it before > plymouth, which is installed before the kernel. > > Jerry That's actually an interesting approach! I hadn't thought about this before. The sugar-logos package doesn't provide all the files the fedora-logos package does, so I guess one could list the fedora-logos one as a build requirement in the sugar-logos one and hope that it gets pulled in time then after making it provide system-logos... but I suppose we'd need to make sure that sugar-logos stayed out of the non-sugar spin composes.