Bug 464936 - No DVI-Output during boot
Summary: No DVI-Output during boot
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-01 14:58 UTC by Chris
Modified: 2008-11-09 10:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-11-09 10:40:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Broken Xorg.0.log with 2.6.27-0.370.rc8 (53.62 KB, text/plain)
2008-10-01 15:00 UTC, Chris 		no flags Details
lspci output (1.76 KB, text/plain)
2008-10-01 15:00 UTC, Chris 		no flags Details
dmesg output with 2.6.26-138.fc10.i686 (53.63 KB, text/plain)
2008-10-28 18:23 UTC, Chris 		no flags Details
dmesg output with 2.6.27.4-58.fc10.i686 (31.86 KB, text/plain)
2008-10-28 18:25 UTC, Chris 		no flags Details
dmesg output with 2.6.27.4-58.fc10.i686 and drm.debug=1 (49.90 KB, text/plain)
2008-10-29 05:41 UTC, Chris 		no flags Details
View All

Description Chris 2008-10-01 14:58:00 UTC 
Description of problem:
The latest rawhide Kernel doesn't provide any graphical output during boot via DVI. The screen switches to powersave-mode.


Version-Release number of selected component (if applicable):
2.6.27-0.370.rc8.fc10.i686
xorg-x11-server-Xorg-1.5.1-2.fc10.i386

How reproducible:
Always

Steps to Reproduce:
1. Connect Screnn to DVI
2. Boot
3. 
  
Actual results:
No signal via DVI until login screen comes up.

Expected results:
Graphical boot logo

Additional info:
VGA output shows graphical boot as expected. The error occurs in every 2.6.27*-kernel. The last 2.6.26 (kernel-2.6.26-138.fc10.i686) works fine and shows output via VGA _and_ DVI
Comment 1 Chris 2008-10-01 15:00:24 UTC 
Created attachment 318205 [details]
Broken Xorg.0.log with 2.6.27-0.370.rc8
Comment 2 Chris 2008-10-01 15:00:55 UTC 
Created attachment 318206 [details]
lspci output
Comment 3 Chris 2008-10-01 17:55:37 UTC 
Same error with 2.6.27-0.372.rc8.fc10.i686
Comment 4 Chris 2008-10-03 20:35:09 UTC 
and with 2.6.27-0.377.rc8.git1.fc10.i686
Comment 5 Chris 2008-10-04 12:50:27 UTC 
and with 2.6.27-0.382.rc8.git4.fc10.i686
Comment 6 Chris 2008-10-05 19:39:40 UTC 
Still the same with 2.6.27-0.391.rc8.git7.fc10.i686
Comment 7 Chris 2008-10-07 13:37:01 UTC 
and 2.6.27-0.392.rc8.git7.fc10.i686
Comment 8 Chris 2008-10-23 01:14:47 UTC 
Still no output with kernel-2.6.27.3-30.rc1.fc10.i686 and plymouth-0.6.0-0.2008.10.17.3.fc10.i386

I checked again the last 2.6.26-kernel (kernel-2.6.26-138.fc10.i686): Works flawlessly and shows graphical boot screen on VGA _and_ DVI...
Comment 9 Dave Jones 2008-10-27 16:59:45 UTC 
does 'nomodeset' make it work?
Comment 10 Dave Airlie 2008-10-27 19:40:34 UTC 
why are you running radeonhd?

please disable radeonhd and let the distro pick the driver.
Comment 11 Dave Airlie 2008-10-27 19:44:43 UTC 
can you also attach the dmesg from both kernel boots when you boot with drm.debug=1.
Comment 12 Chris 2008-10-28 18:23:19 UTC 
Created attachment 321717 [details]
dmesg output with 2.6.26-138.fc10.i686
Comment 13 Chris 2008-10-28 18:25:02 UTC 
Created attachment 321719 [details]
dmesg output with 2.6.27.4-58.fc10.i686
Comment 14 Chris 2008-10-28 18:27:18 UTC 
'nomodeset' helps...

fyi: I'm using radeonhd because radeon (which is picked by Fedora automagically) doesn't show any output at all.
Comment 15 Dave Airlie 2008-10-29 03:43:10 UTC 
actually you mistyped its drm.debug=1 not drm debug=1

the -138 kernel has no modesetting support so its not surprising it works,

so I only need the drm.debug=1 output from the -58 kernel
Comment 16 Chris 2008-10-29 05:41:12 UTC 
Created attachment 321748 [details]
dmesg output with 2.6.27.4-58.fc10.i686 and drm.debug=1
Comment 17 Chris 2008-10-29 05:42:33 UTC 
Hmm...

> Unknown boot option `drm.debug=1': ignoring

for -138 and -58. Attached -58 anyhow.
Comment 18 Dave Airlie 2008-11-02 08:57:33 UTC 
this should be fixed 2.6.27.4-65 or above.
please confirm
Comment 19 Chris 2008-11-05 19:16:50 UTC 
Confirmed. Working perfectly with 2.6.27.4-68
Note You need to log in before you can comment on or make changes to this bug.