You are not logged in.
Pages: 1
Synopsis: replace 'consolefont' and 'keymap' hooks with the 'sd-vconsole' hook
Synopsis: add fbcon=nodefer to the kernel boot parameters. See below for details.
As indicated here I use the kernal parameter fbcon=font:TER16x32 to get rid of gobbly-goop that appears for special characters in one of my kernel hooks. Works fine if I boot using syslinux. However when I boot via UEFI the font initially appears very large and then reverts to the same size as with syslinux and the gobbly-goop is still there.
Is there another kernel parameter required specifically for UEFI and why the difference?
Last edited by CaeriTech (2023-10-13 16:30:41)
-=[ LIVE enabled UEFI with redundant syslinux pure systemd detached LUKS header partitionless encrypted GPT SSDx3 RAID0 wayland only because I can. ]=-
Backward compatibility is for the masses. There's no dual-boot here.
[CaeriTech remains only artificially intelligent. Turing would be aghast at just how artificial.]
Offline
Related to this bug. The recommendation to replace 'consolefont' and 'keymap' hooks with the 'sd-vconsole' hook works and the UEFI boot font is now identical to the syslinux boot.
[Edit] It's still not perfect. There's a flash as the resolution/font is set and some of the special characters in the ASCII art that I dump to the boot screen are not being interpreted as special. syslinux still does a way nicer job of it.
[Edit] A kernel command line parameter fixed this. See here. Now the UEFI boot is identical to the syslinux boot.
Last edited by CaeriTech (2023-10-13 16:27:35)
-=[ LIVE enabled UEFI with redundant syslinux pure systemd detached LUKS header partitionless encrypted GPT SSDx3 RAID0 wayland only because I can. ]=-
Backward compatibility is for the masses. There's no dual-boot here.
[CaeriTech remains only artificially intelligent. Turing would be aghast at just how artificial.]
Offline
Pages: 1