On 10/12/24 5:07 PM, home user via users wrote:
On 10/12/24 5:35 PM, Samuel Sieb wrote:
On 10/11/24 9:36 PM, home user via users wrote:
On 10/11/24 9:50 PM, Samuel Sieb wrote:
On 10/11/24 8:03 PM, home user via users wrote:
On 10/11/2024 7:50 PM, Samuel Sieb wrote:
[snip]
I assumed that force would make it compile again, but apparently
not. But anyway, the kernel modules should be available.
What do the following commands show:
cat /proc/cmdline
grep -rn nouveau /etc/modprobe.d/
lsmod | grep -i nouveau
lsmod | grep -i nvidia
cat /proc/cmdline
BOOT_IMAGE=(hd0,msdos3)/vmlinuz-6.10.12-200.fc40.x86_64
root=UUID=45e553d2-fa0c-4eae-95f6-7bf9086ab74c ro
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-
drm.modeset=1 rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=us
nouveau.modeset=0 video=vesa:on rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1
grep -rn nouveau /etc/modprobe.d/
(nothing)
lsmod | grep -i nouveau
(nothing)
lsmod | grep -i nvidia
nvidia_drm 81920 0
nvidia_modeset 1511424 1 nvidia_drm
nvidia_uvm 2805760 0
nvidia 40759296 2 nvidia_uvm,nvidia_modeset
video 81920 2 asus_wmi,nvidia_modeset
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.
What does "systemctl status gdm" show now? I have no idea how it got
disabled, but if it still is, then try "systemctl enable --now gdm".
It showed "disabled". I entered the command as suggested, the system
paused for about a minute, and then displayed the graphical login screen
(without logging me out). I lost the systemctl status gdm output before
I could capture it.
I shutdown and booted up.
It booted to the graphical console.
Now the suggested status command shows this:
-bash.3[~]: systemctl status gdm
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled;
preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Sat 2024-10-12 17:54:23 MDT; 4min
40s ago
Main PID: 1214 (gdm)
Tasks: 4 (limit: 19026)
Memory: 6.2M (peak: 9.0M)
CPU: 142ms
CGroup: /system.slice/gdm.service
└─1214 /usr/sbin/gdm
Oct 12 17:54:23 coyote systemd[1]: Starting gdm.service - GNOME Display
Manager...
Oct 12 17:54:23 coyote systemd[1]: Started gdm.service - GNOME Display
Manager.
Oct 12 17:54:24 coyote gdm[1214]: Gdm: on_display_added: assertion
'GDM_IS_REMOTE_DISPLAY (display)' failed
Oct 12 17:55:11 coyote gdm-password][1830]: gkr-pam: unable to locate
daemon control file
Oct 12 17:55:11 coyote gdm-password][1830]: gkr-pam: stashed password to
try later in open session
Oct 12 17:55:15 coyote gdm[1214]: Gdm: on_display_added: assertion
'GDM_IS_REMOTE_DISPLAY (display)' failed
Oct 12 17:55:32 coyote gdm[1214]: Gdm: Child process -1318 was already
dead.
Oct 12 17:55:32 coyote gdm[1214]: Gdm: on_display_removed: assertion
'GDM_IS_REMOTE_DISPLAY (display)' failed
-bash.4[~]:
This seems like another good step forward. But what are the 3 "failed"
lines and the "unable to locate" message? Problems or something I can
ignore?
That's expected. It's checking if it's displaying to a remote display
and that check is failing.
I think you're all good now.
--
_______________________________________________
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
