Description of problem: Hot swapped in Samsung S24A450 to replace Samsung 2443BW display (also 1920x1200 native format). Using VGA connection, via Belkin KVM (VGA). Linux systems are Intel and Radeon on-die graphics, connected to VGA connector on motherboards. Initially worked fine on 4 systems (2 W7, 2 X86_64 F20). Both W7 systems rebooted OK. On F20 w/Radeon, logged out and got 1024x768 mode. Xorg log shows what appears to be defaulted EDID. Rebooting F20 w/Intel got blank (black( display. Rebooting into F21 x86_64 Beta TC4 gets the same. I got a temporary Samsung 1920x1080 display until this is fixed. That reported valid EDID, I tried monitor-edid utility on F20, but that reported failure. Using "EDID Manager" on W7, I was able to extract EDID and get raw+formatted values. Ajax hopes this is EDID not yet supported by X, Version-Release number of selected component (if applicable): [root@wallace sa450]# rpm -qa | grep xorg | sort abrt-addon-xorg-2.2.2-1.fc20.x86_64 xorg-x11-drv-ati-7.2.0-3.20131101git3b38701.fc20.x86_64 xorg-x11-drv-evdev-2.8.4-1.fc20.x86_64 xorg-x11-drv-fbdev-0.4.3-10.fc20.x86_64 xorg-x11-drv-intel-2.21.15-7.fc20.x86_64 xorg-x11-drv-mga-1.6.2-8.fc20.x86_64 xorg-x11-drv-modesetting-0.8.0-2.fc20.x86_64 xorg-x11-drv-nouveau-1.0.9-2.fc20.x86_64 xorg-x11-drv-openchrome-0.3.3-2.fc20.x86_64 xorg-x11-drv-qxl-0.1.1-4.fc20.x86_64 xorg-x11-drv-synaptics-1.7.6-6.fc20.x86_64 xorg-x11-drv-vesa-2.3.2-10.fc20.x86_64 xorg-x11-drv-vmmouse-13.0.0-6.fc20.x86_64 xorg-x11-drv-vmware-13.0.2-4.20140613git82c9b0c.fc20.x86_64 xorg-x11-drv-wacom-0.23.0-5.fc20.x86_64 xorg-x11-fonts-Type1-7.5-9.fc20.noarch xorg-x11-font-utils-7.5-18.fc20.x86_64 xorg-x11-glamor-0.5.1-3.20140115gitfb4d046c.fc20.x86_64 xorg-x11-proto-devel-7.7-10.fc20.noarch xorg-x11-server-common-1.14.4-11.fc20.x86_64 xorg-x11-server-utils-7.7-6.fc20.x86_64 xorg-x11-server-Xorg-1.14.4-11.fc20.x86_64 xorg-x11-utils-7.5-12.fc20.x86_64 xorg-x11-xauth-1.0.9-1.fc20.x86_64 xorg-x11-xinit-1.3.4-1.fc20.x86_64 xorg-x11-xkb-utils-7.7-8.fc20.x86_64 How reproducible: -100% Steps to Reproduce: 1.Connect Monitor 2.Use xrandr, reboot, or attempt to boot F21 beta TC3 3.Sigh. Actual results: EDID not recognized. Expected results: EDID recognized, Native preferred 1920x1200 available. Additional info: See attachments.
[root@wallace sa450]# monitor-edid -v probing EDID using VBE (port 0) VBE version: 3.0, oem version = 15.31 Memory: 16384k OEM name: Vendor name: Product name: Product revision: Port 0: DDC1 not supported DDC2 supported Screen not blanked during data transfer Time to transfer one EDID block: 1 sec (rounded up) EDID: Error (0x4f15:01): 0x034f probing EDID using VBE (port 1) Port 1: DDC1 not supported DDC2 supported Screen not blanked during data transfer Time to transfer one EDID block: 1 sec (rounded up) EDID: Error (0x4f15:01): 0x034f probing EDID using VBE (port 2) Port 2: DDC1 not supported DDC2 supported Screen not blanked during data transfer Time to transfer one EDID block: 1 sec (rounded up) EDID: Error (0x4f15:01): 0x034f
Created attachment 946997 [details] Xorg log from SA450 EDID not correctly recognized
Created attachment 947000 [details] Xorg log from 2443BW EDID correctly recognized
Created attachment 947004 [details] Report generated on W7 by Extron EDID Manager W7 recognizes the A450 EDID information. This file is the output of the Extron EDID Manager utility on W7. It shows the raw EDID data dump, and the correctly formatted EDID information. Hopefully it is the new EDID layout that Ajax expected.
EDID looks like a sane format, the question becomes why we're not fetching it correctly. Can you boot with drm.debug=4 on the kernel command line with the broken monitor attached, and attach dmesg from that boot?
Created attachment 948338 [details] dmesg output on Intel box with drm:debug=4
Created attachment 948339 [details] Xorg.0.log for Intel box
Created attachment 948340 [details] Xorg.1.log for Intel box
Adam, Sorry for the delay - real work has been nuts the last two weeks. I'll be at home all day Tuesday Oct 21st (comp time) if you need more info or if you need me to test anything. Thanks again! Al
I'm working from home today and Monday. Saw you were doing LLVM 3.5, hope it is going well.
Remind me, was there a Fedora version where this worked? (Kernel version is sufficient.) If so, can you narrow down when the problem was introduced?
Adam, I got the new monitor because the old one was failing - backlight fading (pre-LED monitor) and some vertical lines. The failure is on current F20, and on F21 Beta TC4. I have live images for F20 and F19 GA releases if you want me to try those. Al
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.