Inconsistent behaviour of the display in Leap 42.1 (upgraded from 13.2)

jrahman · February 17, 2017, 5:39pm

**<<The same posting was posted under Application forum, then I realized, the issue may be rooted from my upgrade installation, therefore I am posting here…>> **

Recently, I have upgraded my laptop from OpenSuse 13.2 to Leap 42.1.
Inconsistent behaviour is now observed when second display is connected to the laptop (as explained in the table below).
This inconsistency was not there before (on 13.2).

The laptop display chip is: AMD Radeon HD 6470M
The driver is: radeon and in active state

**What I need:
When the second display (monitor) will be connected to the laptop, the task bar panel should still be visible and active on the laptop screen. Being the primary display, laptop screen should not change after connected to the second monitor.

Could you please let me know how to fix this ?
****|Scenario #|Graphics option selected at login|Enabled Display (Single or Multi)|Primary Display Selected|Observation after login|Observation 1: after second Display is connected|Observation 2: after second Display is disconnected|
|—|—|—|—|—|—|—|
|1|Default|Single (only laptop)|Laptop|1. Task bar panel appears after login on the primary display (laptop) screen
2. The primary display (laptop) shows the configured wall paper|1. Previously opened application (e.g. Text editor) on primary display moved to second display, leaving the primary display screen empty|1. Previously moved application (e.g. Text editor) returns back to the primary display (laptop) screen|
|2|Default|Multi (both laptop and external monitor)|Laptop|1. Task bar panel appears after login on the 2nd display (external monitor) screen
2. The laptop screen shows no wall paper, it is dark
3. Application opens on the 2nd display
4. Opened application can be moved to the laptop screen
|N/A|1. The laptop screen’s wall paper appears
2. The task bar panel is not appeared (to get the task bar has to add panel)|
|3|KDE Plasma Workspace|Single (only laptop)|Laptop|1. Task bar panel appears after login on the primary display (laptop) screen
2. The primary display (laptop) shows the configured wall paper|1. Previously opened application (e.g. Text editor) on primary display moved to second display, leaving the primary display screen empty|1. Previously moved application (e.g. Text editor) returns back to the primary display (laptop) screen|
|4|KDE Plasma Workspace|Multi (both laptop and external monitor)|Laptop|1. Task bar panel appears after login on the 2nd display (external monitor) screen
2. Application opens on the 2nd display
3. Opened application can be moved to the laptop screen
|N/A|1. The laptop screen’s wall paper appears
2. The task bar panel is not appeared (to get the task bar has to add panel)|
|5|Plasma 5|Single (only laptop)|Laptop|1. Task bar panel appears after login on the primary display (laptop) screen
2. The primary display (laptop) shows the configured wall paper|1. Previously opened application (e.g. Text editor) on primary display moved to second display, leaving the primary display screen empty|1. Previously moved application (e.g. Text editor) returns back to the primary display (laptop) screen|
|6|Plasma 5|Multi (both laptop and external monitor)|Laptop|1. Task bar panel appears after login on the 2nd display (external monitor) screen
2. The laptop screen shows no wall paper, it is dark
3. Application opens on the 2nd display
4. Opened application can be moved to the laptop screen
|N/A|1. The laptop screen’s wall paper appears
2. The task bar panel is not appeared (to get the task bar has to add panel)|

**

tsu2 · February 17, 2017, 9:00pm

Nowadays,
The video driver is normally a kernel Mode (KMS) but you will need to clarify whether you are doing this, or using a User Mode driver (especially since this is an upgrade from another distro version)

Also,
Multiple Displays are generally always managed by the Desktop, so you need to describe whether you are managing your multiple displays using the Desktop and identify which Desktop you’re using (maybe even the version). I see references to KDE, but don’t know which version you’re running.

You should also describe whether your Desktop and any other related sub-systems are installed from the default openSUSE repo (OSS) or from a special repository for that Desktop.

You may also have to describe exactly what you used as your guide and the methods you used to upgrade from 13.2 > LEAP (Did you use a DVD? or use zypper? Did you use the steps outlined in the SDB:Upgrade at the following URL?)
https://en.opensuse.org/SDB:System_upgrade

Also, it’s not sufficient generally to say that your “driver is Radeon,” you need to identify the exact driver and version and where it’s from.

TSU

jrahman · February 18, 2017, 3:04am

Hi Tsu,
Thanks. Providing as much as possible information below. Hope these would help you to find me a solution.

Nowadays,The video driver is normally a kernel Mode (KMS) but you will need to clarify whether you are doing this, or using a User Mode driver (especially since this is an upgrade from another distro version)

AMDGPU (installed driver information):


i | libdrm_amdgpu1                             | Userspace interface for Kernel DRM services for AMD Radeon chips                      | package    
i | libdrm_amdgpu1-32bit                    | Userspace interface for Kernel DRM services for AMD Radeon chips                      | package

Also,
Multiple Displays are generally always managed by the Desktop, so you need to describe whether you are managing your multiple displays using the Desktop and identify which Desktop you’re using (maybe even the version). I see references to KDE, but don’t know which version you’re running.

KDE version information:


Qt: 5.5.1
KDE Frameworks: 5.21.0
kf5-config: 1.0

You should also describe whether your Desktop and any other related sub-systems are installed from the default openSUSE repo (OSS) or from a special repository for that Desktop.

You may also have to describe exactly what you used as your guide and the methods you used to upgrade from 13.2 > LEAP (Did you use a DVD? or use zypper? Did you use the steps outlined in the SDB:Upgrade at the following URL?)
SDB:System upgrade - openSUSE Wiki

I used zypper and followed the instructions from here (which is very similar to OpenSuse’s upgrade wiki):

The zypper lr -d output (captured just after upgrade):


#  | Alias                         | Name                                    | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                    | Service---+-------------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+------------------------------------------------------------------------+--------
 1 | download.opensuse.org-non-oss | Main Repository (NON-OSS)               | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/      |        
 2 | download.opensuse.org-oss     | Main Repository (OSS)                   | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/leap/42.1/repo/oss/          |        
 3 | graphics                      | Graphics Project (openSUSE_leap/42.1)   | No      | ----      | No      |   99     | rpm-md | http://download.opensuse.org/repositories/graphics/openSUSE_leap/42.1/ |        
 4 | openSUSE-leap/42.1-0          | openSUSE-leap/42.1-0                    | No      | ----      | No      |   99     | yast2  | cd:///?devices=/dev/disk/by-id/ata-hp_CDDVDW_TS-L633R_R82M6GDBA09646   |        
 5 | repo-debug                    | openSUSE-leap/42.1-Debug                | No      | ----      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/42.1/repo/oss/    |        
 6 | repo-debug-update             | openSUSE-leap/42.1-Update-Debug         | No      | ----      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/leap/42.1/                   |        
 7 | repo-debug-update-non-oss     | openSUSE-leap/42.1-Update-Debug-Non-Oss | No      | ----      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/leap/42.1-non-oss/           |        
 8 | repo-source                   | openSUSE-leap/42.1-Source               | No      | ----      | Yes     |   99     | NONE   | http://download.opensuse.org/source/distribution/leap/42.1/repo/oss/   |        
 9 | repo-update                   | openSUSE-42.1-Update                    | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/42.1/oss/                     |        
10 | repo-update-non-oss           | openSUSE-42.1-Update-Non-Oss            | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/42.1/non-oss/                 |

Also, it’s not sufficient generally to say that your “driver is Radeon,” you need to identify the exact driver and version and where it’s from.

AMD Display Controller information (from YAST-HW Info):


34: PCI 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.378]
  Unique ID: VCu0.azklWfz4b+7
  Parent ID: vSkL.zG5hGKNZlz7
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Device Name: "0"
  Model: "Hewlett-Packard Company Radeon HD 6470M"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x6760 "Seymour [Radeon HD 6400M/7400M Series]"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x161a "Radeon HD 6470M"
  Driver: "radeon"
  Driver Modules: "drm"
  Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable)
  Memory Range: 0xd4400000-0xd441ffff (rw,non-prefetchable)
  I/O Ports: 0x4000-0x4fff (rw)
  Memory Range: 0xd4440000-0xd445ffff (ro,non-prefetchable,disabled)
  IRQ: 40 (358243 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00001002d00006760sv0000103Csd0000161Abc03sc00i00"
  Driver Info #0:
    Driver Status: radeon is active
    Driver Activation Cmd: "modprobe radeon"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #21 (PCI bridge)