[Bug 867499] New: Cannot enable second radeon card, although it is recognized.
https://bugzilla.novell.com/show_bug.cgi?id=867499 https://bugzilla.novell.com/show_bug.cgi?id=867499#c0 Summary: Cannot enable second radeon card, although it is recognized. Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com ReportedBy: strzol@gmail.com QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=581469) --> (http://bugzilla.novell.com/attachment.cgi?id=581469) Xorg log User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Hello to all, I'm trying to achieve a three display setup by the use of two AMD display adapters on my system. Everything works fine with the first adapter and ywo monitors connected but I am unable to start the second adapter and the third monitor on it. I'm using pure autodetection without any manual xorg.conf. My versions are: kernel 3.13.6-1.g4727218-desktop X.Org X Server 1.15.0 OpenGL renderer string: Gallium 0.4 on AMD OLAND OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.1.0 xf86-video-ati 7.3.0 All from opensuse build service repos. xrandr refuses to list the second adapter: xrandr --listproviders Providers: number : 1 Provider 0: id: 0x54 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 3 associated providers: 0 name:radeon The adapters are: lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670/R7 250] 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] I'm attaching my dmesg drm log and my Xorg.0.log where everything seems ok regarding the initialization of both adapters, although Xorg seems to be aware of the second adapter but doesn't using it. Is this implemented or I am asking to much? Thanks for any info. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=867499 https://bugzilla.novell.com/show_bug.cgi?id=867499#c1 --- Comment #1 from Stratos Zolotas <strzol@gmail.com> 2014-03-08 18:51:39 UTC --- Created an attachment (id=581470) --> (http://bugzilla.novell.com/attachment.cgi?id=581470) dmesg drm log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=867499 https://bugzilla.novell.com/show_bug.cgi?id=867499#c Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED AssignedTo|bnc-team-xorg-bugs@forge.pr |xorg-maintainer-bugs@forge. |ovo.novell.com |provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=867499 https://bugzilla.novell.com/show_bug.cgi?id=867499#c2 Tyler Kay <Tyler_Kdog@Yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Tyler_Kdog@Yahoo.com --- Comment #2 from Tyler Kay <Tyler_Kdog@Yahoo.com> 2014-03-12 21:20:12 UTC --- I can largely confirm Stratos' finding. Note: there is a thread regarding this on the openSUSE forums, with relevant discussion beginning here: https://forums.opensuse.org/showthread.php/490418-Help-Configuring-Multiple-... As noted in that thread: - Stratos tested with radeon+radeon, and as can be seen in the Xorg log above, the second radeon adapter is not found. In addition, the "--listproviders" only shows the one adapter. Obviously, one big desktop can not be achieved. - Stratos additionally tried with mixed adapters; radeon+nouveau ... in that case, the Xorg log showed both adapters. Similarly, "--listproviders" indicates the two adapters. However, after issuing a "--setprovideroutputsource", xrandr indicates that the outputs on the second adapter are disconnected, and one big desktop spread across the outputs of the multiple adapters can not be achieved. I then tested this and found that: - with radeon+radeon, openSUSE 13.1 works fine (meaning Xorg log is correct, providers all detected, setting the providers works, xrandr correctly reports all outputs, and one big desktop can be achieved ) - updating the kernel (I went to 3.13.6) and graphics stack results in a regression that was (strangely) unlike Stratos' radeon+radeon case, but precisely like his radeon+nouveau case. My knee-jerk reaction is that Airlie and/or Deucher mucked something up in either the DRMs, libdrm, the server, or the DDXs when they introduced runtime PM ...If I'm not mistaken, Dave added that feature to intel and nouveau (for optimus systems) in 3.12 and Alex did likewise for powerxpress systems in 3.13 (My suspicion is that they did not test this new feature, that is currently supposed to be limited to hybrid laptops, with an ordinary multi-gpu desktop systems). If so, they owe me a beer. Bring back my multi-gpu driven, xrandr configured, desktop! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=867499 https://bugzilla.novell.com/show_bug.cgi?id=867499#c3 --- Comment #3 from Stratos Zolotas <strzol@gmail.com> 2014-03-20 18:04:40 UTC --- I can confirm that reverting to 3.11 kernel and the official stable packages for xorg, Mesa, drivers etc makes everything working as expected. Latest (today's) update from xorg repo, breaks everything. X server is not starting at all due to a glamor exception. I will keep testing as soon as there are new packages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=867499 https://bugzilla.novell.com/show_bug.cgi?id=867499#c4 --- Comment #4 from Stefan Dirsch <sndirsch@suse.com> 2014-03-21 11:47:21 UTC --- (In reply to comment #3)
Latest (today's) update from xorg repo, breaks everything. X server is not starting at all due to a glamor exception.
I will keep testing as soon as there are new packages.
I have current X11:XOrg running on a ATI Radeon "CAICOS" (ChipID = 0x6771) graphics card. Works with EXA and glamor as AccelMethod. Make sure you have glamor packages uninstalled and reinstall xorg-x11-server, since glamor is now part of xorg-server. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=867499 https://bugzilla.novell.com/show_bug.cgi?id=867499#c5 --- Comment #5 from Tyler Kay <Tyler_Kdog@Yahoo.com> 2014-04-02 15:08:19 UTC --- As I noted in the openSUSE forums yesterday, I tested with the latest package updates (kernel 3.14, X, etc ) and proper functionality has been restored (i.e. you can once again achieve a large contiguous desktop using a non-PX radeon + radeon system). As I applied the updates en masse, I certainly could not pinpoint what resolved the issue. A glance at the server's change log revealed nothing related to randr (though, in relation to commentary in this thread, I do note that the in server glamor changes, discussed just above, are indeed documented). At that point, I suspected that it was probably a change to the kernel driver, and was going to leave it at that. However, curiosity got the better of me, and, upon checking the drm updates applied to kernel 3.14, we do indeed find this: http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.14&id=7848865914c6a63ead674f0f5604b77df7d3874f Which looks strongly to me to be the winner/solution/explanation. Users of other adapters (ex. nouveau, intel) should check to see if similar runtime PM logic has been adopted in the respective DRM/kernel driver. Alex no longer owes me a beer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com