Bug#859458: Because of displays with very high dpi, not only the keyboard, but the font has to be configured early

2024-03-29 Thread Jmkr
Here you go. Both scripts are in the attached "SCRIPTS.txt". Note that on my systems I keep only the one PSF font that I actually use, so my hook script does not need to update cached fonts + my systems are without PLYMOUTH. Check Pedro's scripts if you need to handle those more complex usages.

Bug#859458: Because of displays with very high dpi, not only the keyboard, but the font has to be configured early

2024-03-29 Thread Jörg Sommer
Jmkr schrieb am Di 26. Mär, 23:31 (+0100): > Although Plymouth is not installed on my systems I adapted some safety > check bits from those scripts for my systems. So thanks again Jörg Sommer > and Pedro Dias:). Cool, the power of open source team work. Could you provide your new script? I've

Bug#859458: Because of displays with very high dpi, not only the keyboard, but the font has to be configured early

2024-03-26 Thread Jmkr
I checked the INITRAMFS-TOOLS source code and the "PREREQ" variable + "prereqs" function seems redundant - details are in a new bug I submitted: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067804 I also found an alternative to Jörg's scripts that could be useful for Plymouth boot splash

Bug#859458: Because of displays with very high dpi, not only the keyboard, but the font has to be configured early

2024-03-24 Thread Jmkr
Hello, I also hit this bug when switching from BIOS to UEFI boot process. Details for context are in the next paragraph, but feel free to skip to the QUESTION part:). After disabling the legacy BIOS support on my machines I noticed UEFI boot process uses the native LCD resolution. This causes

Bug#859458: Because of displays with very high dpi, not only the keyboard, but the font has to be configured early

2020-08-04 Thread Diego Escalante Urrelo
Package: console-setup Followup-For: Bug #859458 X-Debbugs-Cc: die...@gnome.org I seem unable to reproduce in my current unstable/sid system. At first I thought it was because I had switched to `dracut`, but seems like I can't reproduce the original issue with `initramfs-tools`. Perhaps