Re: Mobility M1 refresh code problem 2.4.26?
From: Richard Smith <hidden>
Date: 2004-05-06 20:35:50
Mikael Eriksson wrote:
dmesg:
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: Samsung LT141X4-156
id=2, 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, 83 Mhz MCLK, 125 Mhz XCLK
.config:
CONFIG_FB_ATY=y
# CONFIG_FB_ATY_GX is not set
CONFIG_FB_ATY_CT=y
CONFIG_FB_ATY_GENERIC_LCD=y
# CONFIG_FB_ATY128 is not set
boot-param:
video=atyfb:1024x768-32Hmmm... I had GX set. Unsetting and rebuilding did change things. the text is almost readable but its still not quite right. I was doing it as a module rather than at boot time but changing to the driver compiled in still has the same result. My dmesg output is identical to yours. But X still logs a differnt refresh rate code of 7. What refresh rate code is in your X windows log file? I'm doing a make clean;make bzImage right not to be sure its not some holdover of haveing GX enabled on my original build. ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3