You can see the full details of my hardware and configuration in this bug: https://bugzilla.redhat.com/show_bug.cgi?id=707747
Everything worked fine in F15 with my dual monitors. When I upgraded to F16 Alpha, my DVI output disappeared (it is listed as HDMI3 in the xrandr output in the bug linked to above).
My current xrandr output looks like this:
Screen 0: minimum 320 x 200, current 1200 x 1920, maximum 8192 x 8192
LVDS1 connected (normal left inverted right x axis y axis)
1600x900 60.0 + 50.0
800x600 60.3 56.2
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
DP2 connected 1200x1920+0+0 left (normal left inverted right x axis y axis) 518mm x 324mm
Note the lack of HDMI3/DP3. I do have the DVI cable plugged in and nothing else has changed since my upgrade to F16 Alpha.
dmesg? the 3.0 kernel or 3.1-rcX kernel?
The only interesting thing in dmesg is:
[drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
Interestingly, if I boot a f15 kernel I still get the same problem. I've tried:
Also interesting is that the boot splash used to show up on both of my monitors, but now just the one... Same for GDM...
Which kernel do you want dmesg for? Do you want Xorg.0.log as well?
oh wierd, did you test fc15 with 2.6.40 before upgrading?
can you boot with drm.debug=4 on the 3.1.0-0-rc3 kernel, and make/model of the laptop.
I did not test 2.6.40 before upgrading.
Created attachment 519838 [details]
dmesg on 3.1.0-0.rc3.git0.0.fc16.x86_64
Created attachment 519839 [details]
Well, this is wierd... I just downgraded glibc to glibc-2.14.90-4.1 because it was causing a crash in pulseaudio, and all of a sudden DVI started working again. Is there some user-space component that is broken here?
I am unable to reproduce the problem with glibc-2.14.90-4.1 installed.
The alpha contained glibc-2.14.90-4 - not glibc-2.14.90-6. Can you confirm that you only saw this after updating to updates-testing?
No because I didn't install the alpha but upgraded from f15 directly to updates-testing...
As it stands right now my system is fully updates-testing except for glibc which is 2.14.90-4 and everything works.
However, what I'm not understanding is why KMS would depend on glibc...
Try to check /var/log/messages and dmesg (or abrt-gui) for coredumps. Some essential tool might have failed to do its job.
Reassigning to glibc, and closing since I suspect it's fixed in -10. Please reopen if not.