On 10/11/24 11:58 PM, Felix Miata wrote:
home user composed on 2024-10-11 22:36 (UTC-0600):
Samuel Sieb wrote:
Everything looks good. Try running "systemctl start gdm".
Entered it.
The screen blanked.
After about a minute, the graphical login screen appeared.
I was able to log in as root via the graphical login screen.
I shut the workstation down.
I booted the workstation up.
The console-only login appeared.
After logging in as root, I again entered your command and got the same behavior.
I logged in as a regular user.
There are still problems, but we've made an important step forward.
I believe what is happening to you often happens on several of my faster machines.
The following represents evidence of what happens here using KDM or TDM and Xorg/X11:
# egrep 'dev/dr\|Xorg.0.' /var/log/Xorg.0.*
/var/log/Xorg.0.log:[ 19.936] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 29 15:29:38 2024
/var/log/Xorg.0.log:[ 19.938] (II) xfree86: Adding drm device (/dev/dri/card1)
/var/log/Xorg.0.log:[ 19.974] (II) modeset(0): using drv /dev/dri/card1
/var/log/Xorg.0.log.old:[ 4.892] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 29 15:29:23 2024
/var/log/Xorg.0.log.old:[ 4.910] (EE) open /dev/dri/card0: No such file or directory
/var/log/Xorg.0.log.old:[ 4.910] (EE) open /dev/dri/card0: No such file or directory
/var/log/Xorg.0.log.old:[ 4.910] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
#
What this shows is that KMS had not yet succeeded to provide KMS services, so
/dev/dri/cardX did not yet exist, before the DM tried to start. After about
15 seconds, the DM tried again, and succeeded.
What I suspect is that on your system, GDM isn't configured to automatically
retry, so you get no GDM until you start it manually.
I've yet to determine how to ensure the DM doesn't try to start before KMS
has been made ready.
You may be able to get similar data as I get grepping Xorg.0.lo* by seeking
equivalent data from your journal.
Is this what you mean?...
-bash.1[~]: journalctl -b | grep Xorg.0.lo*
Oct 12 12:33:34 coyote /usr/libexec/gdm-x-session[1407]: (--) Log file renamed from "/var/lib/gdm/.local/share/xorg/Xorg.pid-1407.log" to "/var/lib/gdm/.local/share/xorg/Xorg.0.log"
Oct 12 12:33:34 coyote /usr/libexec/gdm-x-session[1407]: (==) Log file: "/var/lib/gdm/.local/share/xorg/Xorg.0.log", Time: Sat Oct 12 12:33:34 2024
-bash.2[~]:
Actually, I have been seeing multiple tries at the smae thing in logs and when watching a boot. I figured similar things - trying b before it's ready, and trying b again.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
