| 1 |
Thanks for the tip. Sounds plausible that it's related to the |
| 2 |
framebuffer -- but it still seems quite strange that it doesn't happen |
| 3 |
every time. I don't know how to reiplicate the behaviour every time. |
| 4 |
|
| 5 |
That said, the `weirdness' might be due to a framebuffer bug, not a |
| 6 |
consolefont-one (i.e. the script `consolefont')? Out of curiosity, what |
| 7 |
video card do you have? I have a ATI Radeon 7500 Mobile. |
| 8 |
|
| 9 |
|
| 10 |
When it does work, I haven't changed anything in my systems setup. |
| 11 |
|
| 12 |
I'm not using the default console-font, since I want to be able to |
| 13 |
use/see the scandinavian characters (åäö). (So everytime I get the |
| 14 |
PIO_FONT I can't use the scand. char. -- that is, not before I've |
| 15 |
restarted consolefont.) |
| 16 |
|
| 17 |
|
| 18 |
Kristian |
| 19 |
|
| 20 |
Gabriel M. Beddingfield wrote: |
| 21 |
> Kristian Niemi wrote: |
| 22 |
> |
| 23 |
> |
| 24 |
>>Every now and then I get the following error on bootup: |
| 25 |
>>putfont: PIO_FONT: Invalid argument |
| 26 |
>>In effect, (/etc/init.d/)consolefont fails to start properly. I have to |
| 27 |
>>restart it manually -- and if I do, it works just fine (i.e. it changes |
| 28 |
>>the font). |
| 29 |
> |
| 30 |
> |
| 31 |
> I noticed the same thing. It either has always happened for me, or it |
| 32 |
> started when I started adding the framebuffer stuff. I worked around it by |
| 33 |
> using the default console font. Do this by commenting out the CONSOLEFONT |
| 34 |
> line in rc.conf. |
| 35 |
> |
| 36 |
> I suspect that it has something to do with the framebuffer console drivers. |
| 37 |
> |
| 38 |
> |
Archives