No video without nvidia driver with 30" screen

Bug #327677 reported by Guillaume Hain
2
Affects Status Importance Assigned to Milestone
xserver-xorg-video-nv (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Hi all,

I had burn the Alpha 4 cd, checksum MD5 of iso, check for errors on disc before install Ubuntu.
I'm using a LG W3000-BN screen ( 30 inch, native resolution is 2560 x 1600 wide screen ).

If I try to boot in LiveCd, or Install Ubuntu, same issue : Black screen, and then, the graphical configuration process start.
I try to launch Ubuntu in Low Mode, but, computer seems not freeze, but black screen again, and CTRL+ALT+F1 do nothing.
When the graphical configuration process start, it show me the last error from logs who said something like "no valid mode found"

I have plug an old 19" screen, and all work fine.
But, my 30" work only after nvidia driver installed and setuped.

So, my point of view is that the nv driver don't try any mode bigger than 1600 x 1200.

P.S: Just to know: Windows work on big screen with small resolution the first time. All is very big, but it work...
Why Ubuntu don't use this way ?

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

Not enough information to troubleshoot. See http://wiki.ubuntu.com/X/Reporting for instructions on reporting X issues.

Changed in xorg:
status: New → Invalid
Revision history for this message
Guillaume Hain (zedtux) wrote :

[14:40:54] sh2[zedtux@zUbuntu][502]~ $ lspci -nn | grep VGA
02:00.0 VGA compatible controller [0300]: nVidia Corporation G80 [GeForce 8800 GTX] [10de:0191] (rev a2)
[14:40:57] sh3[zedtux@zUbuntu][503]~ $

I have reboot on LiveCD, and the only thing I had is an X error message :

(EE) NV(0): Output DVI0 enabled but have no modes
(EE) NV(0): No modes
(EE) Screen(s) found, but none have a usable configuration

CTRL+ALT+F1 is makeing screen black, but nothing happen, but light on keyboard are not forzen.
If I try CTRL+ALT+F7 to back to video, screen still black.

When screen is black, after CTRL+ALT+F1, if I plug an 20" screen, it said "Out of range".

I have no other idea about how get logs ...

Changed in xorg:
status: Invalid → New
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi zedtux,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Changed in xserver-xorg-video-nv:
status: New → Incomplete
Revision history for this message
Guillaume Hain (zedtux) wrote :
Download full text (11.5 KiB)

I can post Xorg.0.log* cause it happen on LiveCD.

Result of lspci -vvnn :

[23:08:39] sh1[zedtux@zUbuntu][500]~ $ lspci -vvnn
00:00.0 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03ea] (rev a1)
 Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: <access denied>

00:01.0 ISA bridge [0601]: nVidia Corporation MCP61 LPC Bridge [10de:03e0] (rev a2)
 Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
 Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Region 0: I/O ports at 0900 [size=256]

00:01.1 SMBus [0c05]: nVidia Corporation MCP61 SMBus [10de:03eb] (rev a2)
 Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Interrupt: pin A routed to IRQ 10
 Region 0: I/O ports at dc00 [size=64]
 Region 4: I/O ports at 0600 [size=64]
 Region 5: I/O ports at 0700 [size=64]
 Capabilities: <access denied>
 Kernel driver in use: nForce2_smbus
 Kernel modules: i2c-nforce2

00:01.2 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03f5] (rev a2)
 Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

00:02.0 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller [10de:03f1] (rev a3) (prog-if 10)
 Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0 (750ns min, 250ns max)
 Interrupt: pin A routed to IRQ 23
 Region 0: Memory at dbfff000 (32-bit, non-prefetchable) [size=4K]
 Capabilities: <access denied>
 Kernel driver in use: ohci_hcd
 Kernel modules: ohci-hcd

00:02.1 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller [10de:03f2] (rev a3) (prog-if 20)
 Subsystem: ASUSTeK Computer Inc. Device [1043:8234]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0 (750ns min, 250ns max)
 Interrupt: pin B routed to IRQ 21
 Region 0: Memory at dbffec00 (32-bit, non-prefetchable) [size=256]
 Capabilities: <access denied>
 Kernel driver in use: ehci_hcd
 Kernel modules: ehci-hcd

00:04.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI bridge [10de:03f3] (rev a1) (prog-if 01)
 Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Steppi...

Revision history for this message
Guillaume Hain (zedtux) wrote :

I have post the lspci -vvnn, and now wait to know if there is/are other way(s) to help you.

tags: removed: needs-lspci-vvnn
Changed in xserver-xorg-video-nv (Ubuntu):
status: Incomplete → New
Bryce Harrington (bryce)
tags: added: needs-lspci-vvnn
Changed in xserver-xorg-video-nv (Ubuntu):
status: New → Incomplete
Revision history for this message
Guillaume Hain (zedtux) wrote :

Any explanations !!?

lspci -vvnn have been posted ! So what are waiting for !?

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

The fix for bug 385658 redoes how card detection works with -nv and may solve this bug. Please test Karmic-beta or newer and verify if it does.

Changed in xserver-xorg-video-nv (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Guillaume Hain (zedtux) wrote :

Download started, I'll try it and let you know !

Thanks !

Revision history for this message
Guillaume Hain (zedtux) wrote :

Amd64 version have failed on boot, with an error about loop0 and sr0, but 32bits version have work fine !!

So this ticket could be closed !

Thanks !

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

Thank you for reporting this issue about xserver-xorg-video-nv. Starting
with Lucid, Ubuntu is transitioning to using the -nouveau video driver
by default instead of -nv. The reason for this change is because
upstream development for the -nv driver has been quite slow. We are
quite pleased with the upstream development speed for -nouveau, and hope
this will translate into swifter bug fixes as well.

Because of this, I'm closing this bug report at this time. I'm marking
it wontfix because what you describe is probably a valid issue, but we
do not have further plans to work on it in Ubuntu. If you would still like
to see this issue investigated, I would encourage you to file it
upstream at http://bugs.freedesktop.org/.

Changed in xserver-xorg-video-nv (Ubuntu):
status: Incomplete → Won't Fix
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.