#Fedora is currently discussing a proposal to replace the #kernel console #fbcon with the userspace console #kmscon in its next version, "to provide an enhanced and more secure console.

The long term goal is also to deprecate fbcon/fbdev emulation in the kernel, and this is the first step in this direction.""

https://fedoraproject.org/wiki/Changes/UseKmsconVTConsole

https://discussion.fedoraproject.org/t/f44-change-proposal-usekmsconvtconsole-selfcontained/172602

https://lists.fedoraproject.org/archives/list/[email protected]/message/MBGFWEQXZP3NFMDB5446ZD6ALUZCUNNI/

#fbdev #vconsole #unimap #fbcon #keymaps #codepages … 3 hours of unproductive time wasted on research why one machine uses code page 437 (the Linux default code page for #tty) and the other machine doesn’t.

It is mentioned on several pages, that the default is #CP437, and how I can change this default, but it seems like a mystery or forbidden knowledge WHY it is changed, without me actively changing it.

It might have to do with the screen resolutions of those two devices, or that one is an #Intel #GPU and the other is #Nvidia. But i was not able to find anything of value.

Oh #fuck this shit.

#ModernLinuxProblems #MagicBullshit

Can the system please let ME be in control and not doing seemingly undocumented random shit that is not represented in any configuration and feels like it’s hidden in a blackbox?

That would be great, thanks.

SUSE has been working on an in-kernel boot splash screen for Linux.

The patches in their initial form for this new kernel "bootsplash" yet still shows a blank screen but can be adapted to a show a distribution's logo, Tux, or the like.

This suggestion comes from developer Max Staudt.

-->

http://lkml.iu.edu/hypermail/linux/kernel/1710.3/01542.html

#Linux #bootsplash #kernel #Tux #boot #fbdev #fbcon

Linux-Kernel Archive: [RFC 00/14] Kernel based bootsplash