From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why is KDE so bad at multiple monitors?
Date: Sun, 25 Feb 2024 18:10:15 +0000 [thread overview]
Message-ID: <2926650.e9J7NaK4W3@rogueboard> (raw)
In-Reply-To: <9b47ecee-b684-490b-bba6-7cb55c4a71b9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
On Sunday, 25 February 2024 17:36:25 GMT Daniel Frey wrote:
> On 2/25/24 01:01, Michael wrote:
> > I used to experience the same when using Xorg with AMD-Radeon graphics
> > instead of Nvidia, but since I moved to Wayland the problem of losing
> > screen settings has gone. One monitor is using the DVI port of the card
> > and the other HDMI. It should be worth trying Wayland instead of Xorg to
> > see if it works out better for your setup.
>
> I actually tried Wayland maybe 3 months ago to try to solve the problem.
> Wayland doesn't work at all - it just gave me a blank screen at login. I
> did check USE flags and recompiled and still login did not work at all.
>
> At least Xorg gave me a misconfigured working login (better than no
> login at all.)
>
> -Dan
From the little I know about Nividia nuances the symptom of a black screen
points to KMS mode setting missing in the kernel. Also nvidia_drm.modeset
should be able to load without errors, or the wayland compositor will not
work. Also, I recall reading somewhere Nvidia does not like monitors with
different resolutions and refresh rates, but I don't know if there is any
workaround to this. TBH I moved away from Xorg because it was getting worse
and worse over time with my graphics. Wayland was a bit unstable on my
systems in the beginning, but over time it has improved significantly.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-25 18:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 4:53 [gentoo-user] Why is KDE so bad at multiple monitors? Daniel Frey
2024-02-25 5:52 ` Dale
2024-02-25 9:01 ` Michael
2024-02-25 15:08 ` Dale
2024-02-25 17:36 ` Daniel Frey
2024-02-25 18:10 ` Michael [this message]
2024-02-25 17:34 ` Daniel Frey
2024-02-25 18:17 ` Mark Knecht
2024-02-27 15:21 ` Daniel Frey
2024-02-25 11:29 ` Paul Colquhoun
2024-02-28 22:13 ` Paul B. Henson
2024-02-28 22:23 ` Dale
2024-02-28 22:43 ` Mark Knecht
2024-02-29 11:27 ` Dale
2024-03-03 18:59 ` Daniel Frey
2024-03-03 19:31 ` Dale
2024-03-03 19:39 ` Daniel Frey
2024-03-03 21:57 ` Dale
2024-03-03 22:39 ` Daniel Frey
2024-03-03 23:47 ` Dale
2024-03-03 21:20 ` Michael
2024-03-04 2:39 ` Dale
2024-03-14 21:23 ` Mart Raudsepp
2024-03-05 10:56 ` Arsen Arsenović
2024-03-02 5:11 ` Paul B. Henson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2926650.e9J7NaK4W3@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox