Bug 588275

Summary: No output on VGA since upgrading from kernel-2.6.33.2-41
Product: [Fedora] Fedora Reporter: Sven Lankes <sven>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: ajax, anton, dougsland, gansalmon, itamar, jonathan, kernel-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-07 09:36:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg of working kernel
none
dmesg of non-working kernel
none
Xorg.log using working kernel (-41)
none
Xorg.log using non-working kernel (-41) none

Description Sven Lankes 2010-05-03 11:40:47 UTC 
Every kernel since 2.6.33.2-41 (tested up to -78) only boots up showing one display.

This is a Dell Optiplex 760 with onboard intel graphics and a DVI and VGA port.

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

When I boot one of the newer Kernels plymouth only shows on the DVI display - the VGA one is put to sleep.

This could be related to #584229

I'm attaching dmesg and Xorg.0.log for the -78 and the -41 Kernel.
Comment 1 Sven Lankes 2010-05-03 11:42:18 UTC 
Created attachment 410946 [details]
dmesg of working kernel
Comment 2 Sven Lankes 2010-05-03 11:42:50 UTC 
Created attachment 410947 [details]
dmesg of non-working kernel
Comment 3 Sven Lankes 2010-05-03 11:43:29 UTC 
Created attachment 410949 [details]
Xorg.log using working kernel (-41)
Comment 4 Sven Lankes 2010-05-03 11:43:59 UTC 
Created attachment 410950 [details]
Xorg.log using non-working kernel (-41)
Comment 5 Sven Lankes 2010-05-07 09:36:45 UTC 

*** This bug has been marked as a duplicate of bug 587171 ***