Bug 858835 - no graphical output over HDMI on 3.5.x kernels with Intel iGPU on H55 Mainboard
Summary: no graphical output over HDMI on 3.5.x kernels with Intel iGPU on H55 Mainboard
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-19 18:55 UTC by Christian Stadelmann
Modified: 2013-01-11 22:18 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-11 22:18:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
"lspci -vv" output on P7H55-M/USB3, Core i5 650 (28.21 KB, application/octet-stream)
2012-09-19 18:58 UTC, Christian Stadelmann
no flags Details
dmesg output from working 3.4.6 kernel on P7H55-M/USB3, Core i5 650 (72.62 KB, application/octet-stream)
2012-09-19 19:02 UTC, Christian Stadelmann
no flags Details
Xorg.0.log from P7H55-M/USB3, Core i5 650 (67.80 KB, application/octet-stream)
2012-09-19 19:05 UTC, Christian Stadelmann
no flags Details
Xorg.0.log from working 3.4.6 kernel, on P7H55-M/USB3, Core i5 650 (67.80 KB, application/octet-stream)
2012-09-19 19:07 UTC, Christian Stadelmann
no flags Details
"lspci -vv" output from not-working 3.5.3 kernel on P7H55-M/USB3, Core i5 650 (28.23 KB, application/octet-stream)
2012-09-19 19:40 UTC, Christian Stadelmann
no flags Details
dmesg output from not working 3.5.3 kernel on P7H55-M/USB3, Core i5 650 (73.08 KB, application/octet-stream)
2012-09-19 19:41 UTC, Christian Stadelmann
no flags Details
Xorg.0.log from not working 3.5.3 kernel, on P7H55-M/USB3, Core i5 650 (51.37 KB, application/octet-stream)
2012-09-19 19:42 UTC, Christian Stadelmann
no flags Details
dmesg output from 3.5.3 kernel working with VGA on P7H55-M/USB3, Core i5 650 (73.03 KB, application/octet-stream)
2012-09-19 19:52 UTC, Christian Stadelmann
no flags Details
"lspci -vv" output from 3.5.3 kernel working with VGA on P7H55-M/USB3, Core i5 650 (28.23 KB, application/octet-stream)
2012-09-19 19:54 UTC, Christian Stadelmann
no flags Details
Xorg.0.log from 3.5.3 kernel working with VGA, on P7H55-M/USB3, Core i5 650 (45.19 KB, application/octet-stream)
2012-09-19 19:55 UTC, Christian Stadelmann
no flags Details

Description Christian Stadelmann 2012-09-19 18:55:54 UTC
Description of problem:
When booting Fedora 17 from a 3.5.x kernel video stops working after early boot kernel output. Working fine with 3.4.x kernels

Version-Release number of selected component (if applicable): 3.5.x


How reproducible:
With 3.5.x kernel on this hardware: always
With 3.4.x kernel on same hardware: never

Steps to Reproduce:
1. Boot Fedora 17 (selected from grub2)
2. wait until display gets blank


Actual results:
After selecting the 3.5.x kernel from grub2, the screen goes blank. Then the Kernel prints some early boot messages (in 640x480 pixels or so) as expected. After some seconds and more output the screen goes blank and powers off (energy saving mode).

Expected results:
After the screen goes blank it should display the output again with full display resolution (the part where plymouth should take over). Then the HDD encryption prompt (luks for LVM2) should be displayed. After that it should boot to GDM. This is the exact behaviour you can see with 3.3.x and 3.4.x kernels.


Additional info:

1. If typing in the HDD encryption password blindly Fedora continues booting without any further problems but still with a blank screen. I can switch to TTYs and run commands, create files, use pipes to save e.g. dmesg, ….

2. Some basic hardware information:
CPU: Intel Core i5 650 with iGPU (in use)
Mainboard: Asus P7H55-M/USB3
Monitor: Some BenQ via HDMI, 1920x1080 resolution

3. Removing terminal_output=gfxterm does not fix this bug.

4. This bug may or may not be related to ID 852826 or 845388

Do you need more info?

Comment 1 Christian Stadelmann 2012-09-19 18:58:37 UTC
Created attachment 614538 [details]
"lspci -vv" output on P7H55-M/USB3,  Core i5 650

Comment 2 Christian Stadelmann 2012-09-19 19:02:35 UTC
Created attachment 614540 [details]
dmesg output from working 3.4.6 kernel on P7H55-M/USB3, Core i5 650

Comment 3 Christian Stadelmann 2012-09-19 19:05:44 UTC
Created attachment 614541 [details]
Xorg.0.log from P7H55-M/USB3, Core i5 650

Comment 4 Christian Stadelmann 2012-09-19 19:07:08 UTC
Created attachment 614552 [details]
Xorg.0.log from working 3.4.6 kernel, on P7H55-M/USB3, Core i5 650

Comment 5 Christian Stadelmann 2012-09-19 19:40:26 UTC
Created attachment 614576 [details]
"lspci -vv" output from not-working 3.5.3 kernel on P7H55-M/USB3, Core i5 650

Comment 6 Christian Stadelmann 2012-09-19 19:41:10 UTC
Created attachment 614577 [details]
dmesg output from not working 3.5.3 kernel on P7H55-M/USB3, Core i5 650

Comment 7 Christian Stadelmann 2012-09-19 19:42:08 UTC
Created attachment 614578 [details]
Xorg.0.log from not working 3.5.3 kernel, on P7H55-M/USB3, Core i5 650

Comment 8 Christian Stadelmann 2012-09-19 19:49:54 UTC
When booting the 3.5.3 kernel with the same setup but the monitor connected with VGA cable instead of HDMI cable, it boots as expected (as it does with 3.4.x kernels).

Comment 9 Christian Stadelmann 2012-09-19 19:52:54 UTC
Created attachment 614579 [details]
dmesg output from 3.5.3 kernel working with VGA on P7H55-M/USB3, Core i5 650

Comment 10 Christian Stadelmann 2012-09-19 19:54:04 UTC
Created attachment 614580 [details]
"lspci -vv" output from 3.5.3 kernel working with VGA on P7H55-M/USB3, Core i5 650

Comment 11 Christian Stadelmann 2012-09-19 19:55:12 UTC
Created attachment 614581 [details]
Xorg.0.log from 3.5.3 kernel working with VGA, on P7H55-M/USB3, Core i5 650

Comment 12 Christian Stadelmann 2012-11-03 10:31:39 UTC
Seems to be fixed with the latest plymouth update to 0.8.5.0.2012.04.27.4.fc17 for recent 3.6.x kernels. Can anyone confirm that?

Comment 13 Christian Stadelmann 2013-01-11 22:18:10 UTC
Since no one could confirm this bug and it does not occur any more I close it. Feel free to re-open it if you can confirm it.


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