From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8D1D915802E for ; Wed, 26 Jun 2024 08:31:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2FF662BC0C1; Wed, 26 Jun 2024 08:30:44 +0000 (UTC) Received: from bisque.elm.relay.mailchannels.net (bisque.elm.relay.mailchannels.net [23.83.212.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6D0402BC0BC for ; Wed, 26 Jun 2024 08:30:43 +0000 (UTC) X-Sender-Id: thundermail|x-authsender|confabulate@kintzios.com Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id C87CEC2752 for ; Wed, 26 Jun 2024 08:30:41 +0000 (UTC) ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1719390641; a=rsa-sha256; cv=none; b=E+27Xc3oM2nm71gXfElcLaJSrIneWIteLeEgvQyQTZuK3eDBrgPqW2E60Q6c7gDdytWBSV doRVH3posXasZvLroeSHKut7kYwsHpXozCjbKH7H2EFqAcWbmOPUDyoK9xp37UFAx1oAvd 7kBS0YHS8zYjzQrsCFfk7zaqDlgpezfaO/AmufxhP4OLzWdOX+Gyt+T93gAEgtaR86YvGE jooxR5j9Lp2AuCaijN5lp6AFHMbAJiOo3h5rv3v7lq0nHXp09BQD1swGLSKn2sa1ANvZuw qHtS36Ngda5XC9dmF/kWdlbppW2kZcSsj9INO/2sBXwcw4FC8ImVpDygY11OeA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1719390641; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=QHKzpVaXk9dBoMgXDP5URRdw8ZyWwQFPguBCy2q/ZcY=; b=L+lg+mWfT2JmUrk9AMa3oqIdPzqYKqAOApHoO5FtbKW9hBFXLvJ8j481u0zNYn2cmFmN8V 4vP36kW1mQW8zJsmGDQzj6lTz4vM3Og4NSVlkmHjFwQbACOqM9BZJLHvJpr7CoXa1Pp927 Ad1o26d3xrc/IngY3m0mRaqSe+bOZJ0cs4jfV8G2H3RBeEZu+uz2wisP82olv08fc5XBvB 3TEkMhhQ2jSXVS2L55rLAQ2rDDwBko81h/C1gdfn+8s+amQQdn1vP9nETBEijPWND9Cyei a2lufFcdWp94NQKHWunZmdwd7WJWuhZnXHbX6lOEZgrWMSs8AqNWKE4xIKGJuQ== ARC-Authentication-Results: i=1; rspamd-79677bdb95-g2xxx; auth=pass smtp.auth=thundermail smtp.mailfrom=confabulate@kintzios.com X-Sender-Id: thundermail|x-authsender|confabulate@kintzios.com X-MC-Relay: Neutral X-MailChannels-SenderId: thundermail|x-authsender|confabulate@kintzios.com X-MailChannels-Auth-Id: thundermail X-Whispering-Quick: 3a14f5db7eaf7f50_1719390641495_1604850462 X-MC-Loop-Signature: 1719390641495:3917166866 X-MC-Ingress-Time: 1719390641495 Received: from mailclean11.thundermail.uk (mailclean11.thundermail.uk [149.255.60.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.96.69.200 (trex/6.9.2); Wed, 26 Jun 2024 08:30:41 +0000 Received: from cloud238.thundercloud.uk (cloud238.thundercloud.uk [149.255.62.116]) by mailclean11.thundermail.uk (Postfix) with ESMTPS id CFD4C1E0006 for ; Wed, 26 Jun 2024 09:30:38 +0100 (BST) Authentication-Results: cloud238.thundercloud.uk; spf=pass (sender IP is 217.169.3.230) smtp.mailfrom=confabulate@kintzios.com smtp.helo=rogueboard.localnet Received-SPF: pass (cloud238.thundercloud.uk: connection is authenticated) From: Michael To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] SOLVED Can't get the GUI to stay up for more than a minute or so before crashing Date: Wed, 26 Jun 2024 09:30:17 +0100 Message-ID: <1896970.CQOukoFCf9@rogueboard> In-Reply-To: References: <10512977.nUPlyArG6x@rogueboard> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart23558748.6Emhk5qWAg"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-PPP-Message-ID: <171939063757.3230416.3787302278249413792@cloud238.thundercloud.uk> X-PPP-Vhost: kintzios.com X-Rspamd-Server: mailclean11 X-Spamd-Result: default: False [-1.61 / 999.00]; SIGNED_PGP(-2.00)[]; MID_RHS_NOT_FQDN(0.50)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; ONCE_RECEIVED(0.10)[]; MX_GOOD(-0.01)[]; R_SPF_ALLOW(0.00)[+mx]; FUZZY_BLOCKED(0.00)[rspamd.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:34931, ipnet:149.255.60.0/22, country:GB]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_ONE(0.00)[1]; R_DKIM_NA(0.00)[]; RCVD_TLS_ALL(0.00)[]; NEURAL_HAM(-0.00)[-0.998]; REPLYTO_ADDR_EQ_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DMARC_POLICY_ALLOW(0.00)[kintzios.com,none]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[gentoo-user@lists.gentoo.org]; HAS_REPLYTO(0.00)[confabulate@kintzios.com] X-Rspamd-Action: no action X-Rspamd-Queue-Id: CFD4C1E0006 X-Archives-Salt: 46c7d956-42ea-4327-a28b-026251a5590e X-Archives-Hash: d14421f60abdd756f45224245f07dee4 --nextPart23558748.6Emhk5qWAg Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8"; protected-headers="v1" From: Michael To: gentoo-user@lists.gentoo.org Reply-To: confabulate@kintzios.com Date: Wed, 26 Jun 2024 09:30:17 +0100 Message-ID: <1896970.CQOukoFCf9@rogueboard> In-Reply-To: MIME-Version: 1.0 On Wednesday, 26 June 2024 01:28:47 BST Dale wrote: > Michael wrote: > > The above message indicates the same problem you had experienced before > > you > > reinstalled. The monitor is not sending its EDID table, or the card can't > > read it. > > > > Your Xorg sets a default dummy resolution of 640 x 480, because it can't > > find anything connected to the card. > > > > Things I would try, until someone who can grok nvidia contributes better > > ideas: > > > > Eliminate the hardware being the cause of the problem, e.g.: try a > > different cable, different monitor, then try the same card (with same > > drivers and same kernel settings) on your other PC. If this proves > > there's nothing wrong with the cable, card, or kernel settings: > > > > 1. Try different ports and restart display-manager each time. > > > > 2. Add these two lines at the bottom of /usr/share/sddm/scripts/Xsetup: > > > > xrandr --setprovideroutputsource modesetting NVIDIA-0 > > xrandr --auto > > > > Again restart display-manager. > > > > 3. Add a file /etc/X11/xorg.conf.d/20nvidia.conf > > > > Section "Device" > > > > Identifier "nvidia" > > Driver "nvidia" > > BusID "PCI:9:0:0" > > Option "UseEDID" "false" ## Try this too ## > > > > EndSection > > > > Again restart display-manager. > > > > Every time you try a setting and it doesn't produce the goods, revert it > > before you try the next thing. Make notes and keep an eye on your logs in > > case you spot a difference. > > > > If none of these tweaks work, then you can try capturing the EDID table > > and creating a file for the card to load. [snip ...] > I was > even thinking of moving my main rig monitor to the new rig and see what > it did. I'd already tried a different card so didn't see any need in > repeating that. Then I had a thought. Why is it saying port DP-3? Why > is it not port DP-0? Your PC indicated DFP-3 was what it had booted at - from your Xorg.0.log: [ 44.311] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:9:0:0 [ 44.311] (--) NVIDIA(0): DFP-0 [ 44.311] (--) NVIDIA(0): DFP-1 [ 44.311] (--) NVIDIA(0): DFP-2 [ 44.311] (--) NVIDIA(0): DFP-3 (boot) [ 44.311] (--) NVIDIA(0): DFP-4 [ 44.311] (--) NVIDIA(0): DFP-5 [ 44.311] (--) NVIDIA(0): DFP-6 [ 44.311] (--) NVIDIA(0): DFP-7 which is the display device connector type nvidia identifies the monitor being connected to. However, then it prints this discouraging message: [ 44.312] (--) NVIDIA(GPU-0): [ 44.332] (--) NVIDIA(GPU-0): DFP-3: disconnected <== This === [ 44.332] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS [ 44.332] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock [ 44.332] (--) NVIDIA(GPU-0): > I thought the first port was the one on the > bottom. Turns out, the top port is the first one. So, I moved the > cable to the first port, DP-0. I thought you had already tried this prior to reinstalling, when I had suggested to try different ports. > I booted the rig up, started DM, got the > login screen as usual and guess what was next, a complete desktop. I > changed it to not power off or switch to a screensaver so that it would > stay on and I could keep a eye on it. I heated up supper, ate, typing > this reply and it is still running, in 1080P no less. YES! :-D > Now tell me this, why would it not work on DP-3 or DP-2 when I tried > those earlier on? Does one always have to have a monitor connected to > DP-0 first then others as monitors are added? It may have something to do with auto-detecting PNP display devices, like DisplayPort monitor devices. There is a HPD pin (Hot Plug Detect) on the DP, which lets the card know if a monitor turns off. This seems to cause the card's driver to detect the display as "disconnected", which then disables the port. The question is why would the monitor turn off. Well, it might be taking too long for the card to walk from DP-1 to DP-3, by which time the monitor has gone to sleep to save energy. If the monitor is on DP-1, then it doesn't get a chance to do this. Alternatively, the Quadro P1000 video card being a 'pro' graphics card may have been designed with the assumption a monitor (the primary monitor) is *always* connected on the first port, or else the PC is configured as a headless server - I don't know really. I think if you capture and feed manually the EDID table to the card's driver, it may work differently - but again, I have no experience with Nvidia. By accident or good fortune I've always had 'linux-friendly' AMD-Radeon cards on my PCs. One thing I have noticed with my DisplayPort monitor, it needs to be powered on while the PC boots up/shuts down. If the monitor is switched off it will not get detected after boot and also the shutdown process is cancelled. :-/ > Now comes the next question. To move just KDE stuff over, desktop > settings and such. ~/.local and .config. Are those the big ones? Yes, if we're talking about plasma and kde applications. You'll also need: .mozilla .ssh .gnupg .gkrellm2 and others, if you want to keep their settings the same across PCs. > Also, I have a .kde4 directory, that's no longer used right? I think it > died ages ago. I forgot all about that thing. Last time kde4 was touched on my system was in 2022 - perhaps I changed some theme/panel colors or some such. I thought it was defunct as a directory for some year now: ~ $ ls -la .kde4/share/apps/color-schemes/ total 23 drwxr-xr-x 2 michael michael 3452 Oct 1 2022 . drwxr-xr-x 3 michael michael 3452 Jun 14 2019 .. -rw-r--r-- 1 michael michael 3519 Jun 16 2019 Breeze.colors -rw-r--r-- 1 michael michael 3806 Jun 15 2019 BreezeDark.colors -rw-r--r-- 1 michael michael 4474 Oct 1 2022 Oxygen.colors ~ $ ls -la .kde4/share/config/ total 11 drwxr-xr-x 2 michael michael 3452 Oct 1 2022 . drwxr-xr-x 4 michael michael 3452 Jun 14 2019 .. -rw------- 1 michael michael 3403 Oct 1 2022 kdeglobals > I'll copy the other > stuff over at some point but just want to play with the big stuff at the > moment. > > In your list, #1 would have been the fix. It also turns out, it was > me. I plugged the cable in the wrong port. No idea why everything else > worked fine tho. All the boot media worked just fine. This is a large > thread over something so simple. ;-) Well, if I had more experience with Nvidia, or if you tried each and every port as I erroneously assumed you had done, it may not have taken this long! ;-) > Thanks so much for all the help. The main rig is still sitting there at > 1080P waiting on me. Finally, after over $1,000 spent, days of > installing, twice, and a lot of testing, a working computer. :-D :-D > > Dale > > :-) :-) Could you please send me your Xorg.0.log again with a working and powered up monitor, off-list to keep the noise down. I'd be interested to see what it reports now the monitor is connected to DP-1 and initialized correctly. --nextPart23558748.6Emhk5qWAg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmZ70ZkACgkQseqq9sKV ZxnDUg/+P6KrP+GFy2vPyJqUphGgH9oeyAKWQLvkcOBaW9AseBJJWfEyt6A+grXk 4BGqGi9VhStVFmYvVD7iK8HxhaIG/dk1NErYQUwXdqdFSrEdEmShblU1IsgrJb9Y J9bHYR58gWp1v8qQ5OxsZLtbr+K6DnLKCpdYD6VjcdZp4sV3wJ+4k4ck+NTuhYIe b0PsCMZxlHIAbgIme4mcJbBqSvF3ZZRyTZLBwiIlBgHe7XIzHLxd8IVf1PyuyiiF EF2acJ5NF5lNfihfqNDuDoVoAm4YaSJ4HMjiszS0mp0+9USGeYlWAddZYtASQSCK Y7jrKpvuDiIMa+xLcLFzWMzi0qzstDcXwbjak1GUuTEotQ6NZed8qT0iO4lovQd9 yXmwaImIsfKZrYIeZoeEVOrkT/8W8nSTgaKisFyWuZlx2g4DoLxcIveejBsDRH9r b5cK9C6WvVOgn6O/+fEYit5SrvyIkaXqnD84E9XK7HlYVj4P1xfQu4UVou0FVAOi fhyr6hqd39izzjMRl6Tp9Ta3evFj4Sn5xwFFQTBF0zZGwoLFRKNYHh7ryvwmNZvl AQd/+3Y2ZrromAHGIfOoz3DY7GwAspzyov5x9DDWY1Bfk76t9FbudEAKO66nOIUT 1eay312jX+meBRU6vfnLXC014LnhXHZZPOqKBaCicwXu0VMbA9k= =KfYp -----END PGP SIGNATURE----- --nextPart23558748.6Emhk5qWAg--