GeForce FX 5700 - Digital DVI output turned off on boot, X11 does not see the output at all.

Bug #1155926 reported by MMlosh
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I upgraded to Raring and lost my digital video output.

The computer has "01:00.0 VGA compatible controller: NVIDIA Corporation NV36.2 [GeForce FX 5700] (rev a1)" video card.
The card has two connectors (VGA and DVI-I) and provides THREE video outputs (2x analogue, 1x digital)

The card's bios correctly detects which outputs are connected and uses them.
I can see BIOS and GRUB on digital.
But then the kernel boots and turns the DVI-I:Digital output off (and turns on DVI-I:Analogue)

I am planning to reinstall that machine, so I don't mind running unverified kernels on them.
Mainline kernel will be tested next.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1155926

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
MMlosh (mmlosh) wrote :

I am unable to run apport (to get my sound configuration published as requested)
It's broken on Raring. ( #1150335 )

I browsed syslog & dmesg for any interesting info and found none.
I'll attach the actually necessary info as soon as requested.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
MMlosh (mmlosh) wrote :

I tried a mainline kernel: mainline/v3.9-rc2-raring
It works.

tags: added: kernel-fixed-upstream
Revision history for this message
MMlosh (mmlosh) wrote :

I ran that kernel and did
sudo apt-get update & sudo apt-get upgrade.
it did what was there to do....

..and left me in a root shell !
Or maybe both user and root shell fighting over the VT1 input.
Hitting Ctrl+D (crashed? and) rebooted the computer.
That is really weird and I further undermines my trust into kernel downloaded over plain HTTP. (no HTTPS, no signature)

PS: kernel 3.8.0-12 does not fix the issue

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
tags: added: needs-bisect
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you also test the latest v3.8 stable kernel with is:

v3.8.4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.4-raring/

Revision history for this message
MMlosh (mmlosh) wrote :

v3.8.4 turns the screen off.. The issue exists in there.

Revision history for this message
penalvch (penalvch) wrote :

MMlosh, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
MMlosh (mmlosh) wrote :

Well..

This is what happens with 13.10's 3.11.0-13 kernel. (reboot after I installed it)
The screen goes dark (probably not off) for a couple of seconds after hitting enter in grub.
Then it goes back on, writing startup messages (first one is, strangely, starting SystemD login service)

I did a full power cycle..
the screen got dark for 12 seconds (I measured it this time)
and the first message displayed was what I expected (fsk message saying disk is OK)

(+ a different issue emerged: In both cases the SLiM login manager was started (incorrectly) on VT1. )

It's not perfect, but I guess it allows you to mark this issue fixed :)

Revision history for this message
penalvch (penalvch) wrote :

MMlosh, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1155926/comments/8 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.