On Tue, 2005-01-18 at 23:54 +0000, Douglas James Dunn wrote:
> On Wed, 2005-01-19 at 09:11 +0930, Iain Buchanan wrote:
> > On Tue, 2005-01-18 at 12:39 +0000, Douglas James Dunn wrote:
> > >
> > > FB Radeon and fglrx used together is a known problem its best not to use
> > > the radeon FB driver.
> >
> > I was hoping the [new] ati-drivers would fix this... Is there anything
> > else I
> > can do to get a 1680x1050 text console with fglrx?
>
> VesaFB
I am using that... TNG to be exact, but it only gives me 4:3
resolutions, so I still get the "black bars" down each side of the LCD.
I tried using fbset with vesafb-tng
1. I got the mode from fbset when using the radeonfb driver:
mode "1680x1050-60"
# D: 119.261 MHz, H: 64.816 kHz, V: 60.014 Hz
geometry 1680 1050 1680 1050 8
timings 8385 80 48 22 2 32 6
hsync high
vsync high
# rgba 8/0,8/0,8/0,0/0
endmode
2. then I put that in /etc/fb.modes
3. I restarted without the radeonfb driver (only vesafb-tng) and used
fbset to switch:
$ fbset "1680x1050-60"
and it just replies:
ioctl FBIOPUT_VSCREENINFO: Invalid argument
however when I use fbset to switch to the mode I'm already in:
$ fbset "1280x1024-60"
The screen text console blanks, and then comes back, and fbset exits
without error... So I think fbset works, but vesafb-tng is for some
reason not letting me change to the 1680x1050 mode.
NB I also tried stty, but didn't work either. I just kept saying "No
such device or address" no matter what I used for -F...
Any ideas anyone? MTIA!!
--
Iain Buchanan <[EMAIL PROTECTED]>
--
[email protected] mailing list
