Bug 346925 - Switching from Xorg to fglrx-updates and back loses 1 monitor
Summary: Switching from Xorg to fglrx-updates and back loses 1 monitor
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.2.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-29 22:50 UTC by androclus
Modified: 2015-05-01 03:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of driver manager dialog box (64.12 KB, image/jpeg)
2015-04-29 22:50 UTC, androclus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description androclus 2015-04-29 22:50:46 UTC
Created attachment 92333 [details]
screenshot of driver manager dialog box

hi, i just updated to Kubuntu 15.04.

in System Settings -> Driver Manager:

at first, i used the X.org Xserver -- AMD/ATI display driver wrapper from xserver-xorg-video-ati (Recommended), and it recognized both my monitors.

but I thought I would try the "Video driver for the AMD graphics accelerators from fglrx-updates", for faster performance, so I switched to this.

however (separate issue), those drivers seem to have problems (even without compositor turned on) with Chromium (really messed up screen drawing on Chromium browser), so I decided to switch back to the X.org Xserver AMD/ATI display driver.

however, when I switched back from fglrx to X.org driver, now I have lost one of my two monitors. The X.org driver now seems to see only 1 monitor.

this is interesting because when I first upgraded to 15.04, and was on the X.org driver, it did see both monitors.  It was only in switching to fglrx and back to X.org driver that I lost the 2nd (dell) monitor.

I have tried switching out and back to X.org again, to no avail.  The fglrx drivers DO see and use the 2nd monitor, but the X.org wrapper driver no longer does.

My computer is a Dell 990
Processor: 4 x Intel Core i5-2400 CPU @ 3.10GHz
Memory: 3.8GiB RAM
Kubuntu 15.04
KDE Plasma Version: 5.2.2
Qt Version 5.4.1
Kernel Version: 3.19.0-15-generic
OS Type: 64-bit

"lspci -v" output on the graphics controller:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller])
        Subsystem: Dell Radeon HD 6350
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at e1520000 (64-bit, non-prefetchable) [size=128K]
        I/O ports at 3000 [size=256]
        Expansion ROM at e1500000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: fglrx_pci

The two displays/monitors:
ASUS VW266 25.5" (1920x1200) (the one that is always on)
Dell P2213t 22" (1680x1050) (the one that only flgrx sees)
both connected to graphics adapter via a dual DVI cable


Please let me know if there is anything I can add to this report. (I'm sure I've left out some vital info..)

Thanks..

-JS
Comment 1 Thomas Lübking 2015-04-29 22:59:36 UTC
This is the bugtracker for the KDE Window manager - the radeon driver is tracked at bugs.freedesktop.org, xorg-driver-ati group.

I'd check the output of "xrandr -r" on whether there's actually no comment on that monitor at all and (if not) try to connect the monitor to another output (twist them?)
Comment 2 androclus 2015-04-29 23:07:34 UTC
okay, thanks, thomas. i'll try over at freedesktop.org -- but somehow i don't think it's actually a driver issue, but a configuration issue, since..

A) it DID originally work for X.org driver when I first upgraded

B) it was only in switching to fglrx drivers and back to X.org driver (i.e., a configuration switch) that the monitor was lost

C) both monitors work FINE under fglrx driver.

=======================================================================
$ sudo xrandr --screen 0
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1600 x 1200, current 1600 x 1200, maximum 1600 x 1200
default connected primary 1600x1200+0+0 0mm x 0mm
   1600x1200      77.0* 
$ sudo xrandr --screen 1
Invalid screen number 1 (display has 1)
$ _
=======================================================================
Comment 3 Thomas Lübking 2015-04-29 23:12:45 UTC
sorry, typo "xrandr -q", and NOT via sudo.

Checking this will indicate whether it's a config (just enable it) or a driver issue.
You can also configure screens graphically via "kcmshell5 kscreen" and in xorg.conf[.d snippets]

Either way: kwin doesn't manage screens.
If somehow kscreen setups fail or do not stick, we'll redirect the bug to kscreen.
Comment 4 androclus 2015-04-29 23:22:05 UTC
thanks again, thomas. i know you've already marked this bug resolved/invalid, i'm just posting this as follow-up in case the information is in any way helpful to future Googlers arriving here..

i did try switching the 2 DVI cables coming out of the graphics adapter. (still using X.org driver)

the result is now that the system sees both monitors, BUT

a) the two displays are showing duplicate desktops, NOT an extended desktop, and

b) it seems now that it thinks that the Dell (the smaller monitor) is now what it is talking to

=======================================================================
$ xrandr -q
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050
default connected primary 1400x1050+0+0 0mm x 0mm
   1400x1050      77.0* 
$ _
=======================================================================

whereas before, it saw the larger (ASUS) screen.

"kcmshell5 kscreen" sees only 1 display (when using X.org driver), and 2 (when using fglrx driver).

i have a hunch that what happens is that when using Driver Manager, switching back to X.org driver somehow forgets Screen 1, keeping only Screen 0, in the xorg.conf file, and so the driver doesn't even look for a second driver.

if this theory were correct, would i still post this bug at freedesktop.org?  Or would it be a Driver Manager bug?

thanks
Comment 5 androclus 2015-04-29 23:24:23 UTC
> and so the driver doesn't even look for a second driver.

sorry, i meant,

and so the driver doesn't even look for a second Screen/display.
Comment 6 androclus 2015-04-29 23:48:02 UTC
per thomas' suggestion, i have posted a bug at 

https://bugs.freedesktop.org/show_bug.cgi?id=90246
Comment 7 Thomas Lübking 2015-04-30 10:13:46 UTC
what might have happened is that fglrx wrote an Xorg config that manipulates screens or crtcs and that only fglrx can "fix" at runtime.

Check /etc/X11/xorg.conf[.d/] contents on whether you find injections or backups by fglrx.
Since the entire thing should work configless, you may also want to try to move all those configs away (sudo mkdir /etc/X11.bak; sudo mv /etc/X11/* /etc/X11.bak) to check whether the problem seems to source from there.
Comment 8 androclus 2015-05-01 03:22:49 UTC
Thanks, Thomas. I did get an immediate repair solution at the freedesktop bug I posted in Comment 6.

Since this appears to be a kubuntu-river-manager package bug, I have gone on and posted another bug at Launchpad, at

https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1450694
Comment 9 androclus 2015-05-01 03:23:42 UTC
sorry, i mean kubuntu-driver-manager