Bug 20168 - nVIDIA 9600GT KMS Blank Screen
Summary: nVIDIA 9600GT KMS Blank Screen
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-17 10:19 UTC by Kyle K
Modified: 2009-03-11 13:16 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (19.77 KB, application/octet-stream)
2009-02-17 10:19 UTC, Kyle K
no flags Details

Description Kyle K 2009-02-17 10:19:51 UTC
Created attachment 23043 [details]
dmesg

As per Ben's request, here's a new bug ;)
All of this takes place in a vc/1. Please look at the attached dmesg.

05:00.0 VGA compatible controller: nVidia Corporation G94 [GeForce 9600 GT] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: nVidia Corporation Device 0545
	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, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at f8000000 (64-bit, non-prefetchable) [size=32M]
	Region 5: I/O ports at 6c00 [size=128]
	[virtual] Expansion ROM at fb000000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel modules: nvidia, nvidiafb
Comment 1 Maarten Maathuis 2009-02-17 10:23:12 UTC
Kernel modules: nvidia, nvidiafb

That's bad twice, you shouldn't load the blob and nvidiafb.
Comment 2 Kyle K 2009-02-17 12:56:16 UTC
Maarten, I think those modules got loaded because I passed vga=795 option to the kernel. I'm using vanilla kernel and nvidia blob wasn't installed. Well I removed vga=795, modprobe -r nvidiafb, and I still get the blank screen. When ssh'ing to the machine dmesg seems to get overflowed with:

[drm:nv50_dac_detect] Using bios provided load_pattern of 520
[drm:nv50_dac_detect] Load was detected on output with or 1
[drm:nv50_connector_hpd_detect] Hotplug detect returned negative for bus 1
[drm:nouveau_nv50_i2c_irq_handler] NV50_PCONNECTOR_HOTPLUG_CTRL - 0x00100010
[drm:nv50_connector_hpd_detect] Hotplug detect returned positive for bus 0
[drm:nv50_dac_detect] Using bios provided load_pattern of 520
[drm:nv50_dac_detect] Load was detected on output with or 1
[drm:nv50_connector_hpd_detect] Hotplug detect returned negative for bus 1
[drm:nouveau_nv50_i2c_irq_handler] NV50_PCONNECTOR_HOTPLUG_CTRL - 0x00100010
[drm:nv50_connector_hpd_detect] Hotplug detect returned positive for bus 0
[drm:nv50_dac_detect] Using bios provided load_pattern of 520
[drm:nv50_dac_detect] Load was detected on output with or 1
[drm:nv50_connector_hpd_detect] Hotplug detect returned negative for bus 1
[drm:nouveau_nv50_i2c_irq_handler] NV50_PCONNECTOR_HOTPLUG_CTRL - 0x00100010
[drm:nv50_connector_hpd_detect] Hotplug detect returned positive for bus 0
....
....
....

Comment 3 Maarten Maathuis 2009-02-17 13:30:21 UTC
Perhaps the unconditional enabling of many hotplug irq's has turned on a "bad" one.

Short time bypass would to be to not enable them, ~line 130 in linux-core/nv50_display.c

Long term solution requires mapping all the irq bits, assuming that it is indeed the problem.

On a different note, besides the existing 0xe050/0xe054 registers, a fairly similar 0xe070/0xe074 has appeared, perhaps just on g9x cards?

I'll leave Ben to decide.
Comment 4 David Heidelberg (okias) 2009-03-11 06:59:30 UTC
try again with lastest GIT, it solved all problems for me :-)
Comment 5 Kyle K 2009-03-11 13:16:02 UTC
Thanks okias, git works for me also.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.