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 E12F415802E for ; Mon, 1 Jul 2024 13:51:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 75915E2B07; Mon, 1 Jul 2024 13:51:55 +0000 (UTC) Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (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 D7DD5E2AC4 for ; Mon, 1 Jul 2024 13:51:54 +0000 (UTC) Received: by mail-oi1-x22a.google.com with SMTP id 5614622812f47-3d562882f4cso1753025b6e.3 for ; Mon, 01 Jul 2024 06:51:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719841914; x=1720446714; darn=lists.gentoo.org; h=in-reply-to:mime-version:user-agent:date:message-id:autocrypt:from :references:to:subject:from:to:cc:subject:date:message-id:reply-to; bh=qSH+EQD8aEHn5LNlZ1T54JEpa8gltgDIKq270eWYBSo=; b=O+ORU09qzVVbsh4yGZu2PtV2ho7b+5/oClUPI56y2hTOUXMfwXTzecyKztnIt08eru fzCi/uKwIEkgPqPgNaJdH4ukCIMC0v89Ec9E1EU0fgGaivboQIdsEQxrC1rK7Otf8ejA MyTu4K8vDZ0eJ+yEtaJiHCrCLkVrXq0DzWshL8n96gWY2VI2pL926L8izdX/IyJbFrua m2Xu/5ojZ901+R/HUQSEl3Fkt7Fg0mx5B6ZM/mywGcfoBhQdo80U/ztUJ51Z0rz4ieCq rbBm8Sq2guWi3Lxb3ZW0CI7SH5/BOJ+wAYcMxrE6MabAa7XQkXxTVXk4EZi65mKwBpOm 1w8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719841914; x=1720446714; h=in-reply-to:mime-version:user-agent:date:message-id:autocrypt:from :references:to:subject:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=qSH+EQD8aEHn5LNlZ1T54JEpa8gltgDIKq270eWYBSo=; b=hMEQCPwo3Tbrpt3noOQlqQTollwXZJMlfKrnvGI7v+9SiRMyBHb0sXD0e+Fj39Ednf wZFAgM7eByU2V11h93JEoMkeOOU8Ya+TfCQ2f6ZTg8HgckQQRl0/hGCFcuL6IXE2jMWT XNebKYFiyAlND3xWHEpO2Qt1eH86pWyPNOIznS99vagG81vI7F7mgfbWa4+Cqlde4QhB 6jPJgWCrbZfLK86lffIrqx/GKxM0uSrAWS7gxtaXYRHiL/YCITOqZ5MTDc4QTWHnuI/u hN1OfAcUazWF5YfswsFB4tnjmcJMWmrmDnmU93tP6fVIjVmQZPLNjSzOEhu7fzNreCa7 jFHA== X-Gm-Message-State: AOJu0YwLBuTTLqVtsU4GBUzyqI1lhB7J2sHUX7QGCLZEMKH95tMVSVKC DUeBDav9ZkQkZhyF8H9B7Qq77IGixO1kSqSNjaAGXG4Kdf7WtPYZ X-Google-Smtp-Source: AGHT+IG/4Qa1NlB5eImW8XCj7HaNqCDJHlX5hKOWhLK80NRxxCkJIk8z4cGdUcTo/xwcHkMQkNhoqw== X-Received: by 2002:a05:6808:2011:b0:3d2:1d67:13e4 with SMTP id 5614622812f47-3d6b50c1ba1mr8923131b6e.36.1719841912440; Mon, 01 Jul 2024 06:51:52 -0700 (PDT) Received: from [10.8.8.16] ([37.19.221.89]) by smtp.gmail.com with ESMTPSA id 5614622812f47-3d62fb4b2d0sm1368993b6e.55.2024.07.01.06.51.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Jul 2024 06:51:52 -0700 (PDT) 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 References: <2201848.Icojqenx9y@rogueboard> <4123ac85-e2ce-4b8c-6e27-91d089eef024@gmail.com> <1973249.PYKUYFuaPT@rogueboard> From: Dale Autocrypt: addr=rdalek1967@gmail.com; prefer-encrypt=mutual; keydata= mQINBGFSciYBEADcEGMyJBSuavKO/XKUVvgkxck7Nl8Iuu8N2lcnRji/rSKg5c1Acix1ll9i oW8JBCHwvn0+Xy60BvEsqcup3YSHw5STl/bR1ePEehtnYrg8FdjdS91+B805RfnKMm69rFVI wLSBHQrSG1yxHd8CloWoEdhmVtP24buajbh114bgXd9ahtpZrCVMrWdWYUg2mEXguGV5uNAh Rf8SWxDNc79w24JxsV34a8niMUYMjzWr0rafIbzk732X38vGjVMLo/2mMpkbp9mPp++LHoY+ 0Pet8zxxdXPJSCd475kza1AD+hhSyBZXB9yknYWgyY3cZe1rGmooJSi2KX4QxO7npwLThcO1 be6KKRkd35+Fi/a1BzVOHsZMiK/gcwxEFoMd27gir4ehaeHJfFXl+65w4hj0EsOZSxrJrm2C R50g5By2czSKP1bADEygFNpIJj51AR+wM88NImG2RPtlT2maYBzazvF05g65cdHXGp1C7W5P wwwKU2DgABB2t7N7z5A69LnryBRw4zUYDRRYLTYlBlYgg+xILm2c0OrBdxJgLJa7JE50Eo25 d3PFwt9J0gYvqy6sPFLl9So0sDg9zm0hKQtXOP5kgropUFGrNoJI+mjwF4rYLRBVzZwNAvlO OhEvHubBo3mEllv4x+FeptwXZxlk7gUsdqI8AxnFB8K9wi6FVQARAQABtBtEYWxlIDxyZGFs ZWsxOTY3QGdtYWlsLmNvbT6JAk4EEwEIADgCGyMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AW IQQSG1h01ruv/WNXc3Q3RqOgiQH1GwUCYVJy8gAKCRA3RqOgiQH1G+waEACeTZCt77jnRAmQ AV7otKuZekDWiLi3Eig8tj5ZJiCNSYA/hIxzmexRP0GMqjitcXK1iGwWcvMzzvIq30GAjIfB 4BR38cnXbtBa6fNewiT7QaZe/Hn6yBRldXNQypzbHy+/o27bUEy+oX4rE7etUgEHQAjuw7xz XFWg4tH1/KJvsOVY5upnWc5LdxYhsuQ3dQD4b22GsK0pOBDfb9PiirYM8eGKvrVuq4E/c75z lDDFhINl18lNZ9D0ZFL3IkTjHsAAqFH9uhnnEB8CWdHbBewPEfRaOhBUYWZ3Q8uTkmDgZT8q D9jlvLEdw7Nh2ApdxoepnI/4D+ql2Gr4DtH7SEPydr5gcf1Qr/2bXRb1hAYnIVcbncs/Bm3Z bkRKPVWMfE3Fusa+p5hMzixk0YysMaTHlc7mYRYAEZGnPMXnmcCbetwARU7A0yz1M1kCMOAQ Lsz8KH5kv3cRenMB6SFfjND2JfAK61H5TtnPq3L8noS2ZykRYxq9Nm3X64O1tJojIKBoZFr8 AwYNCvqC6puUyGMuzHPh7jPof8glfrrEKIYUvNPGMDoVX3IGetxh/9l6NcxgFA4JGoR+LS3C zmeNrwlllAe3OEUfKoWVQ+pagpSdM+8hHolaSda4Ys66Z3fCR4ZvcTqfhTAVskpqdXa4isAk 7vTcXu3L499ttywEp7rJTbkCDQRhUnImARAAncUdVhmtRr59zqpTUppKroQYlzR0jv8oa7DG K4gakTAT2N7evnI9wpssmzyVk8VEiLzhnFQ/Ol3FRt6hZCXDJt0clyHOyTfvz/MNFttWuZTc mLpSvmRR6VRjAH+Tz3Eam2xUw3PGuH97BcXQ3NnX3msv1UDxtxxBu6e2YrdeOhrCUSgzokcJ 98ChUNy934cgepPybAI12lSWqVFQ1aG7jExZfiUk+333fPSDbpKoZbTW5YJLXbycmW/C1IWL qYQyNjRWKaGoJtUWFhhmNiOQct7n90aKivNVPavmN+UQ9LlMaINtf9T6XCzLfogCFsulDCDJ 0yNQLDTurHaB4E71xoctgXmLLq9z1RQ0W2XiVAAOZQj6K3+d0AOUjDhCQ2QW8dUSq0ckkZXV DKVJOGS8Nhf2eIWIqRnP3AcUiiaiFGqUaVUmUAZ6h/oJmgghEu/1S+pcuUKU5i69+XCZ3hH2 Jzwzbf7K+FAIkOhCfHncF8i1N1pk00pOVykNnqHTfFo3qFusHt0ZWgXVnnn4pYdXqZNoDhvF BRE5Vm4k/k96Pw8HRx6Os6eFSRrlqGzRgqsu86FekxusXB9UGv4lJhtU/J+8MRWsh22K718s DbQnABicGKFz1qQlWvcf59oTByhLINJCBt1WXl+TzJDXepr3QSkqmK41dO9Hob97C9dMiK8A EQEAAYkCNgQYAQgAIAIbDBYhBBIbWHTWu6/9Y1dzdDdGo6CJAfUbBQJhUnLyAAoJEDdGo6CJ AfUbVHIQAKSWw620vPhR3A/njU2z77F3z/Jk+HTKdE3fIyWSWdkYN7CBFL0NguOMP30WZ+qE sJhZu7T5hf251MwQUUt27xlfnKYOmQs7CqONlXuXlGZI6WufrUjxNcVz+5gJsqvUWuuJWsgg sDmE92IBnfG/f81fPHWQyfr/SF4wYDMyoFp5xCCQpp1zB63iuFvvrhxBkEHzmbRtVDOhl0Xp BVEDR1w3QRACw9QJD/KM05Czv9JNQYlwinWO/OaQ9cMlUpKLgswUPg9IZ5vucxScfuAUA5uC B1jlAQ8ZPlVukBmbEv5RGOv+lpuEbA3YDMVtEeH4YMFbjt/+vH3Cr2vTbp5JlpByLburJEH0 WXZLUawEfUsZvVwpOuJK75vaa2HYXee+Cb3iCIzwfIfctdlqzUcbGRczlRNM59hpvj4z29Gh 3kAxVHItAYq54ikxQ9l4hQ8s9sLYPbX/WtcBxNX8crBSw0FLnmzGleVEtBHyqtt5CLzQNgrj GYWl1vKDUmRPw1CdZ1c+fMN9CY11jOM5B5ZnqZWfDeVYO2iJ5SuvTycChexCb8WYn1bdCBIo bBtga2RBXbVt4Mh9E4owsszefn51MwfjXxB20Fc5k3GU1AVpTCMs3ayYCzo0b2pvEvdjtDcA CYLEFPWgaFX9iQAM/CDfKvTtvgGWpqtCL2raq/mQoJEU Message-ID: Date: Mon, 1 Jul 2024 08:51:49 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.18.2 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 In-Reply-To: <1973249.PYKUYFuaPT@rogueboard> Content-Type: multipart/alternative; boundary="------------DF77AF38BD28B165A723C460" X-Archives-Salt: 3cc64215-e52b-4b8d-97b8-1760130c26df X-Archives-Hash: 24167947dc254bb52784b29fafa7b026 This is a multi-part message in MIME format. --------------DF77AF38BD28B165A723C460 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Michael wrote: > On Sunday, 30 June 2024 23:56:40 BST Dale wrote: >> Michael wrote: >>> This is good! :D >>> Edit the section below by adding the PreferredMode line: >>> >>> Section "Monitor" >>> >>> Identifier "Monitor0" >>> VendorName "Unknown" >>> ModelName "LG Electronics W2253" >>> HorizSync 30.0 - 83.0 >>> VertRefresh 56.0 - 61.0 >>> Option "PreferredMode" "1920x1080_60.00" >>> Option "DPMS" >>> >>> EndSection >>> >>> Save it, then check if you get a consistent result when you restart the >>> DM, or reboot. >>> >>> If it is still playing up you need to show the Xorg.0.log while the >>> monitor is working with the nvidia driver, to see which Modeline it uses >>> and add this in the "Monitor" section too, above the "PreferredMode" >>> entry. >>> >>> If none of this works reliably, then you have to capture the EDID table >>> while the monitor is working, save it in a file and set nvidia-settings >>> to use it hereafter. However, if you will NOT be using this monitor for >>> much longer this would be an exercise only to make you feel good for >>> beating it into submission! LOL! >> OK. First time, it worked. Second time, it came up but in low res. >> Plasma was working to, both times. So, I opened the Nvidia GUI and told >> it to safe a new config with it in hi res mostly just to see what it >> would add if anything. It did. The only change I could see was it >> added metamodes options like this: >> >> Section "Screen" >> >> # Removed Option "metamodes" "nvidia-auto-select +0+0" >> Identifier "Screen0" >> Device "Device0" >> Monitor "Monitor0" >> DefaultDepth 24 >> Option "Stereo" "0" >> Option "nvidiaXineramaInfoOrder" "DP-3" >> Option "metamodes" "1920x1080 +0+0" >> # Option "metamodes" "1920x1080 +0+0; 1024x768_60 +0+0" >> Option "SLI" "Off" >> Option "MultiGPU" "Off" >> Option "BaseMosaic" "off" >> SubSection "Display" >> Depth 24 >> EndSubSection >> EndSection >> >> >> As you can see, I removed the low res part, don't want that anyway, and >> it seems to work more often but still fails a lot. So, I removed the >> metamodes Nvidia added. Then it didn't come up at all, sddm or >> anything, when I restarted DM. I thought it adding your setting to >> another section might help. Guess not. With the following removed, it >> seems to do a little better but still can't depend on it to work. >> >> Section "Screen" >> # Option "nvidiaXineramaInfoOrder" "DP-3" >> # Option "metamodes" "1920x1080 +0+0" >> # Option "metamodes" "1920x1080 +0+0; 1024x768_60 +0+0" > You can add back: > > Option "metamodes" "1920x1080_60 +0+0" > Well, I did a sync and upgrade last night.  I also renamed the config file so that it shouldn't be seen anymore.  That way when the new monitor arrives, I don't have a clash with it.  >> Basically, it is doing like it always has. Most of the time, it doesn't >> work. Sometimes it does. To be honest tho, I still wonder if it even >> reads the file. When I change something, I'd expect something >> different. Generally, it doesn't seem to affect anything unless I >> reboot completely. Sometimes I'm not sure it does then either. So, I >> think this old monitor just has a issue. Maybe I need to rebuild some >> more of the power supply or something in case it is providing bad power >> to the parts that talks to the puter. Either way, if the new one works, >> I just don't think this old monitor is going to work correctly no matter >> what we throw at it. > The last thing left to try is to capture the EDID table with nvidia-settings, > configure it to stop trying to load it from the monitor and instead feed the > captured file to it. If that doesn't work either, then there is no solution I > can think of ... > > >> I will saw this, we threw the kitchen sink at it. I think this is one >> of the longest threads I've seen in a long while. o_O >> >> Dale >> >> :-) >> >> P. S. Monitor updated. Now it says tomorrow. It's in the right place >> to do so. It's at the Memphis hub. Usually, it comes from there to the >> local distribution point and on the truck. They sometimes deliver by >> noon. Could be a little late given it is Monday. > Hopefully this won't be the start of a new loooooong thread on yet another > monitor! LOL! I hope it works like it should.  If it does, I may do some work on that old monitor.  Check the caps in the power supply and such as that.  I rebuilt it a few years ago but maybe I missed something.  I may have fixed it enough to come on, display part anyway, but not enough for everything, the ID part, to work correctly.  Right now, it still shows the new monitor at the hub around Memphis.  It is Monday and they do get their stuff local a little late. UPS gets theirs before sunup. They don't deliver until late tho, around 3 or 4PM.  Later around the holidays. It still shows delivery today.  It should update, eventually.  I should have proofed previous message more.  I saw some typos.  My supper was getting cold.  :/  I'll update later tho.  If it doesn't work, new thread.  This one is long enough already.  We sure did beat on it some tho.  I'm very confident in the boot up process given the number of reboots.  ROFL  I still wonder if it is reading that xorg.conf file tho.  It doesn't act like it at times. Dale :-)  :-)  --------------DF77AF38BD28B165A723C460 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Michael wrote:
On Sunday, 30 June 2024 23:56:40 BST Dale wrote:

Michael wrote:

This is good! :D
Edit the section below by adding the PreferredMode line:

Section "Monitor"

    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG Electronics W2253"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 61.0
    Option         "PreferredMode"   "1920x1080_60.00"
    Option         "DPMS"

EndSection

Save it, then check if you get a consistent result when you restart the
DM, or reboot.

If it is still playing up you need to show the Xorg.0.log while the
monitor is working with the nvidia driver, to see which Modeline it uses
and add this in the "Monitor" section too, above the "PreferredMode"
entry.

If none of this works reliably, then you have to capture the EDID table
while the monitor is working, save it in a file and set nvidia-settings
to use it hereafter.  However, if you will NOT be using this monitor for
much longer this would be an exercise only to make you feel good for
beating it into submission!  LOL!

OK.  First time, it worked.  Second time, it came up but in low res. 
Plasma was working to, both times.  So, I opened the Nvidia GUI and told
it to safe a new config with it in hi res mostly just to see what it
would add if anything.  It did.  The only change I could see was it
added metamodes options like this:

Section "Screen"

# Removed Option "metamodes" "nvidia-auto-select +0+0"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DP-3"
    Option         "metamodes" "1920x1080 +0+0"
#    Option         "metamodes" "1920x1080 +0+0; 1024x768_60 +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection


As you can see, I removed the low res part, don't want that anyway, and
it seems to work more often but still fails a lot.  So, I removed the
metamodes Nvidia added.  Then it didn't come up at all, sddm or
anything, when I restarted DM.  I thought it adding your setting to
another section might help.  Guess not.  With the following removed, it
seems to do a little better but still can't depend on it to work.

Section "Screen"
#    Option         "nvidiaXineramaInfoOrder" "DP-3"
#    Option         "metamodes" "1920x1080 +0+0"
#    Option         "metamodes" "1920x1080 +0+0; 1024x768_60 +0+0"

You can add back:

Option         "metamodes" "1920x1080_60 +0+0"

Well, I did a sync and upgrade last night.  I also renamed the config file so that it shouldn't be seen anymore.  That way when the new monitor arrives, I don't have a clash with it.  



        

          
Basically, it is doing like it always has.  Most of the time, it doesn't
work.  Sometimes it does.  To be honest tho, I still wonder if it even
reads the file.  When I change something, I'd expect something
different.  Generally, it doesn't seem to affect anything unless I
reboot completely.  Sometimes I'm not sure it does then either.  So, I
think this old monitor just has a issue.  Maybe I need to rebuild some
more of the power supply or something in case it is providing bad power
to the parts that talks to the puter.  Either way, if the new one works,
I just don't think this old monitor is going to work correctly no matter
what we throw at it. 


        

        
The last thing left to try is to capture the EDID table with nvidia-settings, 
configure it to stop trying to load it from the monitor and instead feed the 
captured file to it.  If that doesn't work either, then there is no solution I 
can think of ... 




        

          
I will saw this, we threw the kitchen sink at it.  I think this is one
of the longest threads I've seen in a long while.  o_O 

Dale

:-) 

P. S.  Monitor updated.  Now it says tomorrow.  It's in the right place
to do so.  It's at the Memphis hub.  Usually, it comes from there to the
local distribution point and on the truck.  They sometimes deliver by
noon.  Could be a little late given it is Monday. 


        

        
Hopefully this won't be the start of a new loooooong thread on yet another 
monitor!  LOL!


      

    

    

    

    I hope it works like it should.  If it does, I may do some work on
    that old monitor.  Check the caps in the power supply and such as
    that.  I rebuilt it a few years ago but maybe I missed something.  I
    may have fixed it enough to come on, display part anyway, but not
    enough for everything, the ID part, to work correctly.  

    

    Right now, it still shows the new monitor at the hub around
    Memphis.  It is Monday and they do get their stuff local a little
    late. UPS gets theirs before sunup. They don't deliver until late
    tho, around 3 or 4PM.  Later around the holidays. It still shows
    delivery today.  It should update, eventually.  

    

    I should have proofed previous message more.  I saw some typos.  My
    supper was getting cold.  :/  I'll update later tho.  If it doesn't
    work, new thread.  This one is long enough already.  We sure did
    beat on it some tho.  I'm very confident in the boot up process
    given the number of reboots.  ROFL  

    

    I still wonder if it is reading that xorg.conf file tho.  It doesn't
    act like it at times. 

    

    Dale 

    

    :-)  :-)  

  


--------------DF77AF38BD28B165A723C460--