The Linux kernel patches talked about at the start of the year for more easily changing the boot logo of Tux are now queued into a "for-next" branch and thus expected to be submitted for the upcoming Linux 6.20~7.0 kernel cycle. Those wanting to replace the Tux icon with an alternative logo during the Linux kernel boot process could already patch the file manually but this new code allows for an easy replacement via Kconfig options.
Those wanting to customize their console boot experience for Linux will be able to more easily do so with the next version of the Linux kernel. Rather than patching the source code and Makefile, via the Kconfig an al…
The Linux kernel patches talked about at the start of the year for more easily changing the boot logo of Tux are now queued into a "for-next" branch and thus expected to be submitted for the upcoming Linux 6.20~7.0 kernel cycle. Those wanting to replace the Tux icon with an alternative logo during the Linux kernel boot process could already patch the file manually but this new code allows for an easy replacement via Kconfig options.
Those wanting to customize their console boot experience for Linux will be able to more easily do so with the next version of the Linux kernel. Rather than patching the source code and Makefile, via the Kconfig an alternative boot logo file can be specified. The patches add LOGO_LINUX_MONO_FILE for allowing a monochrome boot logo in PBM file format. Or there is also LOGO_LINUX_VGA16_FILE for a 16 color PPM boot logo file or LOGO_LINUX_CLUT224_FILE for a 224 color PPM logo.
Those patches are now queued into the linux-fbdev.git’s for-next branch. With those patches in recent days making it into FBDEV’s "for-next" branch, it should be submitted as part of the upcoming Linux 6.20~7.0 kernel cycle for this custom logo support.
The Linux 6.20~7.0 kernel cycle will be getting underway in February following the Linux 6.19 stable release. That next kernel is what’s expected to power the likes of Ubuntu 26.04 LTS and Fedora 44 this spring.