linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: biatx@portugalmail.com
To: "adaplas@pol.net" <adaplas@pol.net>
Cc: "linux-fbdev-devel@lists.sourceforge.net"
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Issues with radeonfb (new) in widescreen displays
Date: Wed, 23 Jun 2004 19:16:14 +0100	[thread overview]
Message-ID: <1088014574.40d9c8eee32ad@webmail.portugalmail.pt> (raw)
In-Reply-To: <200406230904.20399.adaplas@hotpop.com>

When I run "stty -F /dev/tty7 cols 80 rows 30" the problem seems gone and
radeonfb acts perfect...hope you can fix it definitively then.

Thank you a lot

Carlos Silva


"Antonino A. Daplas" <adaplas@hotpop.com> wrote:

 A workaround which may or may not work is to set the tty where X is located
 to a different size as compared to the tty's where your console is mapped.
 
 So if X is in /dev/tty7, you can do something like this:
 
 stty -F /dev/tty7 cols 80 rows 30
 
 (Use the latest BK or mm release.  stty will fail in 2.6.7)
 
 The above will set tty7 to 640x480.  This way, when you switch to any of 
 your consoles (assuming they are not in 640x480), the framebuffer console
 will "reinitialize" the hardware. 
 
 A more definitive fix is in the works.
 
 Tony



__________________________________________________________
Continua a preferir gastar mais? Adira à ligação Portugalmail.
http://acesso.portugalmail.pt/compare


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com

      reply	other threads:[~2004-06-23 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23  0:06 Issues with radeonfb (new) in widescreen displays biatx
2004-06-23  1:04 ` Antonino A. Daplas
2004-06-23 18:16   ` biatx [this message]

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=1088014574.40d9c8eee32ad@webmail.portugalmail.pt \
    --to=biatx@portugalmail.com \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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 NNTP newsgroup(s).