On Fri, Feb 24, 2006 at 08:16:52PM +0000, Fractallyte wrote:
> OK, tried out the 18.104.22.168 kernel. dmesg:
> atyfb: using auxiliary register aperture
> atyfb: 3D RAGE Mobility P/M (Mach64 LR, PCI) [0x4c52 rev 0x64]
> atyfb: Mach64 BIOS is located at c0000, mapped at c00c0000.
> atyfb: BIOS frequency table:
> atyfb: PCLK_min_freq 984, PCLK_max_freq 23600, ref_freq 2950,=20
> ref_divider 64
> atyfb: MCLK_pwd 4200, MCLK_max_freq 8300, XCLK_max_freq 12500,=20
> SCLK_freq 5000
> atyfb: BIOS contains driver information table.
> atyfb: colour active matrix monitor detected: Sharp
> atyfb: id=3D1, 1024x480 pixels, 262144 colours (LT mode)
> atyfb: supports refresh rates , default 60 Hz
> atyfb: LCD CRTC parameters: 42.8044 1024 1048 1184 1344 480=20
> 489 495 525
> atyfb: : 23618 160 1024 24 136 30 480 9 6
> atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 236 MHz PLL, 83 Mhz MCLK,=20
> 125 MHz XCLK
> Console: switching to colour frame buffer device 128x30
> atyfb: fb0: ATY Mach64 frame buffer device on PCI
> It's only *seems* to be a success... The console is correctly set to=20
> 128x30, however the timings are apparently not passed from the BIOS to=20
> the console driver. From this point on the screen becomes unreadable=20
> and unusable: white blooms from the edges and spreads inward.
IIRC my OmniBook 500 did the same thing in the past. I don't remember=20
what (if anything) I did to fix it. I tried to fiddle around with the=20
BIOS 'video expansion' option and tried passing various modes to atyfb=20
but I just can't reproduce it.