Re: New Plymouth does not render in VMware framebuffer
Here are more details of my configuration, this is using a custom
3.16.3 kernel which purposefully does not include the kms or drm
drivers.
Here's a screenshot with plymouth:debug because journalctl -b , and
/var/log/plymouth-debug.log only show after this, this is the first
time the init script in the ramdisk tries to run plymouthd
http://picpaste.com/pics/Windows_7-2015-01-06-21-00-26-8VPNU56H.1420599718.png
and some Grub 2 config parts
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
set gfxmode=1024x768
insmod gfxterm
terminal_output gfxterm
insmod png
background_image /boot/splash1024x768.png
set gfxpayload=keep
linux /live/vmlinuz boot=live config noeject nonetworking toram quiet
splash pci=nommconf,nocrs video=uvesafb:1024x768 loglevel=0
plymouth:splash=en
On Tue, Jan 6, 2015 at 8:36 PM, Aaron McSorley <a@aaronmcsorley.com> wrote:
> The Wheezy version of Plymouth (0.8.5.1-5) renders themes without
> issue on the VMware framebuffer but, on the new version with Jessie
> (0.9.0-9) plymouthd seems to crash when the ramdisk scripts try to run
> the daemon. I've tried to get some useful debug by adding --debug to
> plymouth and plymouthd in the ramdisk, as well as plymouth:debug on
> the kernel line but, it's not very helpful. The only way I could find
> to confirm this, was to manually replace the plymouth binaries and
> libraries in the initramfs with the old ones from Wheezy. So, using
> the same kernel, and only replacing the plymouth binaries and
> libraries in the ramdisk that was generated in Jessie it renders
> properly. The new version renders on the real hardware I've tested it
> on but, I'd really like to be able to test my plymouth theme in a VM.
> Does anyone know what might have changed between these version that
> would break compatibility with VMware?
Reply to: