[Linux-fbdev-devel] Re: Patch: Make atyfb framebuffer device support LCD monitors (fwd)

[<da...@de...>]

On Fri, 8 Feb 2002, Geert Uytterhoeven wrote:

> I gave it a try on my Sony Vaio PCG-Z600TEK. Unfortunately the screen was
> either black (booted without arguments, i.e. in 640x480) or grey (booted =
with
> video=3D1024x768-60). When I typed (blindly), I saw some flicker on each =
line
> feed. Using fbset didn't change anything.
>=20
> Relevant dmesg output:
> | atyfb: using auxiliary register aperture
> | atyfb: Mach64 BIOS is located at c0000, mapped at c00c0000.
> | atyfb: BIOS contains driver information table.
> | atyfb: colour active matrix monitor detected: Hitachi TX31D72VC1CAA =20
> |         id=3D2, 1024x768 pixels, 262144 colours (LT mode)
> |         supports 60 Hz refresh rates, default 60 Hz
> |         LCD CRTC parameters: 15384 167 127 130 0 17 805 767 769 6
> | atyfb: 3D RAGE Mobility (PCI) [0x4c4d rev 0x64] 8M SDRAM, 29.498928 MHz=
 XTAL, 230 MHz PLL, 50 Mhz MCLK
> | Console: switching to colour frame buffer device 80x25
> | fb0: ATY Mach64 frame buffer device on PCI
>=20
> Dani=EBl: IIRC, you have a RAGE LT PRO. Did you get any success stories f=
rom
> people with a RAGE Mobility?

Okay, still not perfect, it seems :( I think the problem must be your
monitor, because the chapter about LCD in documentation of the LT PRO and
the Mobility is exactly the same.

Could you try to connect a conventional monitor to your laptop and try to
boot it in the reference video mode (1024x768x60 Hz)? Make sure your LCD
monitor is also switched on, otherwise the patch will do nothing. If the
CRT image is not correct, something goes wrong with the LCD CRTC
parameters.

Dani=EBl Mantione