On Thursday, 22 August 2024 01:34:28 BST corbin bird wrote: [Snip ...] > You need all shown below to get console output.
With EFI MoBos in most cases you no longer need any other than the EFI framebuffer, although legacy framebuffers won't hurt beyond bloating the size of the kernel image. Kernel image size could be an issue for embedded devices, but not for a desktop. > --------- > Under "Device Drivers ---> Firmware Drivers --->" > [*] Mark VGA/VBE/EFI FB as generic system framebuffer > > Under "Device Drivers ---> Graphics support ---> Frame buffer Devices > --->" <*> Support for frame buffer device drivers ---> > [*] Provide legacy /dev/fb* device The legacy /dev/fb* device above is only needed if you have some particular application or code which may use fbdev to provide graphics output - e.g. https://github.com/reiver/go-fbdev > Under "Device Drivers ---> Graphics support ---> Frame buffer Devices > ---> <*> Support for frame buffer device drivers --->" > [*] VESA VGA graphics support > [*] EFI-based Framebuffer Support > <*> Simple framebuffer support Just building the "EFI-based Framebuffer Support" should be enough for EFI MoBos. Note, to have a console coming up and not just a black screen you will also need DRM_FBDEV_EMULATION for the KMS to be able to set your display mode: -> Device Drivers -> Graphics support -> Enable legacy fbdev support for your modesetting driver (DRM_FBDEV_EMULATION [=y]) │ Selects: FRAMEBUFFER_CONSOLE_DETECT_PRIMARY [=y]
signature.asc
Description: This is a digitally signed message part.
