Lots more details here: https://bugzilla.novell.com/show_bug.cgi?id=416044 but the long and short of it is that with the x.org driver that came with opensuse 10.3 *and* 11.0 *and* the latest (2.1.10) I get nothing but a blank screen. sndirsch@suse.de notes the following: Anyway, it's weird which panel size the driver is detected here. (II) NV(0): Output LVDS using initial mode 512x384 (--) NV(0): Virtual size is 1680x1680 (pitch 1792) (**) NV(0): Default mode "512x384": 32.5 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz (D) and it wasn't really much better before: (II) NV(0): Output LVDS using initial mode 1920x1200 (--) NV(0): Virtual size is 1920x1920 (pitch 2048) (**) NV(0): Driver mode "1920x1200" (**) NV(0): Default mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz (II) NV(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
Still present using opensuse 11.1, which uses xorg 7.4. The actual package is: xorg-x11-driver-video-7.4-19.4 More details here: https://bugzilla.novell.com/show_bug.cgi?id=460729 The 'nv' driver has not worked for me with this laptop, ever.
Other freedesktop.org bugs that seem like the same issue: http://bugs.freedesktop.org/show_bug.cgi?id=13184 http://bugs.freedesktop.org/show_bug.cgi?id=12637
The nv driver (currently using openSUSE 11.3, package xorg-x11-driver-video 7.5-15.2) has a very hit-or-miss success rate for me. Typically when it fails it the last thing in the Xorg.0.log is: [ 53.699] (==) NV(0): DPMS enabled Which, when it *works*, is right before RANDR is enabled/detected/whatever. I'll note that I can use the nouveau driver, but nouveau has other issues ( https://bugzilla.novell.com/show_bug.cgi?id=625257 ). I'm generally very available for testing different things. Is the nv driver being phased out in favor of nouveau?
Nobody is supporting xf86-video-nv and it will be going away at some point in the future. If your problem persists with nouveau or the proprietary driver provided by nVidia, please re-file accordingly. We apologize for the inconvenience. This is part of an automated bulk action; if you believe that this bug was closed in error, then change the targeted component and reopen it.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.