Dale wrote:
> Michael wrote:
>> On Friday, 21 June 2024 20:02:22 BST 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)
>> There are reports in the interwebs about LG monitors having buggy EDID
>> tables:
>>
>> https://gist.github.com/kj800x/be3001c07c49fdb36970633b0bc6defb
> Reading that link, mine doesn't behave that way. I see the services
> starting up during boot up just fine, small print but it's there, if I
> squint a bit. Also, the sddm login screen shows up just fine. I might
> add, this same monitor works just fine on the NAS box rig and the older
> Dell rig I have lurking about. It also worked fine on my main rig years
> ago before I bought a larger monitor. It is also the monitor I used on
> the TrueNAS system when I used it. It also works fine with Knoppix and
> the official Gentoo GUI DVD image. Basically, this monitor has never
> gave me any problems with any Linux based install until this new
> install. That's what confuses me.
>
>
>> What is connected at DP-1 and is the problem resolved if you change the port
>> you connect your monitor on the card?
>>
>> Do you get an EDID table shown in your Xorg.0.log, or with xrandr --verbose?
>>
>> Does your ~/.local/share/sddm/xorg-session.log reveal anything more?
>>
>
> I'll check those next time I'm able to spend some time with it. Right
> now, I'm picking basil to dehydrate and chop for later use. Basil
> smells so good too. Nice dark leaves. I have five trays of it from one
> planter. Now to pick planter two, if my back will allow it. My back is
> angry despite meds. :-@
OK. It got to hot and my back is beyond angry now. This is one of them.
root@Gentoo-1 ~ # xrandr --verbose
Can't open display
root@Gentoo-1 ~ #
That's after I started display-manager but this time, it did nothing.
The screen stayed on a console. I did move the cable to another port
before booting up.
This is the other info except nothing xorg there, just wayland. See
below for more on that.
root@Gentoo-1 ~ # cat /home/dale/.local/share/sddm/wayland-session.log
org.kde.startup: not a reply org.freedesktop.locale1
QDBusMessage(type=Error, service="org.freedesktop.DBus", error
name="org.freedesktop.DBus.Error.ServiceUnknown", error message="The
name org.freedesktop.locale1 was not provided by any .service files",
signature="s", contents=("The name org.freedesktop.locale1 was not
provided by any .service files") )
dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activating
service name='org.kde.KSplash' requested by ':1.0' (uid=1000 pid=2767
comm="/usr/bin/startplasma-wayland" label="kernel")
dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activating
service name='org.freedesktop.portal.Desktop' requested by ':1.4'
(uid=1000 pid=2780 comm="/usr/bin/ksplashqml" label="kernel")
dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activating
service name='org.freedesktop.portal.Documents' requested by ':1.5'
(uid=1000 pid=2787 comm="/usr/libexec/xdg-desktop-portal" label="kernel")
dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activating
service name='org.freedesktop.impl.portal.PermissionStore' requested by
':1.6' (uid=1000 pid=2793 comm="/usr/libexec/xdg-document-portal"
label="kernel")
kdeinit5: preparing to launch '/usr/lib64/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 2799, result = 0
dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Successfully
activated service 'org.freedesktop.impl.portal.PermissionStore'
dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Successfully
activated service 'org.freedesktop.portal.Documents'
fuse: device not found, try 'modprobe fuse' first
error: fuse init failed: Can't mount path /run/user/1000/doc
(/usr/libexec/xdg-desktop-portal:2787): xdg-desktop-portal-WARNING **:
03:20:14.139: Failed to load RealtimeKit property:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.RealtimeKit1 was not provided by any .service files
(/usr/libexec/xdg-desktop-portal:2787): xdg-desktop-portal-WARNING **:
03:20:14.139: Failed to load RealtimeKit property:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.RealtimeKit1 was not provided by any .service files
(/usr/libexec/xdg-desktop-portal:2787): xdg-desktop-portal-WARNING **:
03:20:14.140: Failed to load RealtimeKit property:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.RealtimeKit1 was not provided by any .service files
dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activating
service name='org.freedesktop.impl.portal.desktop.kde' requested by
':1.5' (uid=1000 pid=2787 comm="/usr/libexec/xdg-desktop-portal"
label="kernel")
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
No backend specified, automatically choosing drm
kwin_wayland_drm: No suitable DRM devices have been found
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
The Wayland connection broke. Did the Wayland compositor die?
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activated service
'org.freedesktop.impl.portal.desktop.kde' failed: Process
org.freedesktop.impl.portal.desktop.kde exited with status 1
(/usr/libexec/xdg-desktop-portal:2787): xdg-desktop-portal-WARNING **:
03:20:14.512: Failed to create settings proxy: Error calling
StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Process
org.freedesktop.impl.portal.desktop.kde exited with status 1
(/usr/libexec/xdg-desktop-portal:2787): xdg-desktop-portal-WARNING **:
03:20:14.512: No skeleton to export
kdeinit5: Communication error with launcher. Exiting!
dbus-daemon[2766]: [session uid=1000 pid=2766 pidfd=5] Activating
service name='org.freedesktop.impl.portal.desktop.kde' requested by
':1.5' (uid=1000 pid=2787 comm="/usr/libexec/xdg-desktop-portal"
label="kernel")
Error: could not determine $DISPLAY.
Error: Can not contact kdeinit5!
org.kde.startup: "kdeinit5_shutdown" () exited with code 255
startplasma-wayland: Shutting down...
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
root@Gentoo-1 ~ #
Since it complains about DRM. Here's this.
root@Gentoo-1 ~ # lsmod
Module Size Used by
nvidia_drm 102400 0
nvidia_modeset 1544192 1 nvidia_drm
nvidia 59744256 1 nvidia_modeset
root@Gentoo-1 ~ #
What's that about fuse???
>
>>> 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
>>>
>>> :-) :-)
>> If this is a buggy EDID, or monitor chip, you should be able to extract the
>> EDID table and store it as a firmware blob for the video card to load.
>
> I may try to boot the Gentoo GUI DVD and see what entries it has for X
> config files. Do you know what files I should look for or is it the
> same for that as a hard drive based install? I know to check /etc/X11/*
> but could be others I'm not aware of.
>
> Back to picking basil. No zucchini today.
>
> Thanks. I'm not sure what the problem is but it is annoying me. :/
>
> Dale
>
> :-) :-)
>
To add to this, this is a new video card. It's a P1000, Nvidia of
course. Could it be a bad card that works to a point but then dies? I
got a older PCIe V2 card I'm going to try. That was the card that was
in during the early stages. The P1000 was the one that got hung up by
the post office and arrived days late. I'm going to test the other
slower card shortly, got to remember to downgrade nvidia-drivers to
tho. ;-)
On the above wayland info, I recall some having issues with wayland. I
tried to disable wayland by putting -wayland in make.conf and
rebuilding. Since it wanted to rebuild a lot, I removed everything GUI
related from the world file and then ran --depclean to clean house.
Then I emerge everything I removed from the world file again, while I
napped. The output above could be old but may still provide a clue. If
I could figure out how to go back to KDE V5 instead of the new V6, I
would, to eliminate a wayland issue if nothing else. I removed
everything from /etc/portage/package.keyword file but I think KDE V6 is
stable now. The odd part, right now, even sddm isn't coming up.
I ended up with 8 trays of basil. I'll got at least one more picking
from each planter plus I have another planter that will be ready to pick
in a few weeks. Me and my garden. LOL
Dale
:-) :-)
