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

[Michel Dänzer <daenzerm@student.ethz.ch>]

jon ewing wrote:

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

No, at least not if you mean the modes in /etc/fb.modes . X should be able to
use any mode through aty128fb if it can without.


> (WW) r128(0): Mode "1600x1200@70x" deleted (hsync out of range)
> (WW) r128(0): Mode "1600x1200@75x" deleted (hsync out of range)
> (WW) r128(0): Mode "1600x1200@85x" deleted (hsync out of range)
> ...
> (WW) r128(0): Mode "1600x1200@85x" deleted (no mode of this name)
> (--) r128(0): Virtual size is 1792x1344 (pitch 1792)
> (**) r128(0): Default Mode "1792x1344": 204.8 Mhz, 83.7 kHz, 60.0 Hz

These modes don't fit into the horizontal frequency range you specified in the
Monitor Section.


> (--) r128(0): Virtual Size is 1600x1200 (pitch 1600)
> (**) r128(0): Mode "1600x1200@60x": 162.0 MHz, 75.0 MHz, 60.0 Hz
> 
> So, alter Xf86Config firstly to use Mode "1600x1200@65x" which causes the
> screen to go blank.
> Reboot, look at /var/log/XFree86.0.log which is identical except for:
> 
> (--) r128(0): Virtual Size is 1600x1200 (pitch 1600)
> (**) r128(0): Mode "1600x1200@65x": 175.5 MHz, 81.2 MHz, 65.0 Hz
> 
> Both of these last two attempts did flash up a mangled image of the X
> display for a fraction of a second before going blank.

This is strange. It accepts the modes, but they don't get displayed?

Which depth are you trying? If possible, try using lower depths.


Michel


-- 
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and The DRI Project