bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug in stty???


From: Bob Proulx
Subject: Re: bug in stty???
Date: Sun, 24 Jul 2005 09:20:04 -0600
User-agent: Mutt/1.5.9i

Anders Gr�nlund wrote:
> Hi again.
> I am sorry that I was not clear enough.
> I mean terminal I get before I startx. I am not really sure about the 
> terminolgy. I get /dev/vc/1 from tty so I guess what I have is a "virtual 
> console". I thought I should be able to configure this with stty.

The stty command is not the right tool for the job.  You need a
different tool.

As it turns out that it does not really matter whether you are talking
about one of the virtual consoles or about an xterm or about an actual
vt100 terminal.  In none of those cases will changing the tty driver
rows and columns variable with stty change the actual size of the
terminal.  Thinking about the actual hardware vt100 terminal and you
will see that it cannot make any changes to the size through any
command like that.  (Things would be pretty interesting if it did!)
Changes to the size must happen first.  And virtual consoles and
xterms and other terminals emulate that hardware behavior.

You did not say but I think you might be running a linux kernel.
(There are a large number of operating systems and kernels available
in the world.  To you running on your own system it may be obvious.
But to me reading your message unless you say then I have to guess
from the large number of available ones to select from.)  In that case
if you specify vga=ask on the linux kernel command line at boot time
it should prompt you with a list of supported video modes.  Select one
and try it.  Not all modes will produce good results.

If you find a video mode that you like that is not the default and
always want to boot that way you can modify your bootloader (grub,
lilo, etc.  There are also a large number of boot loaders available
too.) to always boot with that command line.

For the linux kernel see the file Documentation/kernel-parameters.txt
included in the linux kernel source for more information.

Bob

> Maybe 
> this should be done with a kernel parameter at boot instead. I've read a 
> lot if stuff about the frambuffer and vesafb etc. I've compiled a new 
> kernel and am checking out the various kernel params. I'd be glad to hear 
> from you if you can help me.
> 
> I hope I don't bother you too much.
> Kind regards,
> 
> Anders.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]