Bug 684688 - [NV96] DVI display doesn't work with nouveau and GeForce 9500GT
Summary: [NV96] DVI display doesn't work with nouveau and GeForce 9500GT
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-14 08:49 UTC by Elad Alfassa
Modified: 2018-04-11 12:48 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1029188 (view as bug list)
Environment:
Last Closed: 2012-08-07 15:33:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/messages (232.12 KB, text/plain)
2011-03-18 08:57 UTC, Elad Alfassa
no flags Details
/var/log/Xorg.0.log (45.26 KB, text/plain)
2011-03-18 08:58 UTC, Elad Alfassa
no flags Details
dmesg output (124.24 KB, text/plain)
2011-03-18 09:01 UTC, Elad Alfassa
no flags Details
dmesg output (without debugging flags) (124.24 KB, text/plain)
2011-03-21 08:53 UTC, Elad Alfassa
no flags Details
dmesg output (without debugging flags) (69.01 KB, text/plain)
2011-03-21 08:54 UTC, Elad Alfassa
no flags Details
/var/log/messages (without debugging flags) (271.95 KB, text/plain)
2011-03-21 08:55 UTC, Elad Alfassa
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 35307 0 None None None Never

Description Elad Alfassa 2011-03-14 08:49:26 UTC
My monitor is usually connected to my computer with a DVI cable.
When using nouveau and the DVI cable, the monitor goes into sleep mode (and doesn't wake up, like when the computer is off) as soon as grub finishes loading the kernel (and the boot process starts). I can't even get a tty. I got this computer around the time Fedora 13 alpha was released, and it didn't work then, not in Fedora 14.

Yesterday, while testing a Fedora 15 Alpha LiveUSB, i switched the DVI cable to a VGA one, and to my surprise, it worked perfectly.

I don't want to use the VGA cable on daily basis, because the DVI one is much better.

Comment 1 Matěj Cepl 2011-03-18 00:31:36 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer (with VGA cable), and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

Also, would it be possible to start with DVI cable at least in the text mode (add number 3 to the kernel command line in grub) and then run startx as normal user? What happens? Could we get the same logs from this attempt as well?

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Elad Alfassa 2011-03-18 08:57:47 UTC
Created attachment 486184 [details]
/var/log/messages

Comment 3 Elad Alfassa 2011-03-18 08:58:18 UTC
Created attachment 486185 [details]
/var/log/Xorg.0.log

Comment 4 Elad Alfassa 2011-03-18 09:01:12 UTC
Created attachment 486187 [details]
dmesg output

Using DVI, I can't get anything on the monitor, even in runlevel 3 or even runlevel 1.

This is a (Fedora 15 Alpha) LiveUSB so I don't have any custom xorg.conf.
These logs that I've attached now are form boot with both VGA and DVI connected to the same monitor (and choosing VGA in the monitor configuration). If that's a problem, I'll get new logs with only VGA connected.

Comment 5 Matěj Cepl 2011-03-18 13:56:31 UTC
(In reply to comment #4)
> These logs that I've attached now are form boot with both VGA and DVI connected
> to the same monitor (and choosing VGA in the monitor configuration). If that's
> a problem, I'll get new logs with only VGA connected.

Awesome, thank you!

Comment 6 Ben Skeggs 2011-03-20 23:19:45 UTC
Both /var/log/messages and dmesg are missing some important info that nouveau generates during startup.  Could I get a dmesg log from a normal boot (so, without debugging flags) too please?

Comment 7 Elad Alfassa 2011-03-21 08:53:06 UTC
Created attachment 486567 [details]
dmesg output (without debugging flags)

Comment 8 Elad Alfassa 2011-03-21 08:53:47 UTC
Comment on attachment 486567 [details]
dmesg output (without debugging flags)

oops wrong file

Comment 9 Elad Alfassa 2011-03-21 08:54:15 UTC
Created attachment 486569 [details]
dmesg output (without debugging flags)

Comment 10 Elad Alfassa 2011-03-21 08:55:09 UTC
Created attachment 486570 [details]
/var/log/messages (without debugging flags)

Comment 11 Elad Alfassa 2011-04-08 06:33:56 UTC
Is there anything else I can do to help debug this issue?

Comment 12 Mark Thompson 2011-12-19 14:14:50 UTC
I see the same "blank screen" issue with an Nvidia 8400GS card when the monitor is attached to the DVI port only.  Reproduced using Fedora 14 i686 LiveCD, Fedora 16 i686 LiveCD, and after a Fedora 14->16 upgrade.  Works OK when attached to the video card's VGA port.  I can attach logs as well if they would help.

Comment 13 Ondrej X Dolezal 2012-06-28 07:25:37 UTC
I think I am hitting the same bug however in different setup
- Fedora 17 clean install, nvidia geforce 9500GT (NV96) with 2 HDMI ports
both connected to a monitor. With nouveau, the secondary display never wakes
up (primary is fine); with proprietary drivers everything works as expected.
I would be glad to help with any debugging.

Comment 14 Fedora End Of Life 2012-08-07 15:33:23 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.