Tested Oliver's suggestion and indeed it does work if the overlay is removed but I assume that the overlay is there for a reason. Furthermore, extracting the psplash binary from the psplash initrd and running it after boot has concluded (at which point /dev/fb0 exists) works successfully which suggests there's no issue with the framebuffer itself, just that the framebuffer doesn't exist (presumably due to the aforementioned lack of kernel modules in the initrd) at the (very early) point in the boot where psplash is executed.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1837209 Title: Splash screen fails to display on recent pi core18 images Status in Snappy: New Status in linux-raspi2 package in Ubuntu: New Bug description: The current core18 image [1] for the raspberry pi fails to display the "Core" splash screen on boot. This is because psplash fails to open the /dev/fb0 framebuffer device, because it doesn't exist. This appears to be due to a lack of supporting kernel modules in the initrd.img (fb_sys_fops, drm, vc4, etc.) which were formerly present but are missing from the version I'm testing (pi-kernel 4.15.0-1041.44, snap rev 42). Steps to reproduce: * Flash the image to a uSD card and boot the pi with it (preferably with a serial console attached). * Note screen remains black instead of displaying the familiar "Core" text under an Ubuntu logo. * If serial console is attached, note "Error opening /dev/fb0" in the output shortly after u-boot starts the kernel; this is output from psplash failing [1] http://cdimage.ubuntu.com/ubuntu-core/18/current/ubuntu- core-18-armhf+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1837209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
