I updated my driver yesterday to the latest provided by ppa:oibaf/graphics-drivers, and now I'm having having problems with on of the monitors attached to my (r7 260x) card. Snippet from [ 2.761940] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 220 [ 2.761945] Raw EDID: [ 2.761948] 00 ff ff ff ff ff ff 00 1e 6d 3b 58 6a 43 03 00 [ 2.761951] 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00 00 [ 2.761954] 0e 50 54 a5 4b 00 71 4f 81 80 81 8f b3 00 01 01 [ 2.761956] 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00 00 [ 2.761959] 45 00 dd 0c 11 00 00 1e 00 00 00 fd 00 38 4b 1e [ 2.761962] 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00 00 [ 2.761964] 32 34 31 31 0a 20 20 20 20 20 20 20 00 00 00 ff [ 2.761967] 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00 00 [ 2.790928] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 220 If you look in the dmesg log, there is also mention of: *ERROR* atombios stuck in loop for more than 5secs aborting My computer did lock up until I installed the latest mainline kernel, but the error still remains. This may be related to https://bugs.freedesktop.org/show_bug.cgi?id=7317 Full Dmesg: http://paste.ubuntu.com/6706927/ Xorg.0.log: http://paste.ubuntu.com/6706938/ Driver apt-cache policy xserver-xorg-video-radeon xserver-xorg-video-radeon: Installed: 1:7.2.0+git1312250730.04ef03~gd~s Candidate: 1:7.2.0+git1312250730.04ef03~gd~s Version table: *** 1:7.2.0+git1312250730.04ef03~gd~s 0 500 http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status 1:7.2.0-0ubuntu10 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages Kernel: linux-image-3.13.0-999-generic_3.13.0-999.201401060405_amd64
Okay, it can't be the xserver-xorg-video-radeon package, since that wasn't upgraded. The packages that were upgraded on the 4th, one of which is causing this: I've removed the kernel and libc upgrade lines since I'm using the mainline build, and since I don't have an intel card, I've removed that line. libgl1-mesa-dev:amd64 (10.1~git1312310730.5a51c1~gd~s, 10.1~git1401041930.a61ae2~gd~s), libegl1-mesa:amd64 (10.1~git1312310730.5a51c1~gd~s, 10.1~git1401041930.a61ae2~gd~s), libopenvg1-mesa:amd64 (10.1~git1312301930.f425d5~gd~s, 10.1~git1401041930.a61ae2~gd~s), libegl1-mesa-drivers:amd64 (10.1~git1312310730.5a51c1~gd~s, 10.1~git1401041930.a61ae2~gd~s), libg3dvl-mesa:amd64 (10.1~git1312301930.f425d5~gd~s, 10.1~git1401041930.a61ae2~gd~s), libgl1-mesa-dri:amd64 (10.1~git1312310730.5a51c1~gd~s, 10.1~git1401041930.a61ae2~gd~s), libglapi-mesa:amd64 (10.1~git1312310730.5a51c1~gd~s, 10.1~git1401041930.a61ae2~gd~s), libgles2-mesa:amd64 (10.1~git1312310730.5a51c1~gd~s, 10.1~git1401041930.a61ae2~gd~s), libgl1-mesa-glx:amd64 (10.1~git1312310730.5a51c1~gd~s, 10.1~git1401041930.a61ae2~gd~s), libxatracker1:amd64 (10.1~git1312301930.f425d5~gd~s, 10.1~git1401041930.a61ae2~gd~s), libgbm1:amd64 (10.1~git1312301930.f425d5~gd~s, 10.1~git1401041930.a61ae2~gd~s), mesa-common-dev:amd64 (10.1~git1312310730.5a51c1~gd~s, 10.1~git1401041930.a61ae2~gd~s), libtxc-dxtn-s2tc0:amd64 (0~git20121227-1, 0~git20131104-1.1~gd~s), libva1:amd64 (1.1.1-3, 1.2.1-2~gd~s), libopus0:amd64 (1.0.1-0ubuntu2, 1.1-0ubuntu1~gd~s), I guess it's probably mesa. I'll compile mesa @ 5a51c1, and see if that fixes things, if so, I'll do I bisect. Looking at the tree, there's only 4 commits in 5a51c1..a61ae2 so maybe not mesa?
Mesa has nothing to do with monitor detection. It's probably the kernel.
You're right, of course, the mesa update required a newer kernel which may have borked my monitor, or the monitor broke coincidentally, either way, it's the physical monitor that's broken.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.