Jul 23 11:40:49 hey folks, I got a rather strange problem since kernel 3.19.0-22+, one of my two displays stays black after boot up. Works in *.0-21. Any idea where I can start looking for the error? Jul 23 11:58:41 * murray2k has quit (Remote host closed the connection) Jul 23 12:31:32 * murray2k (~andreas@dslb-178-005-002-049.178.005.pools.vodafone-ip.de) has joined #ubuntu Jul 23 12:32:03 * murray2k (~andreas@dslb-178-005-002-049.178.005.pools.vodafone-ip.de) has left #ubuntu Jul 23 12:32:15 * murray2k (~andreas@dslb-178-005-002-049.178.005.pools.vodafone-ip.de) has joined #ubuntu Jul 23 12:40:50 * murray2k (~andreas@dslb-178-005-002-049.178.005.pools.vodafone-ip.de) has left #ubuntu Jul 23 12:40:59 * murray2k (~andreas@dslb-178-005-002-049.178.005.pools.vodafone-ip.de) has joined #ubuntu Jul 23 12:44:01 * murray2k has quit (Quit: Leaving.) Jul 23 12:45:14 * murray2k (~andreas@dslb-178-005-002-049.178.005.pools.vodafone-ip.de) has joined #ubuntu Jul 23 12:55:13 Hi folks, I have a strange problem I can not use both of my displays in 1080p since kernel 3.19.0-22. If I set them both to fullhd one turns off. Jul 23 12:56:17 murray2k: does booting from the previous kernel version solve it? Jul 23 12:56:32 yes it does. Jul 23 12:56:53 murray2k: which GPU(s) does the system have; which drivers? Jul 23 13:00:31 TJ-: http://paste.ubuntu.com/11924903/ Jul 23 13:01:40 murray2k: OK, so an ATI/AMD Radeon currently using the open-source driver. Is the PC currently booted with the misbehaving kernel version? Jul 23 13:03:59 TJ-: yes that's correct. Jul 23 13:04:32 murray2k: Can you pastebin "/var/log/dmesg" ? Jul 23 13:07:37 TJ-: sure, here: http://paste.ubuntu.com/11924922/ Jul 23 13:10:05 murray2k: Three ports: 1 x HDMI, 1x DVI-D and 1 x VGA - do all have monitors attached or just the digital outputs? Jul 23 13:11:08 TJ-: just the digital ones. Jul 23 13:11:39 murray2k: OK: can you show "pastebinit <( xrandr -q )" Jul 23 13:12:25 TJ-: http://paste.ubuntu.com/11924936/ Jul 23 13:15:49 murray2k: and is one of those monitors currently blank? Jul 23 13:18:26 TJ-: no, both are working right now. If I set the HDMI-0 to 1920x1080 than this one turns off. Jul 23 13:21:22 murray2k: OK, and the max res is shown as "16384 x 16384" so that shouldn't be the issue; can you "pastebinit /var/log/Xorg.0.log Jul 23 13:23:17 TJ-: http://paste.ubuntu.com/11924974/ Jul 23 13:28:59 murray2k: I'd *suspect* it is because the ACI 22fa has 3 refresh rates for 1920x1080 and the driver is auto-selecting a 'bad' one. Jul 23 13:30:40 murray2k: Try "xrandr --output HDMI-0 --mode "1920x1080@59.9" Jul 23 13:35:51 TJ-: xrandr: cannot find mode 1920x1080@59.9 Jul 23 13:39:11 murray2k: Grrrr, xrandr syntax I think Jul 23 13:40:57 murray2k: Try "xrandr --output HDMI-0 --mode "1920x1080_59.9" Jul 23 13:42:04 TJ-: also not working Jul 23 13:42:06 murray2k: Sorry not it should be "xrandr --output HDMI-0 --mode "1920x1080 --rate 59.9" !! Jul 23 13:45:08 TJ-: yes that works. Jul 23 13:45:37 murray2k: OK ... so you now have 2 working screens? Jul 23 13:47:10 TJ-: that's correct both working with fullhd as resolution. Jul 23 13:47:50 murray2k: I looks as if that ACI screen doesn't like 60Hz refresh, or else the GPU isn't putting out 60Hz when told to. In the current kernel 60Hz is the default so we've forced it to 59.9Hz. You should boot with the older, good, kernel and check the "xrandr -q" report to see if it shows 1920x1080 with 60Hz as the default there too, and check whether it has been selected or is using 59.9. Jul 23 13:51:08 TJ-: OK: I reboot now to check, brb. THX Jul 23 13:51:26 * murray2k has quit (Remote host closed the connection) Jul 23 14:02:12 * murray2k (~andreas@dslb-178-005-002-049.178.005.pools.vodafone-ip.de) has joined #ubuntu Jul 23 14:04:59 TJ-: I booted from the good kernel but here display works with --rate 60.0 Jul 23 14:05:26 murray2k: Right, so it looks like a timing fault in the new kernel; possibly in the radeon driver Jul 23 14:07:04 murray2k: can you report a bug using "ubuntu-bug linux" with a concise description including the good and bad kernel versions, the output of "xrandr -q", and that its using the radeon (not fglxr) driver Jul 23 14:08:12 TJ-: i can do, but can use --rate 60 on the HDMI-0 output, if I decrease the resolution on the second output. Jul 23 14:09:55 murray2k: Yes, it looks like there's a bug in the max clock timing calculations Jul 23 14:11:53 TJ-: OK: I file a bug report. Thanks again. Jul 23 14:17:07 murray2k: I've just looked at the changelog, and there are some drm/radeon changes in -22 .... you should dist-upgrade to the latest 3.19.0-23 because there are a lot of fixes that cover drm including patches for the CRTC Jul 23 14:17:21 murray2k: see http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_3.19.0-23.24/changelog Jul 23 14:21:55 TJ-: yes, I've seen that, but I dist-upgraded today, so I'm already on 3.19.0-23 Jul 23 14:25:49 murray2k: your earlier pastebin showed: "[ 0.000000] Linux version 3.19.0-22-generic (buildd@allspice) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #22-Ubuntu" - I assumed that was the bad kernel Jul 23 14:26:15 murray2k: either way, all those drm/radeon changes will be the cause, and need dealing with Jul 23 14:26:26 murray2k: let me know the bug number once you're reported it Jul 23 14:42:57 murray2k: how you doing with the bug report? I've got one of the kernel devs attention on it Jul 23 14:46:36 TJ-: sorry nearly forgot I'm at work ;), here its https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477587 Jul 23 14:47:11 murray2k: many thanks Jul 23 14:50:19 * murray2k has quit (Remote host closed the connection) Jul 23 14:52:37 * murray2k (~andreas@dslb-178-005-002-049.178.005.pools.vodafone-ip.de) has joined #ubuntu