From: Stephan D. <dr...@fr...> - 2007-04-21 17:35:36
|
Hi list, I've just compiled Linux 2.6.20 on my Fujitsu FMV-253L with ATI Rage Mobility P/M. Enabling the according framebuffer and giving the video=atyfb:... kernel option doesn't work properly, however. With the panels native resolution of 1024x512, I can see that the screen is initialised properly (to the full resolution), but consists only of white on-pixel-wide vertical stripes. Some sort of blinking in the area of the curser is also visible. Changing to other resolutions (640x480) didn't change much, same white stripes, but now with black borders left and right. Changing timing information for atyfb (with M and R options in mode) didn't help, so did enabling the native panel interface in the kernel. Funny thing is, that everything works fine in X.org with the ati/mach64 driver, with a custom modeline. Any ideas / patches, I might try out? Thanks in advance, Stephan |
From: Ville <sy...@sc...> - 2007-04-22 00:15:19
|
On Sat, Apr 21, 2007 at 07:35:27PM +0200, Stephan Diestelhorst wrote: > Hi list, > I've just compiled Linux 2.6.20 on my Fujitsu FMV-253L with ATI Rage > Mobility P/M. > > Enabling the according framebuffer and giving the video=atyfb:... kernel > option doesn't work properly, however. > > With the panels native resolution of 1024x512, I can see that the screen is > initialised properly (to the full resolution), but consists only of white > on-pixel-wide vertical stripes. Some sort of blinking in the area of the > curser is also visible. Try booting with video=atyfb:xclk:63. > Changing to other resolutions (640x480) didn't change much, same white > stripes, but now with black borders left and right. > > Changing timing information for atyfb (with M and R options in mode) didn't > help, so did enabling the native panel interface in the kernel. What is this 'native panel interface'? -- Ville Syrjälä sy...@sc... http://www.sci.fi/~syrjala/ |
From: Stephan D. <lan...@we...> - 2007-04-22 14:25:12
|
> > With the panels native resolution of 1024x512, I can see that the screen > > is initialised properly (to the full resolution), but consists only of > > white on-pixel-wide vertical stripes. Some sort of blinking in the area > > of the curser is also visible. > > Try booting with video=atyfb:xclk:63. Thanks, that helps partly! I can see a proper picture, however just in the left 2/3 of the screen, I guess that is 640x480. It is also slightly shifted downward. What does xclk do? Where can I find proper docs for the driver? (In the usual place aka. the source?) > > Changing timing information for atyfb (with M and R options in mode) > > didn't help, so did enabling the native panel interface in the kernel. > > What is this 'native panel interface'? It is the kernel option FB_ATY_GENERIC_LCD (probably this, together with your fix could make things work perfectly, again) Thanks for the quick and helpful repy! --Stephan |
From: Stephan D. <dr...@fr...> - 2007-04-22 18:13:22
|
> > With the panels native resolution of 1024x512, I can see that the screen > > is initialised properly (to the full resolution), but consists only of > > white on-pixel-wide vertical stripes. Some sort of blinking in the area > > of the curser is also visible. > > Try booting with video=atyfb:xclk:63. Thanks, that helps partly! I can see a proper picture, however just in the left 2/3 of the screen, I guess that is 640x480. It is also slightly shifted downward. What does xclk do? Where can I find proper docs for the driver? (In the usual place aka. the source?) > > Changing timing information for atyfb (with M and R options in mode) > > didn't help, so did enabling the native panel interface in the kernel. > > What is this 'native panel interface'? It is the kernel option FB_ATY_GENERIC_LCD. Enabling it and your proposed kernel argument resulted in a pefectly working framebuffer! Yieppieh! Thanks! :) Thanks for the quick and helpful repy! --Stephan |
From: Ville <sy...@sc...> - 2007-04-22 19:19:45
|
On Sun, Apr 22, 2007 at 08:13:19PM +0200, Stephan Diestelhorst wrote: > > > With the panels native resolution of 1024x512, I can see that the screen > > > is initialised properly (to the full resolution), but consists only of > > > white on-pixel-wide vertical stripes. Some sort of blinking in the area > > > of the curser is also visible. > > > > Try booting with video=atyfb:xclk:63. > > Thanks, that helps partly! I can see a proper picture, however just in the > left 2/3 of the screen, I guess that is 640x480. It is also slightly shifted > downward. What does xclk do? It sets the memory clock to 63 MHz. Typically the BIOS tables specify 125 MHz, but for some laptops that's too much. There have been a few reports about laptops with 32bit memory interfaces that require halved XCLK (I had one). Please post the boot messages from atyfb so I can confirm that your case is similar. > Where can I find proper docs for the driver? (In > the usual place aka. the source?) Yes. -- Ville Syrjälä sy...@sc... http://www.sci.fi/~syrjala/ |
From: Stephan D. <dr...@fr...> - 2007-04-22 20:55:46
|
> Please post the boot messages from atyfb so I can > confirm that your case is similar. Kernel command line: root=/dev/hda3 resume=/dev/hda1 video=atyfb:xclk:63 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, ref_divider 64 atyfb: MCLK_pwd 4200, MCLK_max_freq 8300, XCLK_max_freq 12500, SCLK_freq 5000 atyfb: BIOS contains driver information table. atyfb: colour active matrix monitor detected: 1024x512 Wide TFT Panel atyfb: id=7, 1024x512 pixels, 262144 colours (LT mode) atyfb: supports refresh rates [60], default 60 Hz atyfb: LCD CRTC parameters: 39.1795 1024 1032 1120 1184 512 513 527 550 atyfb: : 25595 64 1024 8 88 23 512 1 14 atyfb: 4M SDRAM (2:1) (32-bit), 29.498928 MHz XTAL, 236 MHz PLL, 83 Mhz MCLK, 63 MHz XCLK atyfb: fb0: ATY Mach64 frame buffer device on PCI As already mentioned, works flawlessly with full resolution now! > > Where can I find proper docs for the driver? (In > > the usual place aka. the source?) > > Yes. I should have guessed ;) I was fooled by the aty128fb.txt docs in kernel-source Documentation/fb/ Thanks, Stephan |