Display issues from the Console/CMD Line

Display issues from the Console/CMD Line

Post by Flipmod » Sun, 06 Jan 2002 03:39:47



I have set in my LILO.CONF
vga=792

should correspond to the following setting.

Also initab file is set to run level 4 boots into X

Now whenever I go back to console mode my screen is all funky.
The starting point of the prompt, and text is close to the far right corner.

?'s.
1. Has anyone encountered this b4?
2. What is the Cause?
3. How do I correct this?

THX Flipmode...

 
 
 

Display issues from the Console/CMD Line

Post by Donovan Nage » Sun, 06 Jan 2002 07:35:05


Yes, I had a similiar problem... you'll need to compile framebuffer
support into your kernel.

> I have set in my LILO.CONF
> vga=792

> should correspond to the following setting.

> Also initab file is set to run level 4 boots into X

> Now whenever I go back to console mode my screen is all funky.
> The starting point of the prompt, and text is close to the far right corner.

> ?'s.
> 1. Has anyone encountered this b4?
> 2. What is the Cause?
> 3. How do I correct this?

> THX Flipmode...


 
 
 

Display issues from the Console/CMD Line

Post by Dances With Cro » Sun, 06 Jan 2002 10:26:45


[crossposting trimmed, message reformatted]
On Sat, 05 Jan 2002 08:35:05 +1000, Donovan Nagel staggered into the
Black Sun and said:


>> I have set in my LILO.CONF
>> vga=792

>> Now whenever I go back to console mode my screen is all funky.  The
>> starting point of the prompt, and text is close to the far right
>> corner.

>> 1. Has anyone encountered this b4?
>> 2. What is the Cause?
>> 3. How do I correct this?

> Yes, I had a similiar problem... you'll need to compile framebuffer
> support into your kernel.

If framebuffer support weren't in Flipmode's kernel, then he would
notice it immediately.  The penguin logo that a framebuffer-enabled
kernel shows on boot is present if the framebuffer has started up
correctly, absent otherwise.  Info is also present in the first ~100
lines of "dmesg" as well as /var/log/boot.log (or wherever Slack keeps
the boot log.)

X and the framebuffer sometimes have weird interactions.  This is
probably what's really going on.  If we knew which graphics card you
have and what version of X you're running, that might help.  You can get
rid of the weird interactions by using the X Framebuffer server, but
that is a *really* bad idea.

--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /
http://www.brainbench.com     /  "He is a rhythmic movement of the
-----------------------------/    penguins, is Tux." --MegaHAL