From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [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 AD73E15817D for ; Sun, 23 Jun 2024 00:13:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1C422E2B08; Sun, 23 Jun 2024 00:13:30 +0000 (UTC) Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (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 75974E2A50 for ; Sun, 23 Jun 2024 00:13:29 +0000 (UTC) Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2eaea28868dso41077741fa.3 for ; Sat, 22 Jun 2024 17:13:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719101607; x=1719706407; darn=lists.gentoo.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=FOBqsc3bYoCnW+s4+Crg4zNuFlj6H3qbo4ktakS7tNk=; b=KNJaIfnRj1nDODqV4bzQ7yuepFaOiofX98i6HZPhNEU7g94OOisrKrlSp27XPDvHSq Hi0NYmThmFU6T1l3S6YHMe1j5vFj77ifAN9ftuuG4ku3CndWRYbTtkIAJf9IBfoGdsQA 8vlknhdpLjoUANMmw3LUdxa+jl0hQTADfyBDuNpMmioPLp/uffShpa5R8RC1dL2lI3OP 40xEKeZHNxj/9ESo2fwsgo8WuqjsB4d3R83PK9WoHqYPbDz6bZAdx5utKvGMgQPGPQTo 2mCavyhXok68PiXc8s4AAZiDVFc8JGrx4bNrQ34R4pg8ZhISiHMAPkf5zPdCW//lLt20 q82A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719101607; x=1719706407; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=FOBqsc3bYoCnW+s4+Crg4zNuFlj6H3qbo4ktakS7tNk=; b=TVEm0UNTI50+q4cC8HctRgJo82WIP+cixQS0tabOo0OzsxPFCTY+66O5/RdRBLBOkz 8BWUytBpMbDMh7KF69Tf110IY6jmCY1XCD32e9NIlv7wNKbz4j+u284UYJY6z0YIufpH 8mdRLVrwaV/9zTyKnbYWwVPV9qKwHTRIzcgB+OpBWiXaiO3FOn5cakp+5N1b1svAowjF DFH49rdhp5EjACMx0iXkUgLBqbz16nc0bltnOej2Iy1YmUl7aCs2VSSGL+nsjk4U1aGx LhEfAbPptBPEfEcPxjWdr5yoSpbIwgIUKblcBE2mFFzF0MBR4iq+2ootuwV4R9Qk6oZ9 0/MA== X-Gm-Message-State: AOJu0YwEB1AV+aWm0d9ngsPOXRQNdwgQd+qDNJ10IvXaY7moyTyjTyrp nwWVWZcONLOADLb+Cn6hnczYTLP1TRpHZNYCMQGdf+mNkWzkRnS1VFA+3/hwjtNETNvSjOfKktn dCdnAeTbmvdOKb7rxX1fcnCYLkpC2wA== X-Google-Smtp-Source: AGHT+IEhri9E6ATNIctxmMGTbUwlh5/Zwmtptj2whIha9Ugu+2LIUQI+1/qsk/ckSWKUgzBuPN6J7SHMpsEGZ4pJuEQ= X-Received: by 2002:a2e:9917:0:b0:2ec:4bb7:d7f6 with SMTP id 38308e7fff4ca-2ec5b2c4daemr6754501fa.7.1719101607167; Sat, 22 Jun 2024 17:13:27 -0700 (PDT) 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 References: In-Reply-To: From: Mark Knecht Date: Sat, 22 Jun 2024 17:13:14 -0700 Message-ID: Subject: Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="000000000000a0cc15061b838886" X-Archives-Salt: 4d4ec352-9ea2-42fe-9315-55f9ea70b8e1 X-Archives-Hash: 5626b600ec8d9137e3f127f51fcfd8e5 --000000000000a0cc15061b838886 Content-Type: text/plain; charset="UTF-8" Dale, Sorry for top posting but I'm travelling and responding on my phone. I don't think this is you hardware and probably not KDE. It's possibly some Gentoo-ish issue. To test and get a KDE config I would boot a Kubuntu flash drive and choose the 'Try it's option which installs nothing. If the GUI stays up then look at drivers and general config. I run Kubuntu on 5 machines, all with different hardware, and I've never had a failure that I did cause. I've installed Kubuntu on at least 20 machines over the last 6 or 7 machines and every one has booted first time. Give it a try. If it does fail then it's possibly something about your hardware but if the machine works as well as you say then I would buy you a cup of coffee if it's not Gentoo-bssed. Good luck, Mark On Fri, Jun 21, 2024, 12:03 PM Dale wrote: > Howdy, > > On my new rig, I've got everything installed. I mostly been on a > console which has worked without issue. Now I've started using the GUI, > KDE, and I'm having issues. I wanted to run a command to generate a > xorg.conf file and it generate all the needed info regarding hardware > and such since the GUI wasn't working right without a config file. The > only one I found is the nvidia one. It is minimal at best. Anyway, > when I try to start display-manager, with or without a config file, I > get the sddm login. I login and if I just let it sit there, after a > minute or so, the monitor goes black. It is still powered up but > nothing on the screen at all. I've moved the mouse and pressed buttons > on the keyboard to make sure it isn't powering off but nothing. Also, > the resolution is pretty low too. It should run in 1080P easily. The > card supports 4K I think. The monitor tho has ran 1080P on my main rig > before, for years I might add. > > I used tail -f to watch a few error logs. I watched sddm, messages and > Xorg.0.log. The only thing that got added when the monitor went black > was this: > > > > Jun 21 13:27:41 Gentoo-1 kernel: nvidia-modeset: WARNING: GPU:0: Unable > to read EDID for display device DP-3 > Jun 21 13:29:01 Gentoo-1 kernel: nvidia-modeset: WARNING: GPU:0: Unable > to read EDID for display device LG Electronics W2253 (DP-3) > Jun 21 13:29:02 Gentoo-1 kernel: nvidia-modeset: WARNING: GPU:0: Unable > to read EDID for display device DP-3 > Jun 21 13:29:03 Gentoo-1 kernel: nvidia-modeset: WARNING: GPU:0: Unable > to read EDID for display device LG Electronics W2253 (DP-3) > > > If I let it sit for a good while, it comes back on, sort of. The plasma > panel thing on the bottom, where the app menu, clock and all is, doesn't > come back tho. Also, the background is just black, no picture like > usual. The only thing that shows up is gkrellm. I'm pretty sure plasma > died. I thought maybe it was heat, the fan isn't running on the video > card or something. Nvidia shows the card between 25 and 30C. The fan > nvidia says is at 34%. If that is correct, then the fan is running and > heat is not a issue. Out comes the flashlight and a mirror. Yep, fan > spinning. According to IR temp thingy, nothing even gets into the 90F > area. I think if it was heat, I'd see something getting hot with the IR > temp thing. > > There is two versions of Nvidia driver for this card in the tree. I've > tried both, no change at all. Screen goes black and after a while comes > back but most of the desktop has crashed. > > By the way, I ran the tail command over ssh. Sometimes when the monitor > goes black, it doesn't come back. I can use ssh to reboot and repeat tho. > > Did I miss something during the install? Does the error above cause > this problem? If so, how do I fix it? If you need info, just let me > know the command to run. I monitored all I could think of. The one > above is all I saw that showed a problem exists. Given this rig is > still in testing, I can reboot or anything else as needed. > > Thanks. > > Dale > > :-) :-) > > --000000000000a0cc15061b838886 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dale,
=C2=A0 =C2=A0Sorry for = top posting but I'm travelling and responding on my phone.

=C2=A0 =C2=A0I don't think this = is you hardware and probably not KDE. It's possibly some Gentoo-ish iss= ue.

=C2=A0 =C2=A0To test= and get a KDE config I would boot a Kubuntu flash drive and choose the = 9;Try it's option which installs nothing. If the GUI stays up then look= at drivers and general config. I run Kubuntu on 5 machines, all with diffe= rent hardware, and I've never had a failure that I did cause. I've = installed Kubuntu on at least 20 machines over the last 6 or 7 machines and= every one has booted first time.

=C2=A0 =C2=A0Give it a try. If it does fail then it's possibl= y something about your hardware but if the machine works as well as you say= then I would buy you a cup of coffee if it's not Gentoo-bssed.

Good luck,
Mark

On Fri, Jun 21, 2024, 12:03 PM Dale <rdalek1967@gmail.com> wrote:
Howdy,

On my new rig, I've got everything installed.=C2=A0 I mostly been on a<= br> console which has worked without issue.=C2=A0 Now I've started using th= e GUI,
KDE, and I'm having issues.=C2=A0 I wanted to run a command to generate= a
xorg.conf file and it generate all the needed info regarding hardware
and such since the GUI wasn't working right without a config file.=C2= =A0 The
only one I found is the nvidia one.=C2=A0 It is minimal at best.=C2=A0 Anyw= ay,
when I try to start display-manager, with or without a config file, I
get the sddm login.=C2=A0 I login and if I just let it sit there, after a minute or so, the monitor goes black.=C2=A0 It is still powered up but
nothing on the screen at all.=C2=A0 I've moved the mouse and pressed bu= ttons
on the keyboard to make sure it isn't powering off but nothing.=C2=A0 A= lso,
the resolution is pretty low too.=C2=A0 It should run in 1080P easily.=C2= =A0 The
card supports 4K I think.=C2=A0 The monitor tho has ran 1080P on my main ri= g
before, for years I might add.=C2=A0

I used tail -f to watch a few error logs.=C2=A0 I watched sddm, messages an= d
Xorg.0.log.=C2=A0 The only thing that got added when the monitor went black=
was this:



Jun 21 13:27:41 Gentoo-1 kernel: nvidia-modeset: WARNING: GPU:0: Unable
to read EDID for display device DP-3
Jun 21 13:29:01 Gentoo-1 kernel: nvidia-modeset: WARNING: GPU:0: Unable
to read EDID for display device LG Electronics W2253 (DP-3)
Jun 21 13:29:02 Gentoo-1 kernel: nvidia-modeset: WARNING: GPU:0: Unable
to read EDID for display device DP-3
Jun 21 13:29:03 Gentoo-1 kernel: nvidia-modeset: WARNING: GPU:0: Unable
to read EDID for display device LG Electronics W2253 (DP-3)


If I let it sit for a good while, it comes back on, sort of.=C2=A0 The plas= ma
panel thing on the bottom, where the app menu, clock and all is, doesn'= t
come back tho.=C2=A0 Also, the background is just black, no picture like usual.=C2=A0 The only thing that shows up is gkrellm.=C2=A0 I'm pretty = sure plasma
died.=C2=A0 I thought maybe it was heat, the fan isn't running on the v= ideo
card or something.=C2=A0 Nvidia shows the card between 25 and 30C.=C2=A0 Th= e fan
nvidia says is at 34%.=C2=A0 If that is correct, then the fan is running an= d
heat is not a issue.=C2=A0 Out comes the flashlight and a mirror.=C2=A0 Yep= , fan
spinning.=C2=A0 According to IR temp thingy, nothing even gets into the 90F=
area.=C2=A0 I think if it was heat, I'd see something getting hot with = the IR
temp thing.=C2=A0

There is two versions of Nvidia driver for this card in the tree.=C2=A0 I&#= 39;ve
tried both, no change at all.=C2=A0 Screen goes black and after a while com= es
back but most of the desktop has crashed.=C2=A0

By the way, I ran the tail command over ssh.=C2=A0 Sometimes when the monit= or
goes black, it doesn't come back.=C2=A0 I can use ssh to reboot and rep= eat tho.=C2=A0

Did I miss something during the install?=C2=A0 Does the error above cause this problem?=C2=A0 If so, how do I fix it?=C2=A0 If you need info, just le= t me
know the command to run.=C2=A0 I monitored all I could think of.=C2=A0 The = one
above is all I saw that showed a problem exists.=C2=A0 Given this rig is still in testing, I can reboot or anything else as needed.=C2=A0

Thanks.

Dale

:-)=C2=A0 :-)=C2=A0

--000000000000a0cc15061b838886--