public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Debian Well Underway
Date: Fri, 17 Oct 2008 08:48:22 +0800	[thread overview]
Message-ID: <BDC8A45D467A42419E6E6FB01A19370B@kazam> (raw)
In-Reply-To: <20081016160109.GA4554@lnx3.holmesgrown.com>

keep in mind that when you ssh or telnet the screen geometry is sent by the 
host telnetting in so for example if you use Teraterm it will give rows and 
columns based on the window size as will cygwin.

The Linux console gives rows and columns based on how the console is set up.

As a matter of interest if you come in on a serial console then your rows 
and columns will be set to 0 as the serial console knows no better.

You can
stty rows 24 columns 80

however don't just
stty rows 60 columns 132

as your window won't fit on the console fix the underlying problem.

Regards, Kerry.

----- Original Message ----- 
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Friday, October 17, 2008 12:01 AM
Subject: Re: Debian Well Underway


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> Interesting observation.  I just suspended mutt and went into /dev and
> sure enough, I have no fb device.  I don't really know anything about
> framebuffer support so don't know about needing a /dev/fb or not to
> enable larger screen sizes at the console.  Even so, vga=extended
> wouldn't yield me 50 lines either.  Yet when I come into my box from a
> remote ssh session, I use vt220 emulation and I get 42 rows and 111
> columns.  I just can't seem to figure out how to do that with a linux
> console.  While on the ssh session, $TERM shows VT220; while at home
> locally, $TERM shows linux.
>
> On Thu, Oct 16, 2008 at 10:57:13AM -0400, Erik Heil wrote:
>> Hi their,
>> What I can tell you is that framebuffer support i.e. /dev/fb is not
>> present in at least 2.6.18 by default.  This is using the stock Debian
>> kernel and using a Geforece2MX video board.  Either framebuffer support 
>> is
>> not in the kernel, or their are problems with that type of particular
>> hardware.  This was, in fact, the culprit of my display problems I posted
>> about efroe.  It had nothing to do with the auto detection code that was
>> introduced between Sarge and Lenny.  Rather, the X server couldn't write
>> to the nonexistent framebuffer device, so of course it would generate an
>> error.  Log messages in this case were not helpful though.
>>
>> --Erik
>>
>> On Wed, 15 Oct 2008, Chuck Hallenbeck wrote:
>>
>> > Date: Wed, 15 Oct 2008 09:55:03 -0400
>> > From: Chuck Hallenbeck <chuckh@ftml.net>
>> > Reply-To: Speakup is a screen review system for Linux.
>> >     <speakup@braille.uwo.ca>
>> > To: Speakup is a screen review system for Linux. 
>> > <speakup@braille.uwo.ca>
>> > Subject: Re: Debian Well Underway
>> >
>> > Hi Steve,
>> >
>> > I wish I could help you, but my installation is a really simple one. I
>> > used Samuel's mini-beep.iso, and selected "standard" from the
>> > configuration menu, and that's all it took. No extra packages relating
>> > to frame buffers or displays, other than what the "standard" choice
>> > implied. I switched from lilo to grub a long time ago, so I can't
>> > compare my loader configuration to yours directly.   But for what it's
>> > worth, here's the kernel line from my grub menu.lst:
>> >
>> > kernel          /boot/vmlinuz-2.6.26-1-686 root=/dev/sda1 ro vga=791
>> > quiet
>> >
>> > That seemed to wrap just now, but it's all one line in the
>> > configuration file. There's also an initrd, but again it was done for
>> > me by magic, I did nothing to modify or enhance it.
>> >
>> > Chuck
>> >
>> >
>> >
>> > On Wed, Oct 15, 2008 at 04:48:11AM -0700, Steve Holmes wrote:
>> > > -----BEGIN PGP SIGNED MESSAGE-----
>> > > Hash: RIPEMD160
>> > >
>> > > Yes, it looks like the exact same kernel here.  Wonder if I need to
>> > > have some frame buffer packages installed or something.  I began
>> > > looking at the console related stuff but haven't uncovered anything
>> > > yet.  Still looking for ideas.
>> > >
>> >
>> > --
>> > The Moon is Waning Gibbous (99% of Full)
>> >
>> > My web site: http://hallenbeck.ftml.net -- my telephone: 
>> > 1-518-334-9022.
>> >                                 --------
>> > Sarah Palin: At last, a Beauty Queen who doesn't want World Peace.
>> > _______________________________________________
>> > Speakup mailing list
>> > Speakup@braille.uwo.ca
>> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>> >
>>
>> eheil@sdf.lonestar.org
>> SDF Public Access UNIX System - http://sdf.lonestar.org
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEAREDAAYFAkj3ZUUACgkQWSjv55S0LfHxHwCeM+/BdOGJPERZwOVfIb6aj8vq
> 5C8AoMxSdltyf/OSnokrOxAVafl+mKIQ
> =+YJL
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 


  parent reply	other threads:[~ UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Steve Holmes
 ` Samuel Thibault
 ` Gregory Nowak
   ` Steve Holmes
 ` Chuck Hallenbeck
   ` Steve Holmes
     ` Chuck Hallenbeck
       ` Steve Holmes
         ` Chuck Hallenbeck
           ` Erik Heil
             ` Steve Holmes
               ` Gregory Nowak
               ` Chuck Hallenbeck
               ` Kerry Hoath [this message]
 ` Kerry Hoath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BDC8A45D467A42419E6E6FB01A19370B@kazam \
    --to=kerry@gotss.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).