KDE/4k/Nvidia - Very concerned about F40 - Wayland is unusable for me

Project Discussion
1

Hi all,

I know this comes up a lot but just wondered what others felt about this.

I cannot use Wayland ever since moving to Fedora 39. It logs the session into a black screen for me. This is after several driver and kernel versions. KDE is really the desktop that I use and want to continue with but concerned that F40 will not be feasible. Does anyone know for sure if I can keep the X11 session after the upgrade or if anyone is having a good experience with a similar set up to mine?

I have been very impressed with the desktop experience with 4k and X11 the scaling (200%) works perfectly and everything looks consistent. When I was able to log into wayland (occasionally), the scaling was all over the place.

Just curious how others with 4k/KDE/Nvidia are getting on.

Thanks!

2

Try wiping your user cache ~/.cache and reset to the default breeze theme (including windows decorations and cursor). There are some issues on Plasma 5, but plasma 6 should be much better.

But yes you can keep X11 but itā€™s not really supported.

3

Yes, you can. A member of the community was concerned about X11 support
being dropped from KDE and came up with a solution.

Not all the pieces needed are in place and enabled yet, but the required
packages should be available already.

See this mailing list
post
for the plan and try to ignore all the noise around it. The Copr repo
isnā€™t there yet, but if you are going to upgrade before it is, you can
simply (re-)install plasma-workspace-x11 package post upgrade.

1 Like
4

Thanks all for the replies. I will be cautiously optimistic for F40.

5

Iā€™m using Fedora Workstation right now, but on my other computer I run Arch with KDE 6 on Wayland on a 4K Screen with my NVIDIA GPU and have since it came out. It works quite well, but XWayland applications (such as Steam, Krita, etc.) flicker a lot: Immense store flicker on Nvidia Wayland Ā· Issue #10313 Ā· ValveSoftware/steam-for-linux Ā· GitHub

This issue is due to lack of Explicit Sync support, but that protocol was merged last month, and NVIDIAā€™s 555 proprietary driver will have support for it. The stable version of that driver will be out within the next 2 months.

XWayland applications can be scaled by KWin, but theyā€™re likely to be blurry. What I do in KDE is turn off scaling for XWayland applications and let them scale themselves, if they can. It works well for Steam, though Krita canā€™t scale itself in quite the right way.

Wayland doesnā€™t have any color management either and calibration tools like DisplayCAL canā€™t calibrate the screen.

Those are the remaining issues for me. This page lists some significant issues with Plasmaā€™s Wayland session.

6

Upgraded to F39 in last 2 weeks.
I generally use KDE. Only root uses gnome.

System details:
Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.8.8-200.fc39.x86_64 (64-bit)
Graphics Platform: X11
Processors: 32 Ɨ IntelĀ® XeonĀ® CPU E5-2650 v2 @ 2.60GHz
Memory: 94.3 GiB of RAM
Graphics Processor: NVIDIA TITAN Xp/PCIe/SSE2
Manufacturer: Intel Corporation
Product Name: W2600CR
System Version: ā€¦

Tried very briefly today my new upgrade with Wayland login. In the past it was useless.

Result: Poor image quality, some of my task bar apps when clicked on would only open one window and not second instance, task bar not really fully functional etc.

As a result switched back to X11.

Then a quick review of Wayland status highlights continuing issues, i.e.

I have other software to develop and test and have no time to explore wayland further. Suffice to say that I am neutral. All I want is something that works and as per article wayland and KDE are still only in courtship from what I can tell. There not even engaged yet, let alone married.

I note F40 is now available. I deliberately lag behind based on past experience. I donā€™t have the time to be right at the bleeding edge of releases and deal with the issues that pop up very occasionally that sometimes force a downgrade while I wait for them to be addressed. The worst being video issue where system wonā€™t even boot leaving me high and dry as happened once with F38 where I helped in the debug cycle.

I also concur with the above article re the software development trends of 50% is good enough and then fix the issues. I accept that (kind off if I am interested in that software function) for opensource. But this trend is also now occuring in commercial software or even websites.

As the above article states:

A tool that doesnā€™t do what itā€™s supposed to do is a broken tool. A useless tool.

Especially so with display cause if it donā€™t display on a desktop properly your kind of blind or need corrective glasses at best. I am old school of the minimum 80% is good enough variety.

From that test on F39, Wayland is not yet ready with KDE. Maybe it is with Gnome but I hate Gnome.

So in my limited view - Wayland is not yet ready for default if I login and have issues immediately.

Would you like a Tesla that only half works?

Kindly now awaiting the flames.

7

All Iā€™ll say is Plasma 6 and Plasma 5 are worlds apart in terms of Wayland support. Itā€™s certainly not perfect now, but lots of bugs (some I reported) have been fixed in the wake of the Qt6 transition and thatā€™s where the focus is now. Thatā€™s why Plasma felt comfortable enough making it the default from then on.

The Wayland session is missing certain features, some core to certain peopleā€™s workflows. Iā€™m surprised you didnā€™t mention flickering given your NVIDIA GPU, but maybe you didnā€™t have the chance to test out some XWayland programs in-depth. That particular issue will certainly be fixed by the time Fedora 41 is out.

It makes a lot of sense to stay on Fedora 39 for the full support period and wait another 6 months for Fedora 41 with 6.1 (or maybe 6.2? Iā€™m not familiar with Fedoraā€™s release cycles, but 6.2 should be out by October). Iā€™m hopeful the color management protocol will be out and implemented in KWin by then.

In the meantime, perhaps it would be prudent to report some bugs? :slight_smile:

Edit: Oh, and the KDE SIG + another KDE contributor are maintaining the X11 session packages for the foreseeable future, so you could jump to Fedora 40 anyway and just add those packages.

1 Like
8

Thanks for the usefull background on KDE & wayland status.

Conclusions: hang onto F39 as long as possible and then maybe jump to F41 and pray my graphics card is still suitable for wayland.

9

Hi all, OP of this thread here. I did upgrade to F40 but still found that Wayland was a suboptimal experience for me with my use case and software. I installed the X11 session for KDE 6 and am successfully running that. So I would say you donā€™t need to avoid F40 if you donā€™t want to but keep in mind that you may need to run the X11 session. Not sure how long that will be maintained for?

10

Explicit sync support was the last major blocker for NVIDIA as far as I know (caused a bunch of flickering issues), and NVIDIA will have a driver out next month with support for it. The question is when the corresponding support in KWin/GNOMEā€™s Mutter will land in Fedora (definitely in 41 if not 40). Even the proprietary NVIDIA driver should provide a good experience on Wayland very soon.

Itā€™s all the other problems with Wayland youā€™ll need to worry about. As far as I know, those are mostly just missing features at this point (certainly in my case) rather than bugsā€¦

So I would say you donā€™t need to avoid F40 if you donā€™t want to but keep in mind that you may need to run the X11 session. Not sure how long that will be maintained for?

It depends on whether youā€™re using the COPR by the KDE SIG or the packages by Kevin Kofler. As far as I know, Kevin Kofler intends to keep them alive as long as he can. Some more context: KDE Plasma X11 support gets a reprieve for Fedora 40 [LWN.net]

11

Updated with dnf update 11 Oct. 2024 from july 2024. Delayed deliberately due to other priority tasks for which I did not want an unable system in case of a bad update.

I am documenting my experience here for others reference.

System details:
Fedora 39
kernel: 6.10.12-100.fc39.x86_64
rpmfusion Nvidia drivers 560.35.03

Initially had same problem of unable to see or configure a second monitor as per start of this post.

After a bit of research found:
https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/

with prime reference:
https://www.nvidia.com/en-us/drivers/details/230929/

explained furter re dkms:
https://wiki.archlinux.org/title/Kernel_mode_setting

i.e.: For Fedora 40/39/38 and Nvidia 560.xx/550.xx/535.xx/470.xx with wayland enabled do

2.6.2 Edit /etc/default/grub Append 'rd.driver.blacklist=nouveau' and ' nvidia-drm.fbdev=1' (and 'nvidia-drm.modeset=1') to the end of GRUB_CMDLINE_LINUX="..."'.

Do not add these grub kernel boot CMDLINE with X11 enabled.

Note: This won't work with kernel 6.9.x and KDE Plasma 6 / SDDM, use wayland only

So

$ cat /proc/cmdline BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.10.12-100.fc39.x86_64 root=/dev/mapper/VG01_nvme_pcie-rootfs ro rd.lv m.lv=VG01_nvme_pcie/rootfs rd.luks.uuid=luks-160cee22-ab53-47b2-a48a-382fca72928a rhgb rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia_drm.modeset=1 nvidia_drm.fbdev=1

This did not work initially. Powered down. Unplugged second monitor, plugged back in.

Still no difference. So unplugged 2nd monitor while powered while logged in gnome and vioā€™la 2nd monitor detected by gnome setting - display.

Logged out then logged in via Plasma. Same again and had to unplug 2nd monitor and plug it in while powered and logged in in Plasma.

Now functional with joint 2nd monitor.

So in conclusion Wayland, Nvidia, Plasma are in a flakky transition state as these overdue Linux and desktop graphics update frm X11 to wayland works itā€™s way through numerous developers hands. At least getting there. I do not strange plasma things like the clock in the task bar gets stuck after about an hour or so from login at a fixed time, some windows when minimised canā€™t be maximised. So numerous quirks. I guess we should expect that during this transition away from X11. Given these which I expect to find more of, I still think certainly re F39 pre kernel 6.9 to stick with X11. No comment on F40 but from above discussion F40 is definitely a transitional release for workstations with Nvidia cards. Depending how I go now with F39 under wayland Iā€™ll still hangback for F41 before next upgrade.

I still need to fully get my head wrapped around the Archlinux description re kernel modesetting for Nvidia to work with Wayland. What is clear this is very much a multiyear work in progress to get nvidia working with Wayland. I hope itā€™s worth it in the end cause X11 did work fine though Understand the ā€˜datedā€™ arguments against it.

12

Oā€™dear ā€¦ spoke too soon ā€¦ :angry:

Reboot and guess what ā€¦ 2nd monitor does not work - blank.

But guess what, unplug and plug back in on the graphics card does the trick while logged in!

OK Help anyoneā€¦? Might have to try F40 after all since I also note niggles with Plasma 5.

Am using Nvidia Titan Xp on rpmfusions Nvidia 560.35.03

13

This is old ā€œbugā€ i call it ā€œfeatureā€ most times when it looses external screen just disconnect and connect back and all is good again

Tho never had this on KDE always on Gnome and currently driving KDE and Kinoite months and no issues yet

Do you run Gnome as base and installed KDE as second DE?

14

Sorry struggling understanding your grammar.

I think the answer your looking for:

  1. Installed first as F36 with subsequent upgrades over the years,
  2. Installed F36 as base gnome and then installed plasma/kde so ā€˜second DEā€™.
  3. My userā€™s use plasma and admin root uses gnome due to base install

Gnome suffers same issue, i.e. after reboot need to unplug and plug back in second Dp-4 monitor, a Samsubg using DVI via hdmi transition into GPU.

This issue of unplug plug in to ā€˜detectā€™ 2nd monitor only occurs with wayland not under X11 login selection. It also never occured before recent upgrade using Nvidia driver 560.35.03

Nvidia bug?

15

Might be nvida or the hdmi dvi adapter

I remeber i had before hdmi and switched to fully DP and havent got any this anymore after switching to only DP

16

Sorry Error - DVI to DP adapter not HDMI

However my prime monitor to DP. So you made me wonderā€¦?

Have another monitor with DP output Iā€™ll try. I do remember somewhere that Nvidia in drivers had a bug something re DVI re multihead.

17

For completness add system details as follows:

$ cat /etc/os-release
NAME="Fedora Linux"
VERSION="39 (Workstation Edition)"
ID=fedora
VERSION_ID=39
VERSION_CODENAME=""
PLATFORM_ID="platform:f39"
PRETTY_NAME="Fedora Linux 39 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:39"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f39/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=39
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=39
SUPPORT_END=2024-11-12
VARIANT="Workstation Edition"
VARIANT_ID=workstation

$ kinfo
Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.116.0
Qt Version: 5.15.14
Kernel Version: 6.10.12-100.fc39.x86_64 (64-bit)
Graphics Platform: offscreen
Processors: 32 Ɨ IntelĀ® XeonĀ® CPU E5-2650 v2 @ 2.60GHz
Memory: 94.3 GiB of RAM
Graphics Processor: NVIDIA TITAN Xp/PCIe/SSE2


$ lspci -k | grep -A 2 -E '(3D|VGA)'
05:00.0 VGA compatible controller: NVIDIA Corporation GP102 [TITAN Xp] (rev a1)
        Subsystem: NVIDIA Corporation Device 11df
        Kernel driver in use: nvidia


$ lspci -k | grep nvidia
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia


        $  nvidia-smi
Sun Oct 13 10:56:13 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 560.35.03              Driver Version: 560.35.03      CUDA Version: 12.6     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA TITAN Xp                Off |   00000000:05:00.0  On |                  N/A |
| 23%   25C    P8             13W /  250W |    1469MiB /  12288MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A      4559      G   /usr/bin/kwin_wayland                         211MiB |
|    0   N/A  N/A      4687      G   /usr/bin/Xwayland                              15MiB |
|    0   N/A  N/A      4708      G   /usr/bin/ksmserver                              3MiB |
|    0   N/A  N/A      4710      G   /usr/bin/kded5                                  3MiB |
|    0   N/A  N/A      4746      G   /usr/bin/plasmashell                          192MiB |
|    0   N/A  N/A      4800      G   ...5/polkit-kde-authentication-agent-1          3MiB |
|    0   N/A  N/A      4802      G   /usr/libexec/xdg-desktop-portal-kde             3MiB |
|    0   N/A  N/A      5066      G   /usr/bin/kwalletd5                              3MiB |
|    0   N/A  N/A      5128      G   /usr/libexec/kdeconnectd                        3MiB |
|    0   N/A  N/A      5272      G   /usr/bin/xwaylandvideobridge                    3MiB |
|    0   N/A  N/A      5310      G   /usr/bin/kaccess                                3MiB |
|    0   N/A  N/A      5321      G   /usr/libexec/DiscoverNotifier                   3MiB |
|    0   N/A  N/A      5322      G   /usr/bin/kalendarac                             3MiB |
|    0   N/A  N/A      5327      G   /usr/lib64/thunderbird/thunderbird            158MiB |
|    0   N/A  N/A      5506      G   /usr/bin/akonadi_control                        3MiB |
|    0   N/A  N/A      5722      G   /usr/bin/akonadi_akonotes_resource              3MiB |
|    0   N/A  N/A      5723      G   /usr/bin/akonadi_archivemail_agent              3MiB |
|    0   N/A  N/A      5724      G   /usr/bin/akonadi_birthdays_resource             3MiB |
|    0   N/A  N/A      5725      G   /usr/bin/akonadi_contacts_resource              3MiB |
|    0   N/A  N/A      5726      G   .../bin/akonadi_followupreminder_agent          3MiB |
|    0   N/A  N/A      5727      G   /usr/bin/akonadi_ical_resource                  3MiB |
|    0   N/A  N/A      5728      G   /usr/bin/akonadi_indexing_agent                 3MiB |
|    0   N/A  N/A      5729      G   /usr/bin/akonadi_maildir_resource               3MiB |
|    0   N/A  N/A      5730      G   /usr/bin/akonadi_maildispatcher_agent           3MiB |
|    0   N/A  N/A      5731      G   /usr/bin/akonadi_mailfilter_agent               3MiB |
|    0   N/A  N/A      5732      G   /usr/bin/akonadi_mailmerge_agent                3MiB |
|    0   N/A  N/A      5733      G   /usr/bin/akonadi_migration_agent                3MiB |
|    0   N/A  N/A      5734      G   /usr/bin/akonadi_newmailnotifier_agent          3MiB |
|    0   N/A  N/A      5735      G   /usr/bin/akonadi_sendlater_agent                3MiB |
|    0   N/A  N/A      5736      G   /usr/bin/akonadi_unifiedmailbox_agent           3MiB |
|    0   N/A  N/A      6113      G   /usr/lib64/firefox/firefox                    613MiB |
|    0   N/A  N/A      6433      G   ...bin/plasma-browser-integration-host          3MiB |
|    0   N/A  N/A      7047      G   /usr/libexec/kf5/klauncher                      3MiB |
|    0   N/A  N/A      7055      G   /usr/bin/kwalletmanager5                        3MiB |
|    0   N/A  N/A     14327      G   /usr/bin/konsole                                3MiB |
|    0   N/A  N/A    100188      G   /usr/libexec/baloorunner                        3MiB |
|    0   N/A  N/A    100211      G   /usr/bin/kwrite                                 3MiB |
+-----------------------------------------------------------------------------------------+

$  cat /proc/cmdline
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.10.12-100.fc39.x86_64 root=/dev/mapper/VG01_nvme_pcie-rootfs ro rd.lvm.lv=VG01_nvme_pcie/rootfs rd.luks.uuid=luks-160cee22-ab53-47b2-a48a-382fca72928a rhgb rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 nvidia-drm.fbdev=1

$ cat /etc/modprobe.d/nvidia.conf
cat: /etc/modprobe.d/nvidia.conf: No such file or directory

$ sudo ls -l  /etc/X11/xorg.conf.d
total 4
-rw-r--r--. 1 root root 311 Jul 12  2022 00-keyboard.conf

$ mokutil --sb-state
SecureBoot disabled
Platform is in Setup Mode

$ sudo dnf list installed \*nvidia\*
Installed Packages
akmod-nvidia.x86_64                                   3:560.35.03-1.fc39            @rpmfusion-nonfree-updates
kmod-nvidia-6.10.12-100.fc39.x86_64.x86_64            3:560.35.03-1.fc39            @@commandline
kmod-nvidia-6.8.10-200.fc39.x86_64.x86_64             3:550.90.07-1.fc39            @@commandline
kmod-nvidia-6.8.11-200.fc39.x86_64.x86_64             3:550.90.07-1.fc39            @@commandline
kmod-nvidia-6.8.9-200.fc39.x86_64.x86_64              3:550.90.07-1.fc39            @@commandline
kmod-nvidia-6.9.4-100.fc39.x86_64.x86_64              3:550.90.07-1.fc39            @@commandline
kmod-nvidia-6.9.5-100.fc39.x86_64.x86_64              3:550.90.07-1.fc39            @@commandline
kmod-nvidia-6.9.6-100.fc39.x86_64.x86_64              3:550.90.07-1.fc39            @@commandline
kmod-nvidia-6.9.7-100.fc39.x86_64.x86_64              3:550.90.07-1.fc39            @@commandline
kmod-nvidia-6.9.8-100.fc39.x86_64.x86_64              3:560.35.03-1.fc39            @@commandline
libva-nvidia-driver.x86_64                            0.0.12-1.fc39                 @updates
nvidia-gpu-firmware.noarch                            20240909-1.fc39               @updates
nvidia-modprobe.x86_64                                3:560.35.03-1.fc39            @rpmfusion-nonfree-updates
nvidia-persistenced.x86_64                            3:560.35.03-1.fc39            @rpmfusion-nonfree-updates
nvidia-settings.x86_64                                3:560.35.03-1.fc39            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia.x86_64                            3:560.35.03-5.fc39            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-cuda.x86_64                       3:560.35.03-5.fc39            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-cuda-libs.i686                    3:560.35.03-5.fc39            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-cuda-libs.x86_64                  3:560.35.03-5.fc39            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-kmodsrc.x86_64                    3:560.35.03-5.fc39            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-libs.i686                         3:560.35.03-5.fc39            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-libs.x86_64                       3:560.35.03-5.fc39            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-power.x86_64                      3:560.35.03-5.fc39            @rpmfusion-nonfree-updates
xorg-x11-drv-nvidia-xorg-libs.x86_64                  3:560.35.03-5.fc39            @rpmfusion-nonfree-updates


$ inxi -Fzxx
System:
  Kernel: 6.10.12-100.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-14.fc39
  Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.14 wm: kwin_wayland dm:
    1: GDM 2: SDDM note: stopped Distro: Fedora Linux 39 (Workstation Edition)
Machine:
  Type: Server Mobo: Intel model: W2600CR v: G21602-303
    serial: <superuser required> part-nu: 00 UEFI: Intel
    v: SE5C600.86B.02.06.0007.082420181029 date: 08/24/2018
CPU:
  Info: 2x 8-core model: Intel Xeon E5-2650 v2 bits: 64 type: MT MCP SMP
    arch: Ivy Bridge rev: 4 cache: L1: 2x 512 KiB (1024 KiB)
    L2: 2x 2 MiB (4 MiB) L3: 2x 20 MiB (40 MiB)
  Speed (MHz): avg: 1446 high: 3400 min/max: 1200/3400 cores: 1: 1197
    2: 1200 3: 1200 4: 1197 5: 3400 6: 2200 7: 1762 8: 1823 9: 1197 10: 1426
    11: 1314 12: 1200 13: 1212 14: 1200 15: 1200 16: 2098 17: 1200 18: 1197
    19: 2378 20: 1200 21: 1200 22: 1200 23: 1200 24: 1197 25: 1200 26: 1200
    27: 1553 28: 1200 29: 1200 30: 1199 31: 1936 32: 1200 bogomips: 166008
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: NVIDIA GP102 [TITAN Xp] driver: nvidia v: 560.35.03 arch: Pascal
    pcie: speed: 8 GT/s lanes: 16 ports: active: none off: DP-2,DP-4
    empty: DP-1,DP-3,HDMI-A-1 bus-ID: 05:00.0 chip-ID: 10de:1b02
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.7
    compositor: kwin_wayland driver: X: loaded: nvidia gpu: nvidia
    d-rect: 4480x1440 display-ID: 0
  Monitor-1: DP-2 pos: right res: 1920x1080 size: N/A
  Monitor-2: DP-4 pos: primary,left res: 2560x1440 size: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
    gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11:
    drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 560.35.03
    glx-v: 1.4 direct-render: yes renderer: NVIDIA TITAN Xp/PCIe/SSE2
    display-ID: :0.0
  API: Vulkan v: 1.3.275 surfaces: xcb,xlib,wayland device: 0
    type: discrete-gpu driver: N/A device-ID: 10de:1b02 device: 1 type: cpu
    driver: N/A device-ID: 10005:0000
Audio:
  Device-1: Intel C600/X79 series High Definition Audio driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1d20
  Device-2: NVIDIA GP102 HDMI Audio driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 05:00.1 chip-ID: 10de:10ef
  API: ALSA v: k6.10.12-100.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel I350 Gigabit Network driver: igb v: kernel pcie:
    speed: 5 GT/s lanes: 4 port: 1020 bus-ID: 07:00.0 chip-ID: 8086:1521
    temp: 52.0 C
  IF: eno0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Intel I350 Gigabit Network driver: igb v: kernel pcie:
    speed: 5 GT/s lanes: 4 port: 1000 bus-ID: 07:00.1 chip-ID: 8086:1521
  IF: enp7s0f1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth 5.1 Radio driver: btusb v: 0.8 type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 bus-ID: 1-1.6:4 chip-ID: 0bda:8771
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: no address: <filter> bt-v: 5.1 lmp-v: 10
Drives:
  Local Storage: total: 5.86 TiB used: 949.45 GiB (15.8%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
    size: 1.82 TiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 33.9 C
  ID-2: /dev/sda vendor: TeamGroup model: T-FORCE 1TB size: 953.87 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 14 C
  ID-3: /dev/sdb vendor: Samsung model: SSD 830 Series size: 238.47 GiB
    speed: 6.0 Gb/s serial: <filter> temp: 25 C
  ID-4: /dev/sdc vendor: Western Digital model: WD10EZEX-00BBHA0
    size: 931.51 GiB speed: <unknown> serial: <filter>
  ID-5: /dev/sdd vendor: Hitachi model: HTS722016K9SA00 size: 149.05 GiB
    speed: <unknown> serial: <filter>
  ID-6: /dev/sde vendor: Western Digital model: WD20JDRW-11C7VS1
    size: 1.82 TiB type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 speed: <unknown>
    serial: <filter>
Partition:
  ID-1: / size: 93.93 GiB used: 22.19 GiB (23.6%) fs: ext4 dev: /dev/dm-1
    mapped: VG01_nvme_pcie-rootfs
  ID-2: /boot size: 1.41 GiB used: 989.4 MiB (68.6%) fs: ext4 dev: /dev/sda2
  ID-3: /boot/efi size: 1.46 GiB used: 31.6 MiB (2.1%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 400.53 GiB used: 117.76 GiB (29.4%) fs: ext4
    dev: /dev/dm-3 mapped: VG01_nvme_pcie-home
  ID-5: /opt size: 7.78 GiB used: 345.1 MiB (4.3%) fs: ext4 dev: /dev/dm-10
    mapped: VG01_nvme_pcie-opt
  ID-6: /var size: 62.44 GiB used: 11.95 GiB (19.1%) fs: ext4 dev: /dev/dm-9
    mapped: VG01_nvme_pcie-var
  ID-7: /var/log size: 1.9 GiB used: 689.3 MiB (35.4%) fs: ext4
    dev: /dev/dm-8 mapped: VG01_nvme_pcie-var_log
  ID-8: /var/tmp size: 7.78 GiB used: 528 KiB (0.0%) fs: ext4 dev: /dev/dm-6
    mapped: VG01_nvme_pcie-var_tmp
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 22.5 MiB (0.3%) priority: 100
    dev: /dev/zram0
Sensors:
  Src: ipmi Permissions: Unable to run ipmi sensors. Root privileges required.
  Src: lm-sensors System Temperatures: cpu: 28.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 96 GiB note: est. available: 94.3 GiB used: 11.11 GiB (11.8%)
  Processes: 778 Power: uptime: 18h 8m wakeups: 0 Init: systemd v: 254
    target: graphical (5) default: graphical
  Packages: 28 pm: flatpak pkgs: 22 pm: snap pkgs: 6 Compilers: gcc: 13.3.1
    Shell: Bash v: 5.2.26 running-in: konsole inxi: 3.3.34

$ lsmod |grep -iE "nvidia|nouveau"
nvidia_drm            135168  154
nvidia_modeset       1650688  78 nvidia_drm
nvidia_uvm           6836224  0
nvidia              72577024  1349 nvidia_uvm,nvidia_modeset
video                  81920  1 nvidia_modeset

After DP2 Samsung Monitor is unplugged and plugged back in  oterwise only detects Dp-4 after rebbot and have to do unplug, plug back in thing
$ xrandr
Screen 0: minimum 16 x 16, current 4480 x 1440, maximum 32767 x 32767
DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
   2560x1440     59.91*+
   1920x1440     59.90
   1600x1200     59.87
   1440x1080     59.87
   1400x1050     59.86
   1280x1024     59.89
   1280x960      59.94
   1152x864      59.78
   1024x768      59.68
   800x600       59.86
   640x480       59.38
   320x240       59.52
   1920x1200     59.88
   1680x1050     59.85
   1440x900      59.89
   1280x800      59.81
   1152x720      59.75
   960x600       59.63
   928x580       59.88
   800x500       59.50
   768x480       59.38
   720x480       59.71
   640x400       59.20
   320x200       58.96
   2048x1152     59.90
   1920x1080     59.88
   1600x900      59.82
   1368x768      59.88
   1280x720      59.86
   1024x576      59.90
   864x486       59.45
   720x400       59.55
   640x350       59.77
DP-2 connected 1920x1080+2560+0 (normal left inverted right x axis y axis) 520mm x 290mm
   1920x1080     59.96*+
   1440x1080     59.99
   1400x1050     59.98
   1280x1024     59.89
   1280x960      59.94
   1152x864      59.96
   1024x768      59.92
   800x600       59.86
   640x480       59.38
   320x240       59.52
   1680x1050     59.95
   1440x900      59.89
   1280x800      59.81
   1152x720      59.97
   960x600       59.63
   928x580       59.88
   800x500       59.50
   768x480       59.90
   720x480       59.71
   640x400       59.95
   320x200       58.96
   1600x900      59.95
   1368x768      59.88
   1280x720      59.86
   1024x576      59.90
   864x486       59.92
   720x400       59.55
   640x350       59.77

NOTE: Above DP-2 not detected if I reboot unless, as mentioned, I then unplug and plug back in DP-2

18

Problem solved!

DVI to DP transition might have been the issue preventinng detection. However I also replaced the cheap Samsung BN59-00982A with a HP Compaq LA2405x plugged into the GPU directly via DPā€™s. Dectected immediately. All fully functional.

Before Wayland however X11/xorg detected Samsung all the time but somehow Wayland did change the detection.

I do not have the time to hunt the issue further. Been on hold since system update last Friday.

Am feeling now more confident to go to F40.

:rofl: