View previous topic :: View next topic |
Author |
Message |
lars_the_bear Guru
Joined: 05 Jun 2024 Posts: 512
|
Posted: Sun Jun 09, 2024 10:33 am Post subject: Font changes at boot time |
|
|
Hi folks
I guess this is a trivial matter, compared to some of the things I'm fighting, but...
When I boot (using OpenRC) the console font changes at some point in the init process. I'm not exactly sure where. It changes to a font so small that I can't see it on my screen.
So I did
rc-update add consolefont boot
and chose a bigger font in /etc/conf.d/consolefont. This does get me a font I can read -- in the end -- but now there are three font switches -- the OK font I see right at the start, then the tiny one, then a different OK one.
That's not just unsightly -- most of the boot messages are still in a font that I can't read.
Can all this be prevented? I'm perfectly happy with the font size that I get at the start of boot. Can I disable whatever it is that's causing it to change?
BR, Lars. |
|
Back to top |
|
|
gentoo_ram Guru
Joined: 25 Oct 2007 Posts: 501 Location: San Diego, California USA
|
Posted: Sun Jun 09, 2024 12:09 pm Post subject: |
|
|
Guessing it has to do with the resolution of your screen. When the kernel switches to a different frame buffer device the resolution must be changing. Look at your kernel logs to see what resolution it uses. Maybe add boot parameters to lower the resolution of your frame buffer. |
|
Back to top |
|
|
lars_the_bear Guru
Joined: 05 Jun 2024 Posts: 512
|
Posted: Sun Jun 09, 2024 2:01 pm Post subject: |
|
|
gentoo_ram wrote: | Guessing it has to do with the resolution of your screen. When the kernel switches to a different frame buffer device the resolution must be changing. Look at your kernel logs to see what resolution it uses. Maybe add boot parameters to lower the resolution of your frame buffer. |
Thanks.
The only relevant thing I see in the boot log is:
Code: |
[ 6.343960] Console: switching to colour frame buffer device 240x67
|
That looks right -- 240x67 is way too dense for my eyesight and screen -- but the change actually happens during execution of init scripts. I've got 'quiet' on my kernel command line, so I don't expect to see any output from the kernel itself.
But perhaps the resolution change is initiated by the kernel, but takes some time to take effect? Perhaps that why it seems to happen late? I don't know.
'nomodeset' stops all this messing about, but they the X server won't start. I just get a black screen.
Is there a kernel command line switch to change the console resolution after KMS is enabled? There's lots of conflicting information in this area.
BR, Lars. |
|
Back to top |
|
|
|