| Summary: | nVIDIA 9600GT KMS Blank Screen | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Kyle K <kylek389> | ||||
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | normal | ||||||
| Priority: | medium | CC: | madman2003 | ||||
| Version: | git | ||||||
| Hardware: | Other | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
Kernel modules: nvidia, nvidiafb That's bad twice, you shouldn't load the blob and nvidiafb. 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 .... .... .... 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. try again with lastest GIT, it solved all problems for me :-) 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.
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