Until FC39, I had only run Wayland on one of my machines, not even trying to bring it up on the others. Since I intensely dislike the graphic login, I found a way to start it from a virtual terminal like I normally start X11. Instead of "startx", I have a short script I call "startw" that contains only the single line, "/usr/bin/dbus-run-session /usr/bin/startplasma-wayland". (Yes, I run KDE.) This worked on FC38.
Now on the same machine with FC39 (upgraded with system-upgrade) this no longer works. Instead, it produces 248 lines of output and then terminates. Reviewing those lines, it appears that it is complaining about, 'failed to open drm device at "/dev/dri/card0"' and 'No suitable DRM devices have been found'. I'm not sure what device that refers to but there seems to be some indication that it is my display. The display certainly works fine for the virtual terminal I use to run this script, and it also works fine for X11 if I run "startx".
Ok, so as a fallback I tried a graphic login. This reaches a completely blank screen and goes no further. The machine is up as I can reach it with SSH but the display is useless. It responds to Ctrl-Alt-Delete but nothing else. I can't get it to switch to a different desktop. I noticed that SDDM defaults to Wayland so I changed "sddm.conf" to include "DisplayServer=x11". The allowed the graphic login to reach a login page but nothing I entered there was accepted even when I switched to specify starting an X11 session instead of Wayland.
There are some online references to a problem with the /dev/dri/card0 device but they are ancient and don't seem relevant.
This machine is intended to run an application that only works on Wayland (Waydroid) so at this point I'm stimied. Any suggestions would be very helpful.
I wrote:
Until FC39, I had only run Wayland on one of my machines, not even trying to bring it up on the others. Since I intensely dislike the graphic login, I found a way to start it from a virtual terminal like I normally start X11. Instead of "startx", I have a short script I call "startw" that contains only the single line, "/usr/bin/dbus-run-session /usr/bin/startplasma-wayland". (Yes, I run KDE.) This worked on FC38.
Now on the same machine with FC39 (upgraded with system-upgrade) this no longer works. Instead, it produces 248 lines of output and then terminates. Reviewing those lines, it appears that it is complaining about, 'failed to open drm device at "/dev/dri/card0"' and 'No suitable DRM devices have been found'. I'm not sure what device that refers to but there seems to be some indication that it is my display. The display certainly works fine for the virtual terminal I use to run this script, and it also works fine for X11 if I run "startx".
Ok, so as a fallback I tried a graphic login. This reaches a completely blank screen and goes no further. The machine is up as I can reach it with SSH but the display is useless. It responds to Ctrl-Alt-Delete but nothing else. I can't get it to switch to a different desktop. I noticed that SDDM defaults to Wayland so I changed "sddm.conf" to include "DisplayServer=x11". The allowed the graphic login to reach a login page but nothing I entered there was accepted even when I switched to specify starting an X11 session instead of Wayland.
There are some online references to a problem with the /dev/dri/card0 device but they are ancient and don't seem relevant.
This machine is intended to run an application that only works on Wayland (Waydroid) so at this point I'm stimied. Any suggestions would be very helpful.
If it matters, this machine was never installed with the KDE spin. It was installed before spins and with extensive editing of the packages to be included. KDE was added to it. It's been working through several Fedora releases for at least three years.
On Fri, 17 Nov 2023 19:44:49 -0800 Dave Close dave@compata.com wrote:
I wrote:
Until FC39, I had only run Wayland on one of my machines, not even trying to bring it up on the others. Since I intensely dislike the graphic login, I found a way to start it from a virtual terminal like I normally start X11. Instead of "startx", I have a short script I call "startw" that contains only the single line, "/usr/bin/dbus-run-session /usr/bin/startplasma-wayland". (Yes, I run KDE.) This worked on FC38.
Now on the same machine with FC39 (upgraded with system-upgrade) this no longer works. Instead, it produces 248 lines of output and then terminates. Reviewing those lines, it appears that it is complaining about, 'failed to open drm device at "/dev/dri/card0"' and 'No suitable DRM devices have been found'. I'm not sure what device that refers to but there seems to be some indication that it is my display. The display certainly works fine for the virtual terminal I use to run this script, and it also works fine for X11 if I run "startx".
Have you tried creating a new user? I'm wondering if there is some cruft in your configuration that a newer version of the executable is choking on. I don't see any bugzillas open against the package plasma-workspace that creates that rpm, so it doesn't seem to be a widespread problem.
I wrote:
Until FC39, I had only run Wayland on one of my machines, not even trying to bring it up on the others. Since I intensely dislike the graphic login, I found a way to start it from a virtual terminal like I normally start X11. Instead of "startx", I have a short script I call "startw" that contains only the single line, "/usr/bin/dbus-run-session /usr/bin/startplasma-wayland". (Yes, I run KDE.) This worked on FC38.
Now on the same machine with FC39 (upgraded with system-upgrade) this no longer works. Instead, it produces 248 lines of output and then terminates. Reviewing those lines, it appears that it is complaining about, 'failed to open drm device at "/dev/dri/card0"' and 'No suitable DRM devices have been found'. I'm not sure what device that refers to but there seems to be some indication that it is my display. The display certainly works fine for the virtual terminal I use to run this script, and it also works fine for X11 if I run "startx".
Ok, so as a fallback I tried a graphic login. This reaches a completely blank screen and goes no further. The machine is up as I can reach it with SSH but the display is useless. It responds to Ctrl-Alt-Delete but nothing else. I can't get it to switch to a different desktop. I noticed that SDDM defaults to Wayland so I changed "sddm.conf" to include "DisplayServer=x11". The allowed the graphic login to reach a login page but nothing I entered there was accepted even when I switched to specify starting an X11 session instead of Wayland.
There are some online references to a problem with the /dev/dri/card0 device but they are ancient and don't seem relevant.
This machine is intended to run an application that only works on Wayland (Waydroid) so at this point I'm stimied. Any suggestions would be very helpful.
If it matters, this machine was never installed with the KDE spin. It was installed before spins and with extensive editing of the packages to be included. KDE was added to it. It's been working through several Fedora releases for at least three years.
stan via users wrote:
Have you tried creating a new user? I'm wondering if there is some cruft in your configuration that a newer version of the executable is choking on. I don't see any bugzillas open against the package plasma-workspace that creates that rpm, so it doesn't seem to be a widespread problem.
I created a new user and obtained the same result using "startw".
I agree that this is not likely a plasma problem. It's the reference to /dev/dri/card0 that concerns me. There must be some reason why this device is needed but can't be found.
For what it may be worth, I'll attach the complete output (if that is accepted on this list). Note that no other compositor is running as this is immediately after a fresh reboot.
I wrote:
Until FC39, I had only run Wayland on one of my machines, not even trying to bring it up on the others. Since I intensely dislike the graphic login, I found a way to start it from a virtual terminal like I normally start X11. Instead of "startx", I have a short script I call "startw" that contains only the single line, "/usr/bin/dbus-run-session /usr/bin/startplasma-wayland". (Yes, I run KDE.) This worked on FC38.
Now on the same machine with FC39 (upgraded with system-upgrade) this no longer works. Instead, it produces 248 lines of output and then terminates. Reviewing those lines, it appears that it is complaining about, 'failed to open drm device at "/dev/dri/card0"' and 'No suitable DRM devices have been found'. I'm not sure what device that refers to but there seems to be some indication that it is my display. The display certainly works fine for the virtual terminal I use to run this script, and it also works fine for X11 if I run "startx".
Ok, so as a fallback I tried a graphic login. This reaches a completely blank screen and goes no further. The machine is up as I can reach it with SSH but the display is useless. It responds to Ctrl-Alt-Delete but nothing else. I can't get it to switch to a different desktop. I noticed that SDDM defaults to Wayland so I changed "sddm.conf" to include "DisplayServer=x11". The allowed the graphic login to reach a login page but nothing I entered there was accepted even when I switched to specify starting an X11 session instead of Wayland.
There are some online references to a problem with the /dev/dri/card0 device but they are ancient and don't seem relevant.
This machine is intended to run an application that only works on Wayland (Waydroid) so at this point I'm stimied. Any suggestions would be very helpful.
After much searching, checking alternate users, verifying permissions, etc, I determined I was unlikely to find the problem. I took the coward's way out and downgraded the machine to FC38. After that, the problem is gone!
I'll leave it at FC38 for a while while watching for any online comments that might provide a clue to a real solution.
On Tue, Nov 21, 2023 at 10:17 PM Dave Close dave@compata.com wrote:
Until FC39, I had only run Wayland on one of my machines, not even trying to bring it up on the others. Since I intensely dislike the graphic login, I found a way to start it from a virtual terminal like I normally start X11. Instead of "startx", I have a short script I call "startw" that contains only the single line, "/usr/bin/dbus-run-session /usr/bin/startplasma-wayland". (Yes, I run KDE.) This worked on FC38.
Now on the same machine with FC39 (upgraded with system-upgrade) this no longer works. Instead, it produces 248 lines of output and then terminates. Reviewing those lines, it appears that it is complaining about, 'failed to open drm device at "/dev/dri/card0"' and 'No suitable DRM devices have been found'. I'm not sure what device that refers to but there seems to be some indication that it is my display. The display certainly works fine for the virtual terminal I use to run this script, and it also works fine for X11 if I run "startx".
Ok, so as a fallback I tried a graphic login. This reaches a completely blank screen and goes no further. The machine is up as I can reach it with SSH but the display is useless. It responds to Ctrl-Alt-Delete but nothing else. I can't get it to switch to a different desktop. I noticed that SDDM defaults to Wayland so I changed "sddm.conf" to include "DisplayServer=x11". The allowed the graphic login to reach a login page but nothing I entered there was accepted even when I switched to specify starting an X11 session instead of Wayland.
There are some online references to a problem with the /dev/dri/card0 device but they are ancient and don't seem relevant.
This machine is intended to run an application that only works on Wayland (Waydroid) so at this point I'm stimied. Any suggestions would be very helpful.
After much searching, checking alternate users, verifying permissions, etc, I determined I was unlikely to find the problem. I took the coward's way out and downgraded the machine to FC38. After that, the problem is gone!
I'll leave it at FC38 for a while while watching for any online comments that might provide a clue to a real solution.
Lol... +1.
Save your strength and fight another day!
-
Dave Close -
Jeffrey Walton -
stan