Bug 590044

Summary: installation misguesses the serviceability of the "NV" video driver
Product: [openSUSE] openSUSE 11.3 Reporter: Bruce Korb <bruce.korb+suse>
Component: X.OrgAssignee: Stefan Dirsch <sndirsch>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <xorg-maintainer-bugs>
Severity: Critical    
Priority: P3 - Medium    
Version: unspecified   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.2   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Bruce Korb 2010-03-21 21:45:01 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4

I have a video card that announces itself as:
  G96 [GeForce 9400 GT]
When installing the latest openSuSE/Debian/Red Hat, I get the
black screen of death upon booting into run level 5.  The
keyboard is inoperable, so I have to cycle power to get out
of the situation.  Obviously, this is not a SuSE issue, but
the nv driver issue.  What _is_ a SuSE issue is that the
installation code can verify that the video driver is working
correctly before making a permanent installation.  You can
well imagine how much work it takes to reboot into run level 3
and then try to divine what went wrong.  There are _no_ error
messages, you know.  The driver thinks everything is fine and
dandy.  It is just that nobody ever types anything in.  Nothing
wrong with that.  Eventually after a couple of re-installs and
a couple of dozen reboots, I finally got the nvidia driver
downloaded and the configuration hand merged from one of the
working OS images I had on my disk.

I think the process was too hard.

Reproducible: Always

Steps to Reproduce:
1. Buy an nVidia GeForce 9400 GT card
2. Install it
3. Install 11.2
Actual Results:  
Black screen and non-responsive keyboard.

Expected Results:  
Working installation.
Comment 1 Marcus Schaefer 2010-03-22 09:10:38 UTC 
assigned to X11 maintainers
Comment 2 Stefan Dirsch 2010-03-22 09:36:28 UTC 
dup

*** This bug has been marked as a duplicate of bug 577140 ***