Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing
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. This first one, I had a few failures before it succeeded. I couldn't figure out when the working bit started so it is the complete log. Gentoo-1 ~ # cat /var/log/Xorg.0.log [ 1236.678] (--) Log file renamed from "/var/log/Xorg.pid-3720.log" to "/var/log/Xorg.0.log" [ 1236.678] X.Org X Server 1.21.1.13 X Protocol Version 11, Revision 0 [ 1236.678] Current Operating System: Linux Gentoo-1 6.9.4-gentoo #11 SMP PREEMPT_DYNAMIC Sat Jun 22 18:45:21 CDT 2024 x86_64 [ 1236.678] Kernel command line: BOOT_IMAGE=/kernel-6.9.4-6 root=UUID=26e58ee4-9c8f-4efd-bbb3-215df71cf85e ro [ 1236.678] [ 1236.678] Current version of pixman: 0.43.4 [ 1236.678] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 1236.678] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1236.678] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun 27 00:50:03 2024 [ 1236.678] (==) Using config file: "/etc/X11/xorg.conf" [ 1236.678] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 1236.678] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 1236.678] (==) ServerLayout "Layout0" [ 1236.678] (**) |-->Screen "Screen0" (0) [ 1236.678] (**) | |-->Monitor "Monitor0" [ 1236.678] (**) | |-->Device "Device0" [ 1236.678] (**) | |-->GPUDevice "nvidia" [ 1236.678] (**) | |-->GPUDevice "Device0" [ 1236.678] (**) |-->Input Device "Keyboard0" [ 1236.678] (**) |-->Input Device "Mouse0" [ 1236.678] (**) Allowing byte-swapped clients [ 1236.678] (==) Automatically adding devices [ 1236.678] (==) Automatically enabling devices [ 1236.678] (==) Automatically adding GPU devices [ 1236.678] (==) Automatically binding GPU devices [ 1236.678] (==) Max clients allowed: 256, resource mask: 0x1f [ 1236.678] (WW) The directory "/usr/share/fonts/OTF" does not exist. [ 1236.678] Entry deleted from font path. [ 1236.678] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi". [ 1236.678] Entry deleted from font path. [ 1236.678] (Run 'mkfontdir' on "/usr/share/fonts/75dpi"). [ 1236.678] (==) FontPath set to: /usr/share/fonts/misc, /usr/share/fonts/TTF, /usr/share/fonts/Type1, /usr/share/fonts/100dpi [ 1236.678] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 1236.678] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. [ 1236.678] (WW) Disabling Keyboard0 [ 1236.678] (WW) Disabling Mouse0 [ 1236.678] (II) Module ABI versions: [ 1236.678] X.Org ANSI C Emulation: 0.4 [ 1236.678] X.Org Video Driver: 25.2 [ 1236.678] X.Org XInput driver : 24.4 [ 1236.678] X.Org Server Extension : 10.0 [ 1236.678] (++) using VT number 8 [ 1236.678] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 1236.679] (II) xfree86: Adding drm device (/dev/dri/card0) [ 1236.679] (II) Platform probe for /sys/devices/pci:00/:00:03.1/:09:00.0/drm/card0 [ 1236.799] (--) PCI:*(9@0:0:0) 10de:1cb1:10de:11bc rev 161, Mem @ 0xfb00/16777216, 0xd000/268435456, 0xe000/33554432, I/O @ 0xe000/128, BIOS @ 0x/524288 [ 1236.799] (II) LoadModule: "glx" [ 1236.799] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 1236.800] (II) Module glx: vendor="X.Org Foundation" [ 1236.800] compiled for 1.21.1.13, module version = 1.0.0 [ 1236.800] ABI class: X.Org Server Extension, version 10.0 [ 1236.800] (II) LoadModule: "nvidia" [ 1236.800] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 1236.800] (II) Module nvidia: vendor="NVIDIA Corporation" [ 1236.800] compiled for 1.6.99.901, module version = 1.0.0 [ 1236.800] Module class: X.Org Video Driver [ 1236.800] (II) NVIDIA dlloader X Driver 550.90.07 Fri May 31 09:34:34 UTC 2024 [ 1236.800] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 1236.803] (II) Loading sub module "fb" [ 1236.803] (II) LoadModule: "fb" [ 1236.803] (II) Module "fb" already built-in [ 1236.803] (II) Loading sub module "wfb" [ 1236.803] (II) LoadModule: "wfb" [ 1236.803] (II) Loading /usr/lib64/xorg/m
Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing
Update. I ordered a monitor. It's bigger than the one I have now. I'd still like to get this one working if you have ideas. May help someone else, we may learn something, you most likely will remember it. LOL My plan, get new monitor working with new rig. When I switch current rig to new rig, monitor moves over with it too. This way, the working monitors stay with the rig they work with. I need a larger monitor and a extra monitor anyway. May give me that second monitor I mentioned earlier too. Monitor is a Samsung LS32B304NWN. I'm pretty sure it is better than my current monitor in most respects. I don't game or anything anyway. On other reply, if you have ideas, I'll try them. Oh, sorry for late reply. My sis-n-law was supposed to have surgery. She's been sick a while and was to dehydrated to have it since they been dragging their feet. Spent over half the day to accomplish nothing. Wore me out. Ebay claims it should be here by next Tuesday. Could be earlier but it does have a ways to go. Dale :-) :-)
Re: [gentoo-user] Can't get the GUI to stay up for more than a minute or so before crashing
Well, I spoke to soon. I shutdown for a while. When I rebooted, to get the logs you wanted, it started cutting off again like it did before. It seems it worked that one time but it just wanted to tease me. :/ Michael wrote: > 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 tried all those in different ways. Basically, same thing. The last one did flash me just long enough to see the sddm login screen was low resolution. > >> 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 noticed that too. I was curious why it was saying disconnected when I didn't. >> 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 did try another port, just not all of them. I figured one port may be bad. Surely not more than one tho. Plus, another card did the same thing. >> 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 > NO!! O_O >> 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 > *al
Re: [gentoo-user] SOLVED Can't get the GUI to stay up for more than a minute or so before crashing
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
