[nvidia-glx] Using nvidia-glx driver, X is blank after install or upgrade (laptop/Geforce Go) without option "UseDisplayDevice" "DFP"

[charlvj]

Binary package hint: nvidia-glx

I have a Dell Latitude C840 with an nVidia graphics card (and the nVidia driver).

I upgraded from Edgy to Feisty just yesterday (28 Jan 2007). A few minor problems with the upgrade came up and it seems like I managed to fix them OK. I rebooted and found that my X terminal is completely blank. I got the login-ready-sound and thought I would go on and enter my login name and password, then the harddrive started working and the login-sound sounded. Everything seem to work fine except I can't see a thing.

Adding
Option "UseDisplayDevice" "DFP"
to the Screen section of /etc/X11/xorg.conf solves the problem

[Sebastien Bacher (seb128)]

does it happen if you uninstall beryl?

[charlvj (charlvj)]

I just uninstalled beryl and all the other beryl-* packages, and I still have this problem.

[Chris Burgan (cburgan)]

I believe that whenever you upgrade the kernel you need to reinstall the proprietary drivers. Can you include your xorg.conf or just see if it modified what drivers it's using?

Try referring to http://doc.gwos.org/index.php/Latest_Nvidia_Edgy

It kind of backs up theory by stating:
 "Every time you change or upgrade your kernel you will have to reinstall the Nvidia driver, no matter which method you used to install the driver."

It will also show you how to install via command line in recovery mode. It says it's for edgy but I am pretty sure it's the same method for feisty.

[charlvj (charlvj)]

I saw the comments in the xorg.conf file and noticed the command to automatically reconfigure X, so I ran it:
sudo dpkg-reconfigure -phigh xserver-xorg
Then restarted X, and now it is working OK.

I did not see the nVidia logo, so I checked the xorg.conf file again. I saw that in the Device section, the driver is set to "nv", instead of "nvidia" as it was before I ran the above command. (According to the ubuntuguide for edgy, the "nv" had to be changed to "nvidia".) When I made this change I had the same problem as before.

Is it a nVidia driver problem?

[charlvj (charlvj)]

Oh, and I forgot to point out that I did not make any change to the xorg.conf file after the upgrade, so the upgrade did not correctly reconfigure the xorg.conf file when the upgrade was made, only when I did it manually.

[charlvj (charlvj)]

Chris, sorry I didn't see your reply...

Thanks for your reply, it kinda backs up my theory as well. I will look into the link you sent me and will report back if I have any successes or not.

I am a little confused though. I have had loads of updates of the kernel through update-manager in the past, but I can't remember if the nvidia driver was updated each time, even so I never had a problem before.

Do you want to see my xorg.conf file of before I did the reconfigure? I guess so, I attach it.

[charlvj (charlvj)]

Umm, sorry, the description of the attached file is incorrect. It is the xorg config file BEFORE the reconfigure.

[Chris Burgan (cburgan)]

The "Nv" drivers are the open source nvidia drivers, you could try setting that to "nvidia" but I doubt that will fix it. Like I said, I'm pretty sure you need to reinstall the nvidia proprietary drivers.

[Chris Burgan (cburgan)]

actually when I first read the xorg.conf I thought it was after, if it's before and the "nvidia" drivers are coming up as a blank screen then changing it back will just meet with the same results.

The update-manager might have handled the problem on it's own (not sure). Let me know how it goes.

[charlvj (charlvj)]

update-manager Just had a load of updates, but no nvidia ones. I checked with synaptic and I have the following nvidia installed:
1.0.9631+2.6.20.1-6 (feisty)
So, it looks like the nvidia-driver was updated to one for feisty.

[Chris Burgan (cburgan)]

Ok I'm going to move this to the restricted modules package for Feisty as the nvidia proprietary drivers are located there. If your xorg.conf says "nv" then what you're looking at in synaptic is most likely the feisty version of the open source drivers. I can't really tell you more, if you want to try to reinstall them it might fix it. Other than that, by moving it here hopefully someone else can possibly come up with another suggestion.

[Joseph Price (pricechild)]

I advise you to get a fresh xorg.conf

sudo dpkg-reconfigure xserver-xorg -phigh

And then prepare it for nvidia:

sudo nvidia-xconfig

Then restart your X server and all "should" be good.

[charlvj (charlvj)]

Thanks, Unfortunately no success though. :-(

I did the reconfigure and then the nvidia config as you suggested. When I restarted X it seemed liked X didn't want to come up right. I couldn't even switch to one of the consoles and had to restart my system. After restart it behaved pretty much the same way it did before - welcome drums and all but no graphics.

I did another reconfigure to get it working again.

[charlvj (charlvj)]

This morning I had an update for both gdm and nvidia, so I thought I would try it all again. So, I did sudo nvidia-xconfig, but no success. I decided to reinstall nvidia-glx package again, but it still didn't work - just the blank screen.

[Michael Asher (asherlm)]

I also have a Latitude C840 with the Geforce4 400 Go. I was able to make my display work properly by using the nvidia-glx-legacy packages.

I also had to add the following in /etc/X11/xorg.conf to make anything GL run reasonably well.

Section "Extensions"
 Option "Composite" "Disable"
EndSection

[zeddock (zeddock)]

I am on a Dell Latitude D800 with GeForce4 Go 4200 Ti AGP8
I see, (or should I say don't see,) the same problem.

Please change this to high and confirmed for Fiesty release?

[jesusthepirate (souldrain69)]

not a big deal.

from the black screen when you boot up, press CTRL+ALT+F2 to get a console, log in.

next, please:
sudo dpkg-reconfigure xserver-xorg -phigh
sudo nvidia-xconfig
nano /etc/X11/xorg.conf

in xorg.conf please locate the section "Screen" and add an option line like so:
     Option "UseDisplayDevice" "DFP"

you may also want to use this opportunity to change the default color depth from 16 to 24

i've attached my xorg.conf

the laptop this xorg.conf runs on is a Dell Latitude C840 w/ GeForce GO MX440 64MB w/ 1400x1050px LCD

[Will Simpson (linux.photo.geek)]

jesusthepirate - hey thanks. I had this problem exactly and your process worked great.

Dell Inspiron 8200 w/GeForce4 440 Go 32MB @ 1400x1050 LCD

[Flabdablet (flabdablet)]

The attached xorg.conf fixed this issue on my Dell Inspiron 8200 (used with nvidia-glx, not nvidia-glx-legacy).

Once you have basic nvidia functionality again, have a play with the nvidia-settings tool; all sorts of nice things can be done.

[jesusthepirate (souldrain69)]

Thanks for the update flabdablet... until I read your comment, it didn't occur to me that my post wasn't really that informative.. I guess I was just focusing on getting people back up and running.

First of all, as far as I know, there is absolutely no reason to run the legacy drivers, so please don't... glad it worked for Michael Asher, but the 440-go isn't on the legacy list, so that might be a bad idea overall.

The issue here is obviously very simple: we're defaulting to the wrong display, which is why the DFP is actually turned off, not just blank or corrupt (like when encountering other problems nvidia binary driver setup on a Latitude C840 / Inspiron 8200)

Option "UseDisplayDevice" "DFP"
conveniently tells x.org what display to use, which is why the display works on your 8200, not to mention why the display works on my C840.

just to be clear since i'm sure a decent few people will be skimming through here: please do not just download other people's xorg.conf file (like flabdablet's or my own) and replace yours with them. it's pretty much a bad idea to just go copying entire xorg.conf files from other people, as they covers quite a few settings. (such as the resolution, my xorg.conf is for a 1400x1050px screen, flabdablet's is for a 1600x1200px screen.. and both our notebooks were available with either screen.) It's a much better idea to read the xorg.conf file and compare the options in appropriate sections with the options in your own xorg.conf file.

To clarify on the instructions I posted above, the commands are intended to
A. reset xorg.conf to a defaults file,
B. have nvidia set it's defaults,
C. splice in the UseDisplayDevice option.

hopefully that clears up a little bit about where the problem lies and what my instructions do, for those who may be a little shaky on either...

[Urs (oerz)]

OMG, JTP!
Have you got any idea how many hours I spent with this issue?!
I found sooooo many posts with the same, there must be hundreds of cursing people out there racking their brains.
You could make some people happy... - in fact, you did!

With your help, I just made an important step towards installing WoW on Feisty... :D
THANKS!!
Cheers,
oerz

[Flabdablet (flabdablet)]

For the benefit of others who spent ages tracking this down: next time
something weird happens to your video display, dive straight into
/var/log/Xorg.0.log and do your best to make sense of it.

The penny dropped for me when I saw no error (EE) lines at all - as
far as X was concerned, everything was working just fine (which would
explain why the login screen's drum sound happened as expected, and
why I was still able to switch consoles with Ctrl-Alt-F1 or cause an X
restart with Ctrl-Alt-Backspace).

But there was a line saying "Assigned Display Device: CRT-0" in there,
and it occurred to me that not only was my flat panel completely
black, but the backlight was turned off, as if X had been told to use
an entirely different display.

Googling "xorg options nvidia" got me here:

http://http.download.nvidia.com/XFree86/Linux-x86/1.0-8774/README/appendix-d.html

and a quick edit to the URL to match the nvidia driver version from
Xorg.0.log got me here:

http://http.download.nvidia.com/XFree86/Linux-x86/1.0-9631/README/appendix-d.html

and the rest was straightforward.

I still don't understand why, left to its own devices, the nvidia
driver autodetects a CRT when there isn't one connected but doesn't
detect my TV-out port at all; is this a Dell BIOS thing? It's good to
have options available to override all the automatic behaviour,
though.

[Sitsofe Wheeler (sitsofe)]

charlvj:
Does using
Option "UseDisplayDevice" "DFP"
with the nvidia-glx drivers resolve the issue for you?

[Sitsofe Wheeler (sitsofe)]

Setting to needsinfo pending reply from charlvj.

[charlvj (charlvj)]

Sorry for taking so long to reply. Unfortunately my laptop broke 2 weeks ago. So I am working on a PC now. I will check if this solves the problem once I get the laptop to work again, if that ever happens.

Thanks.

[Simon Oosthoek (simon-margo)]

I upgraded my old laptop from edgy to feisty yesterday, I only use this laptop to view videos on my TV and the upgrade broke this completely, I cannot get my TV-out to work anymore using the nvidia glx drivers.

the graphics hardware is the GeForce4 420 Go

the relevant sections of my xorg.conf:

Section "Device"
  identifier "nvidia0"
  boardname "NVIDIA GeForce FX (generic)"
  busid "PCI:1:0:0"
  driver "nvidia"
  screen 0
  vendorname "NVIDIA"
  Option "ConnectedMonitor" "DFP"
EndSection

Section "Monitor"
  identifier "Monitor0"
  vendorname "generic 1400x1050 lcd"
  modelname "jewel laptop"
  HorizSync 31.0-75.0
  VertRefresh 59
  gamma 0.76
EndSection

Section "Device"
    Identifier "nvidia1"
    Driver "nvidia"
    Screen 1

    # Edit the BusID with the location of your graphics card
    BusId "PCI:1:0:0"
    Option "ConnectedMonitor" "TV"
EndSection

Section "Monitor"
    Identifier "tv0"
    VendorName "Generic"
    ModelName "TV 16:9"
    HorizSync 30-50
    VertRefresh 60
    DisplaySize 295 167

    # TV fullscreen mode or DVD fullscreen output.
    # 768x576 @ 79 Hz, 50 kHz hsync
    ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630

    # 768x576 @ 100 Hz, 61.6 kHz hsync
    ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616
EndSection

Section "Screen"
  Identifier "Screen0"
  Device "nvidia0"
  Monitor "Monitor0"
  DefaultDepth 24
  SubSection "Display"
    depth 24
    modes "1400x1050"
  EndSubSection
EndSection

Section "Screen"
    Identifier "Screen1"
    Device "nvidia1"
    Monitor "tv0"

    Subsection "Display"
        Depth 24
        Modes "800x600" "640x480"
    EndSubsection
    DefaultDepth 24
EndSection

Section "ServerLayout"
  Identifier "Default Layout"
   Screen 0 "Screen0"
   Screen 1 "Screen1" RightOf "Screen0"
  InputDevice "Generic Keyboard"
  InputDevice "Configured Mouse"
EndSection

Some errors in my /var/log/Xorg.0.log:
(--) NVIDIA(1): Connected display device(s) on GeForce4 420 Go at PCI:1:0:0:
(--) NVIDIA(1): Nvidia Default Flat Panel (DFP-0)
(--) NVIDIA(1): Nvidia Default Flat Panel (DFP-0): 224.0 MHz maximum pixel
(--) NVIDIA(1): clock
(--) NVIDIA(1): Nvidia Default Flat Panel (DFP-0): Internal Dual Link LVDS
(EE) NVIDIA(1): Unable to find available Display Devices for screen 1.

I guess I will have to try an older version of the nvidia driver to see if that fixes it...

[Simon Oosthoek (simon-margo)]

I can't get 8776 to compile on the feisty kernel and 9629 doesn't fix the problem.

Could it be a kernel-nvidiamodule interaction problem?

Anyway, I'll be reverting to edgy on this machine :-(

[Flabdablet (flabdablet)]

I think the problem is that the current nvidia drivers interact with
x.org in strange and wondrous ways, and work more things out for
themselves than they used to, and take less notice of some bits of
xorg.conf than they used to. So before you give up on Feisty: start
with the stock Feisty nvidia-glx package, back up your present
xorg.conf, then replace the bits you've posted here with this fairly
minimal set:

Section "Device"
 identifier "Default Device"
 driver "nvidia"
EndSection

Section "Monitor"
 identifier "Default Monitor"
 HorizSync 31.0-75.0
 VertRefresh 59
 gamma 0.76
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "Default Device"
 Monitor "Default Monitor"
 DefaultDepth 24
 Option "Nologo" "true"
 Option "RenderAccel" "true"
 Option "UseEvents" "true"
 Option "ConnectedMonitor" "dfp, crt, tv"
 Option "UseDisplayDevice" "dfp"
 SubSection "Display"
  Depth 24
  Modes "1400x1050" "1280x1024" "1280x960" "1024x768" "800x600"
"640x512" "640x480" "512x384" "400x300" "320x240"
 EndSubSection
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen" 0 0
 InputDevice "Generic Keyboard"
 InputDevice "Configured Mouse"
EndSection

That should get you up and running with a nice accelerated display on
your flat panel. Once you have that, run the command

nvidia-settings

in a terminal, and mess about with the GUI. You should see all three
display devices (DFP, CRT and TV) represented as boxes in the GUI
under "X Server Display Configuration". The CRT and TV will show as
"disabled" but they will at least be there, and there are a bunch of
options that let you choose what to do with them. Use the GUI to
generate a new x.org config file (don't save it over the existing
one), then edit the new file to put back the Options listed above,
then try backing up the working one and using the new one instead.

[Simon Oosthoek (simon-margo)]

thanks, the line
 Option "ConnectedMonitor" "dfp, crt, tv"
did help eventually!

After I got a working single monitor display going and this line in the Screen section, the nvidia-settings picked it up and configured it (first with the screens in the wrong order, causing the login screen to appear on the TV, but that's quite easily fixed)

After some cleaning up, it now looks like this:

Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" RightOf "Screen1"
    Screen 1 "Screen1" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "Nvidia Default Flat Panel"
    HorizSync 29.0 - 65.0
    VertRefresh 0.0 - 60.0
    Option "DPMS"
EndSection

Section "Monitor"
    # HorizSync source: builtin, VertRefresh source: builtin
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "TV-0"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DPMS"
EndSection

Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce4 420 Go"
    BusID "PCI:1:0:0"
    Screen 0
EndSection

Section "Device"
    Identifier "Videocard1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce4 420 Go"
    BusID "PCI:1:0:0"
    Screen 1
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Videocard0"
    Monitor "Monitor1"
    DefaultDepth 24
    Option "metamodes" "DFP: 1400x1050 +0+0"
    SubSection "Display"
        Depth 24
        Modes "1400x1050"
    EndSubSection
EndSection

Section "Screen"
    Identifier "Screen1"
    Device "Videocard1"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "metamodes" "TV: 800x600 +0+0"
    SubSection "Display"
        Depth 24
        Modes "800x600" "640x480"
    EndSubSection
EndSection

[Sitsofe Wheeler (sitsofe)]

A warning to potential future posters:
Please do not post new queries saying "My X is broken please help me fix it" to this bug report. The correct place to ask these types of queries is over at https://answers.launchpad.net/ , http://ubuntuforums.org/ and the other means described on http://www.ubuntu.com/support/communitysupport . Please read also read https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia - it has links to bug reports talking explictly covering certain common problems. If your issue really isn't covered then please consider filing a new bug report rather than extending this one if you are looking for something more than a "quick fix".

[Simon Oosthoek (simon-margo)]

Hey, nice warning, but I thought the problem was related and relevant, turned out it wasn't and as a side effect, I got a fix.

If you discourage people from posting additional information (which may not be relevant, but not everyone can tell), you will discourage people from writing bugreports entirely.

I'm sorry for disturbing the peace in the quiet backwaters of launchpad, nevermind me!

[Flabdablet (flabdablet)]

Sitsofe, is there anything you think can be done about this, beyond
possible inclusion of a warning about known issues on upgrade and a
link to the BinaryDriverHowto/Nvidia page in the package description?

[Sitsofe Wheeler (sitsofe)]

Simon:
The comment was not aimed at you. I don't expect people to be psychic and magically know that they can get faster (and sometimes better) responses without an endless back and for (which can last days, months or even years on bug reports) elsewhere depending on their problem. I don't expect them to already know that the system works better if a new bug is marked as duplicate of an old bug if it turns out to already be a known issue (Why? Because if it turns out that the bug was new and not related then you haven't confused the original bug with unrelated information). I don't expect them to have already scanned through the entirety of the BinaryDriver help page (including the disjointed Troubleshooting section at the bottom which most people won't get to due to its buried nature). You can't expect people to do any of these things unless you tell them about them first. I thought I was informing people - your comment clearly tells me that I was wrong. All I was doing was creating angst.

I don't want to discourage people from reporting new bugs when they are using the Ubuntu provided software. I want people to get the fastest and most appropriate resolution to their problem (and bug reports are not always the best way to do that). I want Ubuntu to improve in the long run and for it to be supportable. I don't want people to add a comment and then never have a reply (and then in turn become frustrated) simply because they commented in the "wrong place". I don't want bugs that are so big that people no longer know what they are about and where the solutions are no longer visible. I don't want to chase away the people who look at bug reports and take the time to reply to them by frustrating them with bugs that contain dozens of issues. I don't want the bustling river that is launchpad to turn into a becalmed lake but nor do I want it to burst it banks and turn the surrounding land into marsh.

(A brief aside. Since you have working TV-Out do you think you can help the people over in Bug #109703 solve their int10 issue?)

Like you I am just another Ubuntu user. I have been spending time looking at NVIDIA binary driver bug reports (https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=nvidia+glx&orderby=-date_last_updated ) trying to make some of them useful and ensure they have the information they need, trying to check whether the original reporter's issue is clear and has been resolved and trying to adjust titles to try and maximise the information they provide. Given your reaction, I think we might be better off if I scaled back this work (or stopped entirely) as it seems to be counter-productive.

Flabdablet:
I think the best thing would be to see if NVIDIA can be contacted and helped to improve their display detection so that the right thing is more likely to happen out of the box for more people. I don't know how feasible or easy this is to do though.

[Loïc Martin (loic-martin3)]

@ Sitsofe
I think you're doing (and have been doing) a good job - you will always have some people overreact or not understand you, however your advice was valid and given in a nice way.

@ Simon
We all learn by making mistakes (at the beginning). Actually, we all learn *if* we accept we can make mistake and listen to other's advices without overreacting "you will discourage people from writing bugreports entirely".
Launchpad and bug reporting have been new to most of us at the beginning. At the time, we also had our "Sitsofe" helping us like he just helped you, and thanks to them we have learnt to use it better - that's why you too have been able to find helpful and relevant information here.

To summarize what you can do if you happen to be in the same situation again : open a new bug report https://bugs.launchpad.net/ubuntu/+filebug and fill it will all the information you got, then you can write a nice comment here "I've got a different problem but it might be related, could you please see <add here a link towards your bug report> and tell me if it's a duplicate?".
Then edit your bug description with a link to this bug, explaining that it could be related to it.

This way you don't just get help, you also will _provide_ help for the ones with the same problem you have (many people might be affected by the bug you encounter), because it would be hard for them to find the solution hidden in a bug concerning another problem :)

[Loïc Martin (loic-martin3)]

The bug is reproducible and the fix too. It happens on scratch Feisty install and upgrades from Edgy as well. It is not linked to Beryl/Compiz.

[Simon Oosthoek (simon-margo)]

Loic, thanks for the advice, I didn't intend the negative vibe of my message, but I guess Sitsofe's comment triggered an old sour spot in my mind. I'll try to be more careful next time.

Regarding this bug, it was part of my set of problems that the display was blank, so I thought it was the same or similar bug (Elsewhere I've learned that filing a duplicate was considered bad form, but apparently the culture is different here).

Generalising, this bug is related to the core bug of nvidia changing the driver in incompatible ways and the friction between closed source drivers and an open source community. Trying to provide support the combination is tough and you're doing a respectable job, thankless as it may be! But thanks from me, anyway :-)

Cheers

Simon

[Sitsofe Wheeler (sitsofe)]

I just want to follow up on the recent comments. Simon contacted me privately by mail shortly after my previous comment and it was agreed by both sides that my "warning" (a loaded term in the first place) could have been better worded. We both overreacted but subsequently all misunderstandings have been worked out and I for one consider this side of things to have been resolved and in no need of further discussion. Hopefully the comments contained here will help others learn more about the nature of NVIDIA binary bugs, launchpad bug reporting AND launchpad bug triage!

[Timo Aaltonen (tjaalton)]

Moving forward and setting priority.

[unggnu (unggnu)]

This still happens with current Hardy RC with Geforce 440 Go 64 MB. I guess it should be reported upstream since it is a closed source driver bug.

[Wei-Ning Huang (aitjcize)]

I have the same problem. The screen just gone black after gdm. but if I press ctrl + alt + f1 then press ctrl + alt + f7, i can get the screen to work properly...
After I added (Option "UseDisplayDevice" "DFP") in xorg.conf, it still didn't work...
Anyone knows how to fix it?

it's Nvidia GeForce 7150M
Driver version: the newest 180.08

I install the dirver because i saw that it fixed the problem " Fixed a regression that could result in window decoration corruption when running Compiz using Geforce 6 and 7 series GPUs."
and it did, but i got a bigger problem ....

Here's my Xorg.conf:

Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "Module"
    Load "dbe"
    Load "extmod"
    Load "type1"
    Load "freetype"
    Load "glx"
EndSection

Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DPMS"
EndSection

Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
        Depth 24
    EndSubSection
    #Option "UseDisplayDevice" "DFP"
EndSection

thanks,
Francis

[Jarl (jarl-dk)]

I am still affected by this bug in Jaunty.

Why is this bug not fixed yet. It would be so easy for the ubuntu package to add the "UseDisplayDevice" "DFP" to the xorg.conf file for all laptops

This is not an upstream driver bug, from the README, appendix B (http://us.download.nvidia.com/XFree86/Linux-x86_64/180.51/README/appendix-b.html), the documentation says under the option UseDisplayDevice:

<quote>
Of the list of display devices considered for this X screen (either all connected display devices, or a subset limited by the "UseDisplayDevice" option), the NVIDIA X driver first looks at CRTs, then at DFPs, and finally at TVs. For example, if both a CRT and a DFP are connected, by default the X driver would assign the CRT to this X screen. However, by specifying:

    Option "UseDisplayDevice" "DFP"

the X screen would use the DFP instead.
</quote>

So it is well documented that all laptops which has a VGA connector must specify Option "UseDisplayDevice" "DFP" to ensure the driver would assign the DFP to the X screen.

And it is also very clear from the Xorg.0.log that this is the way the driver behaves. Take a look at this diff of Xorg.0.log_black and Xorg.0.log_DFP

[Simon Fogliato (simonfogliato)]

HP-Pavilion-tx1000-Notebook-PC
nVidia Corporation C51 [Geforce Go 6150] (rev a2)
Ubuntu 10.10 (maverick)

https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia
       "Screen Blanks/Monitor Turns Off"

I live in fear to activate the nVidia driver on any laptop.

[Jussi (jussi-lahtinen-gmail)]

Importance low!!??
For non-technical persons this means totally dead computer!
You cannot even get to internet to search for help!
Also this bug happens automatically with upgrade form 10.04 to 10.10!

[Bryce Harrington (bryce)]

Thank you for reporting this issue about a driver from the
linux-restricted-modules package. lrm-2.4.24 was shipped with Ubuntu
8.04 which reached end-of-life for desktop support on May 12th, 2011.

For that reason, this bug report is being closed at this time. I'm
marking it wontfix because what you describe is probably a valid issue,
but there are no plans to work on lrm 2.4.24 bugs further.

The issue may be resolved in a newer version. If not, aside from filing
a new bug report, another angle may be to file it directly with the
driver vendor.

[Emilian Bold (emilianb)]

Thanks for the update, but I won't be trying to duplicate the bug and re-open it on a newer Ubuntu release because that particular laptop showing the bug died of old age.

It seems a bit odd to use 'Won't Fix' on a 4 year bug that was delayed so much it got outside the LTS(!) window. There should really be another classification for this kind of bugs.