Bug 477137 - Top screen doesn't display graphics although the cursor travels to it when in MUX mode on a dual-screen laptop.
Summary: Top screen doesn't display graphics although the cursor travels to it when in...
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: master
Platform: Arch Linux Linux
: NOR grave
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-11-17 12:11 UTC by Stavros Aeneas Kokkineas
Modified: 2023-12-09 05:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
drm_info of Mesa Tkg Git and Nvidia Drivers using different kernels (29.99 KB, application/zip)
2023-11-18 09:54 UTC, Stavros Aeneas Kokkineas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stavros Aeneas Kokkineas 2023-11-17 12:11:43 UTC
SUMMARY
Plasma 6 from `kde-unstable` Arch repositories cannot display graphics on the second screen on a dual-screen laptop when dGPU with MUX is enabled.

I have an Asus Zephryus Duo 2023 (7945HX with a MUX switched 4090 and two screens) and , considering this might be a Wayland issue, I have tried using Hyprland and Plasma on it. Both DEs can detect the second (primary - meaning the top screen) screen but Hyprland doesn't really even enable it.

In Plasma 6, both with Nouveau (and NVK) and Nvidia drivers, Plasma fails to display graphics on the top screen. The cursor travels to the top screen but no graphics are displayed (the screen remains black). When trying to manually enable the screen from the Plasma Setting app a single frame is displayed offsetted and nothing else.

When the laptop doesn't use MUX switch (Optimus mode) everything works properly. Currently ubmitting this bug from this laptop with Plasma 6 Wayland on Optimus mode.

Specs:
CPU: AMD Ryzen 9 7945HX
GPU: Nvidia 4090 with MUX switch
RAM: 32 GBs DDR5
SSD: M.2 2TB

STEPS TO REPRODUCE
1. Set the laptop to MUX dGPU mode.
2. Log in to Plasma using SDDM

OBSERVED RESULT
The top screen doesn't display graphics although the cursor travels to it when in MUX mode.

EXPECTED RESULT
The top screen should display graphics even when in MUX mode.

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: Garuda Linux with KDE Plasma
KDE Plasma Version: 6 Alpha
KDE Frameworks Version: 5.245.0
Qt Version: 6.6.0

ADDITIONAL INFORMATION
Comment 1 Zamundaaa 2023-11-17 23:32:34 UTC
Please attach the output of drm_info, once with the mux switch active, and once in optimus mode
Comment 2 Stavros Aeneas Kokkineas 2023-11-18 09:54:12 UTC
Created attachment 163259 [details]
drm_info of Mesa Tkg Git and Nvidia Drivers using different kernels

drm_info on Nvidia failed to produce output for card0 whether using the MUX or Not. linux-next-git failed to boot with mesa-tkg-git.
Comment 3 Stavros Aeneas Kokkineas 2023-11-18 09:54:47 UTC
(In reply to Stavros Aeneas Kokkineas from comment #2)
> Created attachment 163259 [details]
> drm_info of Mesa Tkg Git and Nvidia Drivers using different kernels
> 
> drm_info on Nvidia failed to produce output for card0 whether using the MUX
> or Not. linux-next-git failed to boot with mesa-tkg-git.

I attached the output as requested. Please let me know if you need anything else.
Comment 4 Stavros Aeneas Kokkineas 2023-11-18 09:55:56 UTC
(In reply to Zamundaaa from comment #1)
> Please attach the output of drm_info, once with the mux switch active, and
> once in optimus mode

I attached the output as requested. Please let me know if you need anything else.
Comment 5 Zamundaaa 2023-11-18 18:10:55 UTC
You need to enable modesetting for the proprietary NVidia driver, see https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting
Comment 6 Stavros Aeneas Kokkineas 2023-11-18 18:48:58 UTC
(In reply to Zamundaaa from comment #5)
> You need to enable modesetting for the proprietary NVidia driver, see
> https://wiki.archlinux.org/title/NVIDIA#DRM_kernel_mode_setting

I prefer the Mesa Drivers to be honest. NVK has actually become usable for me. Is there any way to do that with Mesa?
Comment 7 Bug Janitor Service 2023-12-03 03:45:49 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Zamundaaa 2023-12-05 14:20:10 UTC
Sorry for the delay. Your logs for upstream drivers suggest you only get nouveau with Linux Zen + No Mux, and with Linux Zen + Mux you even get simpledrm loaded instead.
So this still looks like a driver issue to me. I don't know the specifics of nouveau but IIRC 4000 series support is still quite new. It might be worth making a bug report to https://gitlab.freedesktop.org/drm/nouveau/-/issues about this
Comment 9 Stavros Aeneas Kokkineas 2023-12-05 14:27:14 UTC
(In reply to Zamundaaa from comment #8)
> Sorry for the delay. Your logs for upstream drivers suggest you only get
> nouveau with Linux Zen + No Mux, and with Linux Zen + Mux you even get
> simpledrm loaded instead.
> So this still looks like a driver issue to me. I don't know the specifics of
> nouveau but IIRC 4000 series support is still quite new. It might be worth
> making a bug report to https://gitlab.freedesktop.org/drm/nouveau/-/issues
> about this

I just made an issue on their tracker, thank you! :)