Bug 61169

Summary: 2nd Monitor No Longer Works after upgrading from F17 to F18
Product: xorg Reporter: earthwormgaz
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg
none
Xorg.log none

Description earthwormgaz 2013-02-20 14:36:29 UTC 
Description of problem:
When I connect my second monitor, the first dies. This set up worked fine on F17, but after upgrading I can't get it to play nice.

The first boot after install, it took me a while to realise the 2nd monitor was killng the first. I disconnected it and hard rebooted, and I was able to use the computer again.

Now, if I plug the 2nd monitor in, and go to Displays, the first monitor goes black, there's no obvious way out of this apart from unplugging the 2nd monitor and hard rebooting.

This is using the DVI and VGA outputs on my AMD motherboard.

Here's lspci in case it helps ...

00:00.0 Host bridge: Advanced Micro Devices [AMD] Family 12h Processor Root Complex
00:01.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Device 9645
00:11.0 SATA controller: Advanced Micro Devices [AMD] FCH SATA Controller [IDE mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices [AMD] FCH USB OHCI Controller (rev 11)
00:12.2 USB controller: Advanced Micro Devices [AMD] FCH USB EHCI Controller (rev 11)
00:13.0 USB controller: Advanced Micro Devices [AMD] FCH USB OHCI Controller (rev 11)
00:13.2 USB controller: Advanced Micro Devices [AMD] FCH USB EHCI Controller (rev 11)
00:14.0 SMBus: Advanced Micro Devices [AMD] FCH SMBus Controller (rev 13)
00:14.1 IDE interface: Advanced Micro Devices [AMD] FCH IDE Controller
00:14.2 Audio device: Advanced Micro Devices [AMD] FCH Azalia Controller (rev 01)
00:14.3 ISA bridge: Advanced Micro Devices [AMD] FCH LPC Bridge (rev 11)
00:14.4 PCI bridge: Advanced Micro Devices [AMD] FCH PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices [AMD] FCH USB OHCI Controller (rev 11)
00:15.0 PCI bridge: Advanced Micro Devices [AMD] Hudson PCI to PCI bridge (PCIE port 0)
00:15.1 PCI bridge: Advanced Micro Devices [AMD] Hudson PCI to PCI bridge (PCIE port 1)
00:16.0 USB controller: Advanced Micro Devices [AMD] FCH USB OHCI Controller (rev 11)
00:16.2 USB controller: Advanced Micro Devices [AMD] FCH USB EHCI Controller (rev 11)
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 0 (rev 43)
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 1
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 2
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 3
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 4
00:18.5 Host bridge: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 6
00:18.6 Host bridge: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 5
00:18.7 Host bridge: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 7
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Comment 1 earthwormgaz 2013-02-20 14:38:33 UTC 
Filed upstream, also here ...

https://bugzilla.redhat.com/show_bug.cgi?id=912728
Comment 2 Alex Deucher 2013-02-20 15:47:13 UTC 
Please attach your xorg log and dmesg output.  Is there any chance you could bisect the kernel?
Comment 3 earthwormgaz 2013-08-28 13:08:15 UTC 
Created attachment 84790 [details]
dmesg
Comment 4 earthwormgaz 2013-08-28 13:08:58 UTC 
Created attachment 84791 [details]
Xorg.log
Comment 5 earthwormgaz 2013-08-28 13:11:09 UTC 
This is still a problem on F19. I just filed another bug on there, that reminded me I'd already raised one, and then I remembered it was on here! Only just saw those questions!

I've attached the logs. I Googled bisecting the kernel and it's probably too late for that. What version did they move to in Fedora 18? The bug must have crept in round there somewhere.
Comment 6 Alex Deucher 2013-08-28 13:40:38 UTC 
(In reply to comment #5)
> I've attached the logs. I Googled bisecting the kernel and it's probably too
> late for that. What version did they move to in Fedora 18? The bug must have
> crept in round there somewhere.

It would really be helpful if you could bisect.  There are a huge amount of changes that go into each kernel release so it's hard to say what change might have caused it.

Can you also attach an Xorg log and dmesg output from the working kernel?
Comment 7 earthwormgaz 2013-08-28 14:16:04 UTC 
How could I do this? Run a Fedora 17 live CD? Surely the old kernels won't run on Fedora 19?
Comment 8 Alex Deucher 2013-08-28 15:09:58 UTC 
If you clone Linus' kernel git tree you can check out older kernels and even bisect ;)
Comment 9 earthwormgaz 2013-08-28 15:12:13 UTC 
Will those built kernels work with Fedora 19 though?

I looked up ..

Fedora 17 was kernel 3.3.4
Fedora 18 was kernel 3.6.10

Does this help?
Comment 10 Martin Peres 2019-11-19 07:40:18 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/60.

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.