Bugzilla – Bug 113781
broken frambuffer (nvidia) after first reboot
Last modified: 2005-09-01 11:21:41 UTC
After the first reboot of SL 10.0 installation my screen is broken. The screen is split vertically and the left half of the screen is on the right and right half of the screen is on the left side of the monitor. I can finish the installation but it's quite funny because if you want to reach the right half of the screen (which is physically on left) you have to go to the right with the mouse. I tried to take a screenshot (via PrintScreen btn) of the installer, but the screenshot is OK. my hwinfo and y2logs are attached. PS: not only the installer's screen is broken but also the text console (the same graphical effect). Installing nvidia binary drivers helps and the system is runing fine then.
Created attachment 47944 [details] y2logs
Created attachment 47945 [details] hwinfo output
Please attach /etc/X11/xorg.conf and /var/log/Xorg.0.log for the "nv" driver configuration, i.e. configure X11 again with "sax2 -r".
Created attachment 48409 [details] Xorg.0.log
Created attachment 48410 [details] xorg.conf
This are the config and logfiles for the "nvidia" driver. Please call "switch2nv" and attach the new files after restarting the Xserver again.
sorry you were faster ;) but anyway, here is my comment: Log/configs after running "sax2 -r". However sax2 configured xorg with "nvidia" driver, so if you need something else please let me know. I tried manually change the Driver in Device section to "nv" and it is almost working normally. The only (but annoying) problem I have now is my text cursor in text areas like this one (in html form). It is blinking in a weird way - always one half of the cursor is visible - either the bottom or the top one. If I try to move with cursor keys the cursor is not erased and I can see vertical "lines" all around the text. I'm swithing back to "nvidia" ;)
Created attachment 48413 [details] Xorg.0.log
Created attachment 48414 [details] xorg.conf
still the same problem with cursor as described above.
another thing that came up into my mind. After first reboot the screen was "broken". But this was only in the installer (at the place where you should type the root password etc). After kdm started the screen was again "normal" (except that annoying thing with cursor)
Unfortunately for switching from nvidia to nv driver you need to reboot before since these drivers don't like each other. The cursor problem will went away when doing this. But since you're saying that you cannot produce this problem any longer with running the "nv" driver and the config and logfile right after installation are no longer available I need to close this one now. Or do you like to reinstall the machine? Then please reopen after attaching the new config and logfile. This time please the "nv" ones.
I can reinstall - no problem. So I should send you the same logs/configs as above before I touch anything? But as I said - after the kdm start the problem appears only in the text console and X are running fine.
> another thing that came up into my mind. After first reboot the screen was > "broken". But this was only in the installer (at the place where you should > type the root password etc). Strange. At this moment "fbdev" driver is still in use (instead of "nv"). Maybe "nvidiafb" kernel module has been loaded after reboot. Can you check this please with "lsmod"? This problem has been fixed with Beta4. > After kdm started the screen was again "normal" (except > that annoying thing with cursor) At this time "nv" driver is in use. So "nv" is ok.
Ok. Check first if "nvidiafb" module is loaded with "lsmod".
I think that nvidiafb was loaded, but I'm not sure. I'll check that with beta4 and reopen if there are any problems.
Thanks. This would be fine.
so. I'm trying to install beta4. This time after the first reboot the ncurses yast started comlaining that graphical interface could not be started. Although this is definitely better than the "broken" GUI I'm not sure whether this is not a bug (GUI not running). The installation prior to the reboot was graphical and everything went smoothly so I don't understand why after the reboot yast2 is unable to start in graphical mode. I'll not touch my test machine, so if you need some special logs/output of lsmod etc... please let me know. PS: nvidiafb is NOT loaded
This is probably a complete different problem. Please open a seperate bugreport for this (YaST component). P.S.: Good to see that nvdidiafb is no longer loaded by default.
Thanks. Opened new bug (bug #114676).