nvidia driver won't work on Gutsy Beta upgrade

Bug #146988 reported by wactuary
4
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xorg

Upgrading from Feisty to Gutsy using sudo apt-get update -d

X server fails to start and regresses to Vesa driver and Screens and Graphics recovery view. At that point it recognizes that I have an Nvidia GeForce 7 Series card and shows proprietary and open-source driver options. If I choose proprietary, I end up at the same screen. If I choose the OSS driver nv, it works fine (but 2D, no acceleration).

Debug stuff attached

Tags: gutsy nvidia
Revision history for this message
wactuary (launchpad-nosnhoj) wrote :
Download full text (12.6 KiB)

[CODE]
chris@megasun:~$ lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation 82P965/G965 Memory Controller Hub [8086:29a0] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:81ea]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Capabilities: <access denied>

00:01.0 PCI bridge [0604]: Intel Corporation 82P965/G965 PCI Express Root Port [8086:29a1] (rev 02) (prog-if 00 [Normal decode])
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 32 bytes
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000a000-0000afff
        Memory behind bridge: fa800000-fe8fffff
        Prefetchable memory behind bridge: 00000000bfe00000-00000000dfdfffff
        Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
        BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
        Capabilities: <access denied>

00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 [8086:2834] (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:81ec]
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 16
        Region 4: I/O ports at dc00 [size=32]

00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:81ec]
        Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin B routed to IRQ 17
        Region 4: I/O ports at e000 [size=32]

00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 02) (prog-if 20 [EHCI])
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:81ec]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin C routed to IRQ 18
        Region 0: Memory at febffc00 (32-bit, non-prefetchable) [size=1K]
        Capabilities: <access denied>

00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Unknown device [1043:81ec]
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Sta...

description: updated
Revision history for this message
wactuary (launchpad-nosnhoj) wrote :

chris@megasun:~$ uname -a
Linux megasun 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux

And attached is the Xorg log.

Revision history for this message
wactuary (launchpad-nosnhoj) wrote :

And here is my xorg.conf file.

Note, I've tried picking my monitor from the Screens and Graphics screen (Dell E171fpb), I've tried picking generic LCD with the correct max resolution and I've tried using dpkg-reconfigure xorg-server and using Medium and Advanced to try to configure the nvidia to no avail.

Here are all the related xorg.conf files. Note there is no current xorg.conf file because the debug wiki suggested deleting it to see if X could autoconfigure. All attempts end up in the same place. It properly identifies the card and lets me select nvidia proprietary driver, but if I select it X won't start and I have to fall back to nv driver.

Revision history for this message
wactuary (launchpad-nosnhoj) wrote :

Fixed with the updates from last night.

Changed in xorg:
status: New → Fix Released
Revision history for this message
Kamba (blamer) wrote :

I have the same problem.
I have latest release of gutsy for 10.10.2007
"Nvidia" argument in "Driver" function in my xorg.conf make my screen black. When i change it on "nv" - OS starts properly, but without 3D-acceleration.

i've tried to install driver using "System settings"-"Advanced"-"Restricted drivers". All i had was black screen.

In some reboot attempt i saw the sign, something like "Your kernel version and your NVidia driver version are different." Maybe, it will be useful information.

Revision history for this message
Jan Pfeifer (pfjan) wrote :

Just upgraded from Feisty do Gutsy (2.6.22-14).

When X tries to start, it just complains that it can't find kernel module "nvidia" (nvidia.ko) -- there is no such file in linux-restricted-modules, according to dpkg --listfiles

I tried reinstalling (apt-get install --reinstall) linux-restricted-modules -- to no effect -- and running nvidia's installation script -- it generated a module that always fails to load.

Just yesterday it was working fine on feisty :(

do you think this could be related ? Any ideas ?

ps.: my xorg.conf driver is set to "Nvidia". I don't want to use "nv" because it won't give me the 2560x1600 of the monitor i'm using. My card is a GTX8800, but i don't think it matters, as the problem is just that the nvidia.ko module isn't there ... (well, maybe it's generated by some other way i'm not aware of).

thx!!! :)

Revision history for this message
Bryce Harrington (bryce) wrote :

Kamba and Jan, this bug is closed so you should report new bugs, but please see http://wiki.ubuntu.com/X/Debugging for directions on how to report bugs and what files to include.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.