I've just performed a long and very tedious update of 2022 Gentoo to actual state (using historical portage git repo and 2 week steps).
The system is in actual state, kernel is 6.12.31. But the installation itself originates to late 2009, I think, so some pieces are from that age giving me random headaches in very unexpected places.
Anyways, the system boots, all the hardware seems to work as expected, except the hostapd that I was forced to downgrade to 2.9-r6 cause of the crda and all this pesky regulatory stuff - I'm not very concerned cause it seem to work stable and I'm planing to take a look later probably tuning Qualcomm Atheros QCA9880 802.11ac to perform better.
The thing that drives me mad is the consolefont.
Code: Select all
/etc/init.d/consolefont restart
* Setting console font [UniCyr_8x16] ...
setfont: ERROR kdfontop.c:212 put_font_kdfontop: Unable to load such font with such kernel version [ !! ]
* ERROR: consolefont failed to start
Since that system is pretty skinny in packages installed (only about 400, unlike fat desktops) and I was going to rebuild it anyway I let it go through emptytree overnight and then rebooted expecting it to be some old includes/dependencies from the old system - same result.
Moving consolefont from boot to default runlevel also made no change.
Cause I have a laptop running exactly same kernel I then gone checking configuration in /etc/conf.d and kernel parameters, made it same - failure - same error.
So, currently I have two systems with same configs, same kernel versions and moreover, built from same kernel configs (the difference is intel microcode and preemption model) one of which give no error on setfont, the other one fails.
I've checked logs of 4.19.222 that was running on that server for years and years and found no errors on /etc/init.d/consolefont startup:
Code: Select all
* Setting console font [cyr-sun16] ...
[ ok ]
The only idea I have - the system that fails to load console fonts is completely headless - there is no any display connected to HDMI port as it a humble fanless server, but it had no problems with this when 4.19.222 was in service. I can't check this idea because I have no spare monitor.
Any idea what is going on and how to fix that?


