Re: Issues with radeonfb (new) in widescreen displays

["Antonino A. Daplas" <adaplas@hotpop.com>]

On Wednesday 23 June 2004 08:06, biatx@portugalmail.com wrote:
> Hi!
> I'm having a problem on a HP NX7000 laptop (the same as Compaq X1000)
> which has a mobility radeon 9000 (identified and marketed by HP as Radeon
> 9200 because of its clock rates) and a Samsung LCD with 1680x1050 (WSXGA+)
> as its native resolution.
>
> After booting up the system with a 1680x1050 radeonfb (only possible by
> editing
>
> drivers/video/aty/radeon_base.c
>
> and commenting out the
>
> radeon_map_ROM(rinfo, pdev);
>
> everything appears fine, except when Xorg launches using the 'radeon'
> driver and loads the GNOME environment. After that, if I switch back to a
> vt with eg. Ctrl+Alt+F1 my console will show up some garbled lines with
> green pixels mostly, in the bottom, in the area never used because of the

<snip>

> I'd really appreciate if someone could come up with a solution or patch,
> otherwise i'll have to fallback to the more limited and buggy old radeonfb
> driver that doesn't exhibit this behaviour when interacting with X.
>

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




-------------------------------------------------------
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