Re: console font corruption after exiting xorg

2008-09-27 Thread j t
On Thu, Aug 28, 2008 at 5:35 PM, Scott Edwards [EMAIL PROTECTED] wrote: After I switch to a console screen, or exit from xorg, the console font is corrupted. I can see what I type, but you cannot make out what the characters are on the screen. Does anyone have suggestions on how troubleshoot

Re: console font corruption after exiting xorg

2008-08-31 Thread Andrei Popescu
On Thu,28.Aug.08, 10:35:27, Scott Edwards wrote: I'm having similar problems on two different machines. For now I'll focus on the laptop running stable on a g4 ppc CPU. After I switch to a console screen, or exit from xorg, the console font is corrupted. I can see what I type, but you

Re: console font corruption after exiting xorg

2008-08-29 Thread Mumia W..
On 08/28/2008 11:35 AM, Scott Edwards wrote: I'm having similar problems on two different machines. For now I'll focus on the laptop running stable on a g4 ppc CPU. After I switch to a console screen, or exit from xorg, the console font is corrupted. I can see what I type, but you cannot make

console font corruption after exiting xorg

2008-08-28 Thread Scott Edwards
I'm having similar problems on two different machines. For now I'll focus on the laptop running stable on a g4 ppc CPU. After I switch to a console screen, or exit from xorg, the console font is corrupted. I can see what I type, but you cannot make out what the characters are on the screen.

Re: console font corruption after exiting xorg

2008-08-28 Thread Bob McGowan
Scott Edwards wrote: I'm having similar problems on two different machines. For now I'll focus on the laptop running stable on a g4 ppc CPU. After I switch to a console screen, or exit from xorg, the console font is corrupted. I can see what I type, but you cannot make out what the characters

Re: console font corruption after exiting xorg

2008-08-28 Thread Paul Dufresne
More like a me too, but just a little bit for me. Once in a while, one of the letters have missing part. Like the 'f' have some part missing, or the 'n'. For me rebooting seems to fix it. I had almost the feeling a developper was making some kind of joke. I have a i945GZ chipset, so no proprietary