If I set it to verbose, the consolefont is set as it should be; but if it's set to silent I get the PIO_FONT error.
Might it be due to some configuration on my computer, or is it perhaps a bug?
Kristian
Kristian Niemi wrote:
Thanks for the tip. Sounds plausible that it's related to the framebuffer -- but it still seems quite strange that it doesn't happen every time. I don't know how to reiplicate the behaviour every time.
That said, the `weirdness' might be due to a framebuffer bug, not a consolefont-one (i.e. the script `consolefont')? Out of curiosity, what video card do you have? I have a ATI Radeon 7500 Mobile.
When it does work, I haven't changed anything in my systems setup.
I'm not using the default console-font, since I want to be able to use/see the scandinavian characters (едц). (So everytime I get the PIO_FONT I can't use the scand. char. -- that is, not before I've restarted consolefont.)
Kristian
Gabriel M. Beddingfield wrote:
Kristian Niemi wrote:
Every now and then I get the following error on bootup: putfont: PIO_FONT: Invalid argument In effect, (/etc/init.d/)consolefont fails to start properly. I have to restart it manually -- and if I do, it works just fine (i.e. it changes the font).
I noticed the same thing. It either has always happened for me, or it
started when I started adding the framebuffer stuff. I worked around it by
using the default console font. Do this by commenting out the CONSOLEFONT
line in rc.conf.
I suspect that it has something to do with the framebuffer console drivers.
signature.asc
Description: OpenPGP digital signature
