[GUTSY] Black screen with nvidia-glx on Quadro4 500 GoGL

Bug #146342 reported by ari häyrinen
2
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx

Enabling nvidia-glx driver from restricted drivers results a black screen on next boot. Switching to text mode works but X shows nothing.

OS:Gutsy Beta
PC: Fujitsu Siemens Celsius Mobile H

Here is output from lspci -vv:
01:00.0 VGA compatible controller: nVidia Corporation NV17GL [Quadro4 500 GoGL] (rev a3) (prog-if 00 [VGA])
 Subsystem: Siemens Nixdorf AG Unknown device 0089
 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: 248 (1250ns min, 250ns max)
 Interrupt: pin A routed to IRQ 10
 Region 0: Memory at d8000000 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at f0000000 (32-bit, prefetchable) [size=128M]
 Region 2: Memory at e8000000 (32-bit, prefetchable) [size=512K]
 [virtual] Expansion ROM at e8080000 [disabled] [size=128K]
 Capabilities: [60] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [44] AGP version 2.0
  Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
  Command: RQ=32 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=x4

Here is output from dpkg -l nvidia-glx|grep ii:
nvidia-glx 1:1.0.9639+2.6 NVIDIA binary XFree86 4.x/X.Org driver

Here is a xorg.log:
http://www.opendimension.org/Xorg.0.log

Revision history for this message
ari häyrinen (ari-hayrinen) wrote :
Revision history for this message
ari häyrinen (ari-hayrinen) wrote :

Ok, I investigated further and it seems that this is more a hardware detection problem. By adding following line to xorg.conf I managed to get it work:

Option "ConnectedMonitor" "DFP"

So it seems that the monitor was not detected properly?

Revision history for this message
ari häyrinen (ari-hayrinen) wrote :

One more piece of information:

arihayri@arihayri-laptop:~$ sudo get-edid
get-edid: get-edid version 1.4.1

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
        Function supported
        Call successful

        VBE version 300
        VBE string at 0x11110 "NVidia"

VBE/DDC service about to be called
        Report DDC capabilities

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
        Function supported
        Call successful

        Monitor and video card combination does not support DDC1 transfers
        Monitor and video card combination does not support DDC2 transfers
        0 seconds per 128 byte EDID block transfer
        Screen is not blanked during DDC transfer

Reading next EDID block

VBE/DDC service about to be called
        Read EDID

        Performing real mode VBE call
        Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
        Function supported
        Call failed

The EDID data should not be trusted as the VBE call failed
Error: output block unchanged

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

(Sounds similar to Bug #109414 )

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

Hi ari-hayrinen,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in linux-restricted-modules-2.6.22:
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in linux-restricted-modules-2.6.22:
status: Incomplete → Invalid
Revision history for this message
ari häyrinen (ari-hayrinen) wrote :

Thanks for response and sorry for delay.
This was fixed in Hardy. Not tested with Intrepid.

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.