Distribution: Debian sid Hardware Environment: Toshiba satellite pro 6100 Software Environment: Problem Description: I power-on the laptop, see a lilo prompt, select the kernel image and from that moment on, my screen is messed up (picture1). I just have to wait a few minutes for X to start op and I'm able to work in X as usual. If I switch from X to console then garbage shows up again (picture 2). This is what I see: picture1: http://213.51.14.124/~stortplaats/IMG_2731.JPG picture2: http://213.51.14.124/~stortplaats/IMG_2728.JPG debbie:/home/kvdb# uname -a Linux debbie 2.5.69 #7 ma mei 5 12:19:30 CEST 2003 i686 unknown unknown GNU/Linux /var/log/messages: May 1 10:16:25 debbie kernel: rivafb: nVidia device/chipset 10DE0175 May 1 10:16:25 debbie kernel: rivafb: On a laptop. Assuming Digital Flat PanelMay 1 10:16:25 debbie kernel: rivafb: Detected CRTC controller 1 being used May 1 10:16:25 debbie kernel: rivafb: RIVA MTRR set to ON May 1 10:16:25 debbie kernel: rivafb: PCI nVidia NV20 framebuffer ver 0.9.5b (nVidiaGeForce4-4, 16MB @ 0xEC000000)
Created attachment 352 [details] 2728
Created attachment 353 [details] 2731
I no longer own this laptop so I can't confirm a fix. Better close this bug if nobody else reported the same problem.
I am seeing the same problem with my Acer TM 630 laptop with 2.6.0. A lspci is here: http://www.odi.ch/prog/tm630/index.php Please note that 2.4.23 works flawlessly.
In 2.6.8.1 the rivafb driver still (despite 2.6.8 patches) fails to initialize in Vesa modes (0x305 etc). Also when running X with the nVidia 5336 drivers, switching to a text console and back hangs the kernel and the screen is messed up!
Created attachment 3970 [details] Accept all modelines if EDID block is absent
The rivafb driver is not compatible with nVidia's binary drivers. The switch from X->console works, it's the console->X switch that hangs, so it's a problem on their part. Nothing much we can do. As for rivafb restricted to certain modes, note that you need to boot rivafb like this: video=rivafb:800x600 for example. The vga=0xxxx is for vesafb only (and a few drivers) If that still does not work, try the patch 'Accept all modelines if EDID block is absent'. Use the latest kernel, preferably mm or rc1. Let me know what happens.
Closing this bug due to lack of feedback. Lots of changes in the rivafb in recent kernels, so most probably this bug is already fixed.