Re: Scrambled early boot messages (gremlins) Reply #15 – 24 June 2023, 05:08:48 Yes, that's the one, something like April's Fool's day on Stack Exchange! It's fixed upstream now, I built and tested it and I can confirm everything seems fine here.
Re: Scrambled early boot messages (gremlins) Reply #16 – 24 June 2023, 06:47:22 Quote from: melleus – on 24 June 2023, 01:32:17If I remove the consolefont service completely I don't get the font in console, If I put the consolefont service at the default runlevel I get the scrambled screen anyway. The only way for me to get the readable boot screen is to downgrade the broken kbd package to the last working version, 2.5.1-2 in my case.
Re: [SOLVED] Scrambled early boot messages (gremlins) Reply #17 – 27 June 2023, 01:30:27 I hope that fixed kbd will arrive to the repos finally. Still have the garbage with the current version of kbd when booting.
Re: [SOLVED] Scrambled early boot messages (gremlins) Reply #18 – 27 June 2023, 03:27:13 It won't get picked up as an update until the upstream KBD gets a new release, the most recent is still 2.6.0. I expect the change is still in the testing and review phase. The only other way that might happen is if Artix devs make their own patched version. But it's quite normal and acceptable practice to downgrade a package on a rolling release distro, then put it into /etc/pacman.conf as an ignorepkg so it won't get upgraded on updates. Although my own solution was to build a fixed 2.6.0 package version which won't get upgraded until a newer version is released. 1 Likes
Re: [SOLVED] Scrambled early boot messages (gremlins) Reply #19 – 27 June 2023, 15:09:07 Some lack of stability is the only thing that bothers me in Artix from time to time. But I don't have to have so much resources like Gentoo and I have all softwares that I need, unlike FreeBSD or Void.
Re: [SOLVED] Scrambled early boot messages (gremlins) Reply #20 – 06 July 2023, 11:09:12 FWIW, this is just a harmless aesthetic glitch.
Re: [SOLVED] Scrambled early boot messages (gremlins) Reply #21 – 07 July 2023, 03:58:05 QuoteIf I remove the consolefont service completely I don't get the font in consoleTo get the kernel to set the console font, it's required to first create /etc/vconsole.conf with a line like:Code: [Select]FONT="lat4-19"or any of the fonts in /usr/share/kbd/consolefonts. It works with or without the "" quotes. Then check that /etc/mkinitcpio.conf doesn't have a .pacnew, because the consolefont hook was recently added to the line near the end of that file, and without it this won't work. Then run:Code: [Select]# mkinitcpio -Pto regenerate the kernel initcpio's which also gets done as a package installation hook sometimes, and after rebooting, the font should be set in the console, without needing to use the consolefont service.https://wiki.archlinux.org/title/Linux_consoleAmong the font choices it's possible to choose ones larger than standard, although the standard choice in the kbd package of these over 16 is limited, but that could be useful for some laptops and so on with small but high resolution screens, because the standard font can look tiny.The current kbd package has fixed this problem, incidentally.