Description of problem: The intel driver does not see the second screen, and thus does not allow dual screen setup
Version-Release number of selected component (if applicable): 2.10.0-4.el6.i686
How reproducible: 100%
Steps to Reproduce:
1. connect two screens
2. start x
3. check Xorg.0.log or do 'xrandr -q'
Actual results: Only screen connected via VGA is seen and used
Expected results: Both screens are seen and can be used
Additional info: This is an HP7900 with 00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
Please attach your X logs.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Created attachment 410197 [details]
Created attachment 410199 [details]
Created attachment 410251 [details]
Created attachment 410253 [details]
:0.log from the tarball of logs
Comment on attachment 410251 [details]
johanka:gdm$ cat \:0-slave.log
pam: gdm-password: PAM unable to dlopen(/lib/security/pam_krb5.so): /lib/security/pam_krb5.so: cannot open shared object file: No such file or directory
pam: gdm-password: PAM adding faulty module: /lib/security/pam_krb5.so
pam: gdm-password: pam_unix(gdm-password:session): session opened for user schroder by (uid=0)
This looks bad as well
Concerning pam_krb5: I did an install with package groups 'base' 'desktop' 'X11' and 'Fonts' only, and pam_krb5 is not part of any of these sets. But I don't believe that adding it has an impact on the intel driver ;)
(In reply to comment #9)
> Concerning pam_krb5: I did an install with package groups 'base' 'desktop'
> 'X11' and 'Fonts' only, and pam_krb5 is not part of any of these sets. But I
> don't believe that adding it has an impact on the intel driver ;)
I haven't tried to blame crashing Xorg on missing pam_krb5, just wasn't sure whether it isn't a factor. Leaving this to developers for further analysis.
That's... curious. The X log is only reporting VGA, period. Normally you'd expect to see your other outputs listed as disconnected.
Can you attach dmesg from booting with 'drm.debug=0x04' please?
Created attachment 416319 [details]
dmesg from booting with drm.debug=0x04
as requested, the dmesg from booting with drm.debug=0x04.
This should be resolved by Intel DRM driver updates since the beta was released. Please retest with kernel-2.6.32-33.el6 or later.
I will be glad to test this, but where do I find the newer kernel and drivers?
Beta 2 will be publicly available on FTP and RHN.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
I am a bit puzzled by Comment 16, I have installed beta 2 now, and the problem with the second video out is solved. So what does comment 16 mean?
Comment 16 was added by a bot. It means "we won't go out of our way to fix this in 6.0". But since it appears to be already fixed, we don't have to.
Thanks for testing!