Bug 484910 - DP DaisyChain Second Monitor detected but not possible to enable
Summary: DP DaisyChain Second Monitor detected but not possible to enable
Status: RESOLVED UPSTREAM
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 6.0.3
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-02 08:51 UTC by Frieder
Modified: 2024-04-10 08:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frieder 2024-04-02 08:51:56 UTC
SUMMARY

STEPS TO REPRODUCE
1. Connect 2 External Displays to Laptop via DP Daisy Chain
2. Check settings to see that one is disabled
3. Enable on the settings page and press apply 

OBSERVED RESULT

Screen doesn't turn on and seems to revert back to the original state where the screen is disabled.

EXPECTED RESULT

Second Screen turns on.

---

*Note:* I've also tried to enable the screen via `kscreen-doctor output.DP-12.enable`
with the following output:

```
kscreen-doctor output.DP-12.enable
Enabling output 3
kscreen.doctor: setop exec returned KScreen::Config( 
KScreen::Output(1, "eDP-2", connected enabled priority 2, pos: QPoint(2560,263), res: QSize(2560, 1600), modeId: "0", scale: 1.75, clone: no, rotation: KScreen::Output::None, followPreferredMode: false) 
KScreen::Output(2, "DP-10", connected enabled priority 1, pos: QPoint(0,0), res: QSize(3840, 2160), modeId: "0", scale: 1.5, clone: no, rotation: KScreen::Output::None, followPreferredMode: false) 
KScreen::Output(3, "DP-12", connected enabled priority 3, pos: QPoint(6400,0), res: QSize(3840, 2160), modeId: "0", scale: 1.25, clone: no, rotation: KScreen::Output::None, followPreferredMode: false) )
```

SOFTWARE/OS VERSIONS
Windows:  11
Linux/KDE Plasma:  6.7.10-2-MANJARO
KDE Plasma Version:  6.0.2
KDE Frameworks Version:  6.0.0
Qt Version:  6.6.2

ADDITIONAL INFORMATION

Output of  `kscreen-doctor -o`
```
Output: 1 eDP-2
        enabled
        connected
        priority 2
        Panel
        Modes:  0:2560x1600@120*!  1:2560x1600@96  2:2560x1600@72  3:2560x1600@60  4:2560x1600@60  5:2560x1600@50  6:2560x1600@48  7:1920x1200@120  8:1920x1080@120  9:1600x1200@120  10:1680x1050@120  11:1280x1024@120  12:1440x900@120  13:1280x800@120  14:1280x720@120  15:1024x768@120  16:800x600@120  17:640x480@120  18:1600x1200@60  19:1280x1024@60  20:1024x768@60  21:2560x1600@60  22:1920x1200@60  23:1280x800@60  24:2560x1440@60  25:1920x1080@60  26:1600x900@60  27:1368x768@60  28:1280x720@60 
        Geometry: 2560,263 1463x915
        Scale: 1.75
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: unknown
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
Output: 2 DP-10
        enabled
        connected
        priority 1
        DisplayPort
        Modes:  0:3840x2160@60*!  1:3840x2160@60  2:3840x2160@60  3:3840x2160@50  4:3840x2160@30  5:3840x2160@30  6:3840x2160@30  7:3840x2160@25  8:3840x2160@24  9:3840x2160@24  10:2560x1440@60  11:1920x1080@60  12:1920x1080@60  13:1920x1080@60  14:1920x1080@50  15:1920x1080@30  16:1920x1080@30  17:1920x1080@25  18:1920x1080@24  19:1920x1080@24  20:1600x1200@60  21:1680x1050@60  22:1600x900@60  23:1280x1024@75  24:1280x1024@60  25:1280x800@60  26:1152x864@75  27:1280x720@60  28:1280x720@60  29:1280x720@60  30:1280x720@50  31:1024x768@75  32:1024x768@60  33:1440x480@60  34:1440x480@60  35:832x624@75  36:800x600@75  37:800x600@60  38:720x576@50  39:720x480@60  40:720x480@60  41:720x480@60  42:720x480@60  43:640x480@75  44:640x480@60  45:640x480@60  46:640x480@60  47:720x400@70  48:1600x1200@60  49:1280x1024@60  50:1024x768@60  51:2560x1600@60  52:1920x1200@60  53:3840x2160@60  54:3200x1800@60  55:2880x1620@60  56:2560x1440@60  57:1920x1080@60  58:1600x900@60  59:1368x768@60  60:1280x720@60 
        Geometry: 0,0 2560x1440
        Scale: 1.5
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: unknown
        HDR: disabled
        Wide Color Gamut: incapable
        ICC profile: none
Output: 3 DP-12
        disabled
        connected
        priority 0
        DisplayPort
        Modes:  0:3840x2160@60*!  1:3840x2160@60  2:3840x2160@60  3:3840x2160@50  4:3840x2160@30  5:3840x2160@30  6:3840x2160@30  7:3840x2160@25  8:3840x2160@24  9:3840x2160@24  10:2560x1440@60  11:1920x1080@60  12:1920x1080@60  13:1920x1080@60  14:1920x1080@50  15:1920x1080@30  16:1920x1080@30  17:1920x1080@25  18:1920x1080@24  19:1920x1080@24  20:1600x1200@60  21:1680x1050@60  22:1600x900@60  23:1280x1024@75  24:1280x1024@60  25:1280x800@60  26:1152x864@75  27:1280x720@60  28:1280x720@60  29:1280x720@60  30:1280x720@50  31:1024x768@75  32:1024x768@60  33:1440x480@60  34:1440x480@60  35:832x624@75  36:800x600@75  37:800x600@60  38:720x576@50  39:720x480@60  40:720x480@60  41:720x480@60  42:720x480@60  43:640x480@75  44:640x480@60  45:640x480@60  46:640x480@60  47:720x400@70  48:1600x1200@60  49:1280x1024@60  50:1024x768@60  51:2560x1600@60  52:1920x1200@60  53:3840x2160@60  54:3200x1800@60  55:2880x1620@60  56:2560x1440@60  57:1920x1080@60  58:1600x900@60  59:1368x768@60  60:1280x720@60 
        Geometry: 6400,0 3072x1728
        Scale: 1.25
        Rotation: 1
        Overscan: 0
        Vrr: incapable
        RgbRange: unknown
        HDR: disabled
        Wide Color Gamut: incapable
        ICC profile: none
```
Comment 1 Frieder 2024-04-04 20:18:18 UTC
Just updated to the latest 6.0.3
Comment 2 Zamundaaa 2024-04-05 14:53:45 UTC
Is this on Wayland or Xorg?
Comment 3 Frieder 2024-04-08 07:26:01 UTC
This is on wayland but I've also just tried it on X11 and the issue is the same.

Just to be sure that it works I've tried it with a Windows PC  and there the setup works so the cables and monitor settings should be fine.
Comment 4 Zamundaaa 2024-04-08 11:29:21 UTC
Okay, then this will be a driver bug. What GPU does your laptop have?
Comment 5 Frieder 2024-04-08 20:55:54 UTC
TLDR:
- 6700S or 6800S
- AMD Ryzen 9 6900HS

----

> inxi -Fxz
gives me the following (I've removed some parts that are obviously unnecessary...)

CPU:
  Info: 8-core model: AMD Ryzen 9 6900HS with Radeon Graphics
Graphics:
  Device-1: AMD Navi 23 [Radeon RX 6650 XT / 6700S 6800S] vendor: ASUSTeK
    driver: amdgpu v: kernel arch: RDNA-2 bus-ID: 03:00.0
  Device-2: AMD Rembrandt [Radeon 680M] vendor: ASUSTeK driver: amdgpu
    v: kernel arch: RDNA-2 bus-ID: 07:00.0 temp: 52.0 C
  Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 23.2.5
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu,amdgpu
    resolution: 1707x1067
  API: EGL v: 1.5 drivers: radeonsi,swrast platforms:
    active: wayland,x11,surfaceless,device inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.4-manjaro1.2
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
    rembrandt LLVM 17.0.6 DRM 3.57 6.8.4-1-MANJARO)
Comment 6 Frieder 2024-04-09 06:54:59 UTC
Would you know any logs that I can have a look at to see what's going wrong?
Then I could go and create an issue somewhere else I guess :D
Comment 7 Zamundaaa 2024-04-09 14:03:40 UTC
https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues describes how to get detailed logs about what the kernel is doing with displays.

You can capture the dmesg output with that debugging enabled, and open an issue at https://gitlab.freedesktop.org/drm/amd/-/issues about it
Comment 8 Frieder 2024-04-10 08:59:53 UTC
The story continues here: https://gitlab.freedesktop.org/drm/amd/-/issues/3319