On Thursday, 27 June 2024 07:54:43 BST Dale wrote: > Update. I played around a bit. I figured I didn't have a lot to lose > here. It either works, or it doesn't. After playing around a bit, I > got it to work. I have not restarted it to see if it will work again, > yet. I wanted to grab some log info first, while it is working. So, > this part is about when KDE comes up completely but could include some > attempts that failed. Comes up completely means, in the correct > resolution, background image and the panel thing on the bottom, which > means plasma is running as it should. I'm doing these inside the email > instead of as attachments. Sorry for the length. I just want to share > this while I have it available.
Your Display Manager (SDDM) works fine. There is no problem with the the DM. Your system log does not reveal anything untoward. The driver components are loading fine. No problem with this either. Your Xorg.0.log now shows a different port (DP-5) and the monitor bobs up & down. My money is on a buggy EDID. > [ 1236.810] (--) NVIDIA(GPU-0): > [ 1237.031] (--) NVIDIA(GPU-0): LG Electronics W2253 (DFP-5): connected > [ 1237.031] (--) NVIDIA(GPU-0): LG Electronics W2253 (DFP-5): Internal TMDS > [ 1237.031] (--) NVIDIA(GPU-0): LG Electronics W2253 (DFP-5): 300.0 MHz > maximum pixel clock [Snip ...] Are you still plugged into the same physical port on the video card? If yes, then its designation DFP-? is allocated dynamically. The monitor is shown to be disconnected a couple of times and eventually reconnected. Again on port DP-5. Normally this should be on port DP-0 if you have plugged it into the first port. > This is xorg.conf. At which point did you originally generate this file? While the monitor was on and running, or after it went sideways? > Gentoo-1 ~ # cat /etc/X11/xorg.conf > # nvidia-xconfig: X configuration file generated by nvidia-xconfig > # nvidia-xconfig: version 550.90.07 [Snip ...] > Section "Monitor" > Identifier "Monitor0" > VendorName "Unknown" > ModelName "Unknown" > Option "DPMS" > EndSection Regenerate the file while the monitor is working and check what/if its details come up in the above section. > #Section "Device" > # Identifier "Device0" > # Driver "nvidia" > # VendorName "NVIDIA Corporation" > #EndSection > > Section "Device" > > Identifier "Device0" > # Identifier "nvidia" > Driver "nvidia" > BusID "PCI:9:0:0" > Option "UseEDID" "false" ## Comment out this entry for now <== > > EndSection > > Section "Screen" > Identifier "Screen0" > Device "Device0" > Monitor "Monitor0" > DefaultDepth 24 > SubSection "Display" > Depth 24 > EndSubSection > EndSection > > Gentoo-1 ~ # > > > I took the info you sent and sort of combined it with what > nvidia-xconfig created. This is when it worked, this time anyway. > Other things I tried did nothing. Now that I have documented all this, > I'm going to reboot the rig and see if it works again. I think we > already have failed logs but will share what happens. Comment out the line: Option "UseEDID" "false" Let's see if the Monitor shows up in the recreated config file, otherwise you'll need to fill in its Model name and sync frequencies to take probing and guessing out of the equation. If this still doesn't work, then you should try to feed its EDID file to the card. > Given I get different results even with the same settings, I'm wondering > about that monitor. I've changed video cards so that should eliminate > that. The only common thing is the monitor. Thing is, that monitor > worked for a long time on my main rig, it also has worked fine on the > NAS box and the old Dell system as well. That was very recent I might > add. This new system is the only one that has issues with that monitor. Were the other PCs using the same DP cable, or HDMI/DVI? What xorg.conf files did they have generated? > The new monitor should give us clues. If it just works when it gets > here, then it is the monitor acting weird. If it does the same thing, > there is a config error somewhere. I can't think of anything else. I can think of a buggy monitor EDID. There are a lot of cheap monitors being churned out with average display panels, but bottom dollar chip, bezel and stand. Power saving features introduce their own bugs. You could check the monitor's own menu to disable eco modes and what not, if you keep your monitor running 24-7. > Open to ideas still. I'd like to get this working. If for no other > reason, the new monitor could have the same issue and require some > special settings somewhere. > > Thanks for all the help. Sorry to have so much info in one email. :/ > At least we have details of when it is working now tho. :-D The email line wrap makes things difficult to read. You can redirect the Xorg.0.log to a txt file and take it off the PC via SSH even if the monitor goes to sleep. Some other things to try, beyond finding DP-0 on the card and using it: - See what config files worked on the other PCs and compare them with what you are using now. - Unplug/replug the monitor. - Power down/up the monitor. - Use the monitor's OSD to reset it, or disable eco mode, or set it to standard resolution/frequency. Finally, see how the new monitor suits your needs and if it works as expected.
signature.asc
Description: This is a digitally signed message part.
