Bugzilla – Bug 370159
nvidia: Bogus DPI values
Last modified: 2008-03-15 21:31:23 UTC
Opening "YaST -> Hardware -> Graphics Card and Monitor" turned my screen completely blue. I SSHed into the machine and rebooted it, but it's still blue. I still have SSH access, but can't get the screen back.
Ok. Please attach /var/log/SaX.log.
Created attachment 201946 [details] SaX.log
Same issue when you run a) "sax2" b) "sax2 -r" Does it work for you if you switch to runlevel 3 ("init 3") and then run "sax2"?
I have no usable screen, so I will need some direction on how to do those over SSH.
Ok. I suggest to boot into runlevel 3. Just add 3 to the boot prompt. Or if you login with ssh, after login type "unset DISPLAY", then "init 3" and then "sax2".
In runlevel 3, running "sax2" made my screen turn blue. Then I left my screen on and opened an SSH session. Running "sax2 over SSH spit different output to my SSH console than I got straight from the terminal and made the screen flicker a bit, but then it turned back to blue. I closed that SSH session, opened another and ran "sax2 -r" and some KDE windows appeared on my screen. However, the text is so large (about 8 letters across fit on the screen) that I cannot tell what is actually on the screen (probably related to this bug https://bugzilla.novell.com/show_bug.cgi?id=334138) Neither the "sax2" nor "sax2 -r" commands completed. They both appeared to freeze. Then when I rebooted my machine the screen was back to blue.
Created attachment 202239 [details] SaX.log after running "sax2 -r" and rebooting
Ok. So you get complete bogus DPI values from your monitor. Try the following sax2 -r -m 0=nv This should give you a working nv driver configuration. Replace the "nv" driver entry in /etc/X11/xorg.conf with "nvidia". Then you get probably the blue screen again. If you can confirm this behaviour it's a nvidia driver issue, which can be workarounded with some nvidia driver options as you already figured out.
Yes, "sax2 -r -m 0=nv" fixed my problem and changing the driver entry to nvidia caused it to reappear. I had thought that I did not have the nVidia driver installed due to the problems it has caused me in the past. However, it was indeed installed, so I had to uninstall it. Would SaX have installed this for me when I clicked on "Graphics Card and Monitor"?
>Would SaX have installed this for me when I clicked on "Graphics Card and >Monitor"? Yes, when you've installed the official openSUSE RPMs available from the NVIDIA server (YaST2 -> Community Repositories -> NVIDIA Repository), SaX2 will use the NVIDIA driver for configuration. Since you uninstalled the NVIDIA driver I'm assuming you don't want to use it. Otherwise please reopen the bugreport. Then I'm trying to figure out, what's wrong (either bogus monitor data or a bug in monitor detection of the NVIDIA driver).
I would like to use the nVidia driver, but only uninstalled it because I haven't ever been able to get it to work. I am not reopening this bug at this point because I am assuming it is the same as bug 334138. If these are separate issues, please let me know and I will reopen and provide debug info. -Thanks for your help
Ok. Please attach /var/log/Xorg.0.log right after nvidia driver was in use. See commment #8. Of course you need to reinstall the NVIDIA driver first. Does adding Option "UseEdidDpi" "FALSE" to Section "Device" of your /etc/X11/xorg.conf help?
Created attachment 202322 [details] /var/log/Xorg.0.log
I do need Option "UseEdidDpi" "FALSE" for the text to be properly sized. With the nVidia driver installed, the screen is blue about 50% of the time I reboot regardless of whether the UseEdidDpi method is used.
(**) NVIDIA(0): Option "UseEdidDpi" "FALSE" (**) NVIDIA(0): DPI set to (95, 96); computed from "DisplaySize" Monitor (**) NVIDIA(0): section option This is with the option. So it helps. More interesting is of course the logfile when the option is *not* in use.
Created attachment 202323 [details] /var/log/Xorg.0.log without Option "UseEdidDpi" "FALSE"
Here we are. (--) NVIDIA(0): DPI set to (812, 866); computed from "UseEdidDpi" X config (--) NVIDIA(0): option These values are completely bogus.
Appearently this is a duplicate of Bug #334138. Even exactly the same bogus DPI values. Maybe the same monitor.
This not only the same monitor. This is also the same graphics card and now I finall noticed that it is THE SAME BUGREPORTER So you reported the same issue twice. Thanks! *** This bug has been marked as a duplicate of bug 334138 ***
Yes, I'm quite sorry to have wasted your time. I at first thought there was a separate issue since problems opening a window in YaST didn't seem related to a bad DPI value. However, in comment 11 I said that I thought this bug was a duplicate. You asked for more info right after, so I assumed you thought they must not be. Sorry for any miscommunication on my part.