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

Re: XFree864.01, G4, Ati Rage Pro 128 & Apple Studio 17"



On Wed, Nov 22, 2000 at 02:48:45PM +0000, jon ewing wrote:
> 
> Hi,
> 
> If I understand correctly, when I boot with
> 
> append="video=aty128fb:vmode:20,cmode=32"
> 
> in my yaboot.conf, the aty128fb driver will be communicating directly with 
> my graphics hardware. When I then start X using the fbdev driver, the modes 
> available to X are limited by the modes available to aty128fb. So, if I add 
> a new mode to fb.modes and am able to successfully switch to that mode on 
> the console using, eg, fbset --test, then I should also be able to run X in 
> that mode.
> 
> My fb.modes initially contained 3 "1600x1200-.." modes (.. = 60, 66 or 76), 
> but if I try fbset-ing to any of these modes the screen goes blank. By 
> default the console appears at 1280x1024-75.
> 
> If instead I boot with novideo then my console appears in glorious 
> 1600x1200. I then tried fbset, which returned
> 
> mode "1600x1200-49"
> 	# D: 100.00 MHz, H: 60.976 kHz, V: 49.174 Hz
> 	geometry 1600 1200 1600 1200 8
> 	timings 10000 16 16 16 16 8 8
> endmode

The video mode information returned while using offb (novideo) is not
valid, as far as I know, so using this will not work.

> I added this to my fb.modes, changed my yaboot.conf back to aty128fb, 
> rebooted, tried fbset --test "1600x1200-49", and again the screen went blank.
> 
> Am I going about this the right way?
> 
> Olaf - I tried those settings and each of them just blanked the screen. Are 
> you booting with the aty128fb driver or with novideo (or something else)? 
> Also, are you using the fbdev driver for X or the r128 driver? What 
> parameters are you passing to the driver?
> 
> Michel - How would I find the timings that I'd need in order to add a 
> 1600x1280 mode to my fb.modes?

Try the mode lines from Olaf (which I haven't tried, but let's assume
they're right), and make sure you do NOT have UseFBDev in your
/etc/X11/XF86Config file.  This sounds like it might be a bug in the
aty128fb driver.

ttyl,

-- 
Josh Huber                                   | huber@debian.org |
                                             | Debian Developer |
1024D/6B21489A 61F0 6138 BE7B FEBF A223  E9D1 BFE1 2065 6B21 489A

Attachment: pgp0IsQtruuIT.pgp
Description: PGP signature


Reply to: