View previous topic :: View next topic |
Author |
Message |
ultimeight n00b
Joined: 09 Apr 2023 Posts: 60
|
Posted: Sun May 05, 2024 2:41 am Post subject: SDDM Not Working |
|
|
After setting up KDE and sddm according to the wiki, I'm redirected to tty login instead of sddm upon startup. I've tried enabling DRM as suggested in the troubleshooting section of sddm's Gentoo wiki page and added the following to /etc/modules-load.d/nvidia-drm.conf:
Code: | nvidia-drm
options nvidia-drm modeset=1
|
Thank you. _________________ Regards,
ultimeight. |
|
Back to top |
|
|
kgdrenefort Guru
Joined: 19 Sep 2023 Posts: 314 Location: Somewhere in the 77
|
Posted: Sun May 05, 2024 6:50 am Post subject: Re: SDDM Not Working |
|
|
ultimeight wrote: | After setting up KDE and sddm according to the wiki, I'm redirected to tty login instead of sddm upon startup. I've tried enabling DRM as suggested in the troubleshooting section of sddm's Gentoo wiki page and added the following to /etc/modules-load.d/nvidia-drm.conf:
Code: | nvidia-drm
options nvidia-drm modeset=1
|
Thank you. |
Hello,
First things first, is the sddm service enabled at boot ? We miss a lot of informations too:
1/ What profile are you using ?
Code: | eselect profile list | grep "*" |
(will display the line with your selected profile)
2/ Did you enabled the systemd or openrc service ?
3/ Could you paste us your make.conf please ? As you emerge --info, maybe too:
Code: | wgetpaste /etc/portage/make.conf && wgetpaste -c "emerge --info" |
4/ Are you using X, or Wayland ?
5/ If X, does this works in TTY without SDDM ?
Code: | exec dbus-launch --exit-with-session startplasma-x11 |
Or for Wayland:
Code: | dbus-launch --exit-with-session startplasma-wayland |
Source: https://wiki.gentoo.org/wiki/KDE#Starting_Plasma
Regards,
GASPARD DE RENEFORT Kévin _________________ Traduction wiki, pour praticiper.
Custom logos/biz card/website. |
|
Back to top |
|
|
ultimeight n00b
Joined: 09 Apr 2023 Posts: 60
|
Posted: Sun May 05, 2024 11:40 am Post subject: |
|
|
Hello, display-manager is installed in the boot runlevel.
1) default/linux/amd64/23.0/desktop/plasma (stable) is the profile that I am using.
2) yes I have enabled the openrc service.
3) make.conf: https://0x0.st/XXDl.conf and emerge info: https://0x0.st/XXDI.info
4) I am using X.
5) After running the command for X, I am being sent to TTY login again.
Thank you and apologies for the lack of information, please let me know if you need anything else. _________________ Regards,
ultimeight. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5256 Location: Bavaria
|
|
Back to top |
|
|
ultimeight n00b
Joined: 09 Apr 2023 Posts: 60
|
Posted: Sun May 05, 2024 3:40 pm Post subject: |
|
|
pietinger wrote: | ultimeight wrote: | Hello, display-manager is installed in the boot runlevel. |
Thats is wrong (too soon). display-manager must be in runlevel "default".
See also: https://wiki.gentoo.org/wiki/SDDM#OpenRC |
I had it in the default runlevel initially, but changing that did nothing. _________________ Regards,
ultimeight. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5256 Location: Bavaria
|
|
Back to top |
|
|
ultimeight n00b
Joined: 09 Apr 2023 Posts: 60
|
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5256 Location: Bavaria
|
|
Back to top |
|
|
ultimeight n00b
Joined: 09 Apr 2023 Posts: 60
|
Posted: Sun May 05, 2024 6:13 pm Post subject: |
|
|
Haven't done anything like that, there is no .xinitrc on my system. Although I added just the DRM config as I mentioned before. _________________ Regards,
ultimeight. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5256 Location: Bavaria
|
Posted: Sun May 05, 2024 8:57 pm Post subject: |
|
|
Soemthing is wrong ... ... you use VT1 instead of VT2 (*) ... Can you describe what you have installed and configured ? Do you try to start sddm manually ?
We would need also the output of "rc-update" and the content of /etc/conf.d/display-manager
*) Example of a correct start of sddm:
Code: | [16:36:16.977] (II) DAEMON: Initializing...
[16:36:16.981] (II) DAEMON: Starting...
[16:36:16.981] (II) DAEMON: Logind interface found
[16:36:16.981] (II) DAEMON: Adding new display...
[16:36:16.981] (II) DAEMON: Loaded empty theme configuration
[16:36:16.982] (II) DAEMON: Xauthority path: "/run/sddm/xauth_QQmGTk"
[16:36:16.982] (II) DAEMON: Using VT 2
[16:36:16.982] (II) DAEMON: Display server starting...
[16:36:16.982] (II) DAEMON: Writing cookie to "/run/sddm/xauth_QQmGTk"
[16:36:16.982] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_QQmGTk -noreset -displayfd 16
[16:36:18.015] (II) DAEMON: Setting default cursor
[16:36:18.105] (II) DAEMON: Running display setup script "/usr/share/sddm/scripts/Xsetup"
[16:36:18.110] (II) DAEMON: Display server started.
[16:36:18.110] (II) DAEMON: Socket server starting...
[16:36:18.110] (II) DAEMON: Socket server started.
[16:36:18.112] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[16:36:18.113] (II) DAEMON: Greeter starting...
[16:36:18.125] (II) HELPER: [PAM] Starting...
[16:36:18.125] (II) HELPER: [PAM] Authenticating...
[16:36:18.125] (II) HELPER: [PAM] returning.
[16:36:18.144] (II) HELPER: Writing cookie to "/tmp/xauth_aIeMUe"
[16:36:18.144] (II) HELPER: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-OPiaXP --theme /usr/share/sddm/themes/breeze"
[16:36:18.147] (II) DAEMON: Greeter session started successfully
[16:36:18.220] (II) DAEMON: Message received from greeter: Connect
[16:36:40.079] (II) DAEMON: Message received from greeter: Login
[16:36:40.080] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[16:36:40.082] (II) DAEMON: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11" for VT 2
[16:36:40.101] (II) HELPER: [PAM] Starting...
[16:36:40.101] (II) HELPER: [PAM] Authenticating...
[16:36:40.101] (II) HELPER: [PAM] Preparing to converse...
[16:36:40.101] (II) HELPER: [PAM] Conversation with 1 messages
[16:36:40.108] (II) HELPER: [PAM] returning.
[16:36:40.109] (II) DAEMON: Authentication for user "peter" successful
[16:36:40.169] (II) HELPER: Writing cookie to "/tmp/xauth_kXftjG"
[16:36:40.169] (II) HELPER: Starting X11 session: "" "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
[16:36:40.170] (II) DAEMON: Session started true
[16:36:40.188] (II) HELPER: [PAM] Closing session
[16:36:40.188] (II) HELPER: [PAM] Ended.
[16:36:40.188] (II) DAEMON: Auth: sddm-helper exited successfully
[16:36:40.188] (II) DAEMON: Greeter stopped. SDDM::Auth::HELPER_SUCCESS |
_________________ https://wiki.gentoo.org/wiki/User:Pietinger |
|
Back to top |
|
|
ultimeight n00b
Joined: 09 Apr 2023 Posts: 60
|
Posted: Sun May 05, 2024 10:11 pm Post subject: |
|
|
pietinger wrote: | Soemthing is wrong ... ... you use VT1 instead of VT2 (*) ... Can you describe what you have installed and configured ? Do you try to start sddm manually ?
We would need also the output of "rc-update" and the content of /etc/conf.d/display-manager
*) Example of a correct start of sddm:
Code: | [16:36:16.977] (II) DAEMON: Initializing...
[16:36:16.981] (II) DAEMON: Starting...
[16:36:16.981] (II) DAEMON: Logind interface found
[16:36:16.981] (II) DAEMON: Adding new display...
[16:36:16.981] (II) DAEMON: Loaded empty theme configuration
[16:36:16.982] (II) DAEMON: Xauthority path: "/run/sddm/xauth_QQmGTk"
[16:36:16.982] (II) DAEMON: Using VT 2
[16:36:16.982] (II) DAEMON: Display server starting...
[16:36:16.982] (II) DAEMON: Writing cookie to "/run/sddm/xauth_QQmGTk"
[16:36:16.982] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_QQmGTk -noreset -displayfd 16
[16:36:18.015] (II) DAEMON: Setting default cursor
[16:36:18.105] (II) DAEMON: Running display setup script "/usr/share/sddm/scripts/Xsetup"
[16:36:18.110] (II) DAEMON: Display server started.
[16:36:18.110] (II) DAEMON: Socket server starting...
[16:36:18.110] (II) DAEMON: Socket server started.
[16:36:18.112] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[16:36:18.113] (II) DAEMON: Greeter starting...
[16:36:18.125] (II) HELPER: [PAM] Starting...
[16:36:18.125] (II) HELPER: [PAM] Authenticating...
[16:36:18.125] (II) HELPER: [PAM] returning.
[16:36:18.144] (II) HELPER: Writing cookie to "/tmp/xauth_aIeMUe"
[16:36:18.144] (II) HELPER: Starting X11 session: "" "/usr/bin/sddm-greeter --socket /tmp/sddm-:0-OPiaXP --theme /usr/share/sddm/themes/breeze"
[16:36:18.147] (II) DAEMON: Greeter session started successfully
[16:36:18.220] (II) DAEMON: Message received from greeter: Connect
[16:36:40.079] (II) DAEMON: Message received from greeter: Login
[16:36:40.080] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[16:36:40.082] (II) DAEMON: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11" for VT 2
[16:36:40.101] (II) HELPER: [PAM] Starting...
[16:36:40.101] (II) HELPER: [PAM] Authenticating...
[16:36:40.101] (II) HELPER: [PAM] Preparing to converse...
[16:36:40.101] (II) HELPER: [PAM] Conversation with 1 messages
[16:36:40.108] (II) HELPER: [PAM] returning.
[16:36:40.109] (II) DAEMON: Authentication for user "peter" successful
[16:36:40.169] (II) HELPER: Writing cookie to "/tmp/xauth_kXftjG"
[16:36:40.169] (II) HELPER: Starting X11 session: "" "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
[16:36:40.170] (II) DAEMON: Session started true
[16:36:40.188] (II) HELPER: [PAM] Closing session
[16:36:40.188] (II) HELPER: [PAM] Ended.
[16:36:40.188] (II) DAEMON: Auth: sddm-helper exited successfully
[16:36:40.188] (II) DAEMON: Greeter stopped. SDDM::Auth::HELPER_SUCCESS |
|
I did not divert from the wiki at all during the installation, did everything by the wiki, not sure what's going wrong here.
https://bpa.st/PBSA
https://bpa.st/WPXA _________________ Regards,
ultimeight. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5256 Location: Bavaria
|
Posted: Mon May 06, 2024 12:17 am Post subject: |
|
|
ultimeight ,
please help us to help you ... we need as much information as possible ... please answer also every question ...
Please do a reboot and describe exactly what happens on your screen. Please do as few as possible interactions yourself.
IF you must to do any user input, tell us exactly what (and where) you type in (even a keystroke like ESC).
Are you able to reach the terminal ? (ALT+F1 or CTRL+ALT+F1) OR do you end up in the terminal ?
If you are now in the terminal please give us the complete output of "dmesg" and (again) the (new) sddm.log and xorg.log.
Then we need also the output of "emerge -pvD xorg-server plasma-meta" _________________ https://wiki.gentoo.org/wiki/User:Pietinger |
|
Back to top |
|
|
ultimeight n00b
Joined: 09 Apr 2023 Posts: 60
|
Posted: Mon May 06, 2024 9:48 am Post subject: |
|
|
pietinger wrote: | ultimeight ,
please help us to help you ... we need as much information as possible ... please answer also every question ...
Please do a reboot and describe exactly what happens on your screen. Please do as few as possible interactions yourself.
IF you must to do any user input, tell us exactly what (and where) you type in (even a keystroke like ESC).
Are you able to reach the terminal ? (ALT+F1 or CTRL+ALT+F1) OR do you end up in the terminal ?
If you are now in the terminal please give us the complete output of "dmesg" and (again) the (new) sddm.log and xorg.log.
Then we need also the output of "emerge -pvD xorg-server plasma-meta" |
Here's the entire process:
After I press the power-on key on my laptop, I get the Grub menu after a few seconds. Then, I don't hit enter, just let the 6 seconds go by. After that, I see the OpenRC messages go by, and then I am at the tty login.
However, there is a peculiar behavior about the login. I begin to type my username, 'root' in this case. As soon as I press 'r', nothing gets typed in after that. The cursor keeps blinking, and after a few seconds, a new login prompt shows up just below that, like an unsuccessful login attempt. Then, I log in. This one allows me to type everything out, and then I am into the system. Below are the requested logs.
https://bpa.st/UZNQ
https://bpa.st/442Q
https://bpa.st/5WBA
https://bpa.st/V2PA _________________ Regards,
ultimeight. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5256 Location: Bavaria
|
Posted: Mon May 06, 2024 11:37 am Post subject: |
|
|
What happens if you delete dbus (because it is not necessary) from runlevel "default" and do a reboot ? ->
Code: | # rc-update del dbus default |
Do you have then the same situation ? _________________ https://wiki.gentoo.org/wiki/User:Pietinger |
|
Back to top |
|
|
ultimeight n00b
Joined: 09 Apr 2023 Posts: 60
|
Posted: Mon May 06, 2024 12:56 pm Post subject: |
|
|
pietinger wrote: | What happens if you delete dbus (because it is not necessary) from runlevel "default" and do a reboot ? ->
Code: | # rc-update del dbus default |
Do you have then the same situation ? |
Nothing's changed, same situation. _________________ Regards,
ultimeight. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5256 Location: Bavaria
|
Posted: Mon May 06, 2024 2:16 pm Post subject: |
|
|
This is very strange ... because ... you have/use:
1. Our Gentoo dist-kernel (which has all necessary modules; it works out of the box)
2. All necessary run-scripts in the correct runlevels
3. Corrrect setting of PLASMA profile
4. No error messages in dmesg
5. No error message when booting for rc-scripts
... my last advice would be: Please check if/where you have deviated from these steps:
( a) https://wiki.gentoo.org/wiki/User:Pietinger/Draft/Quick_Installation_OpenRC_for_an_UEFI_System )
+
b) ->
Code: | # emerge -vD xorg-server
# emerge -vD plasma-meta kdecore-meta
# rc-update add elogind boot
# rc-update add display-manager default
# nano -w /etc/conf.d/display-manager
=> DISPLAYMANAGER="sddm"
# reboot |
(because these steps are the only ones you will need for a working KDE/PLASMA system; of course you will need also a user account for login but this you can do whenever you want)
Please check also if you have:
Code: | /etc/sddm.conf.d # ls -al
insgesamt 16
drwxr-xr-x 2 root root 4096 11. Sep 2023 .
drwxr-xr-x 80 root root 4096 6. Mai 12:40 ..
-rw-r--r-- 1 root root 73 30. Mär 14:22 01gentoo.conf
-rw-r--r-- 1 root root 146 12. Mai 2023 kde_settings.conf |
Do you had a problem when emerging some packages ? Maybe do before anything else:
Code: | # emerge --sync
# emerge -uUDv @world |
_________________ https://wiki.gentoo.org/wiki/User:Pietinger |
|
Back to top |
|
|
ultimeight n00b
Joined: 09 Apr 2023 Posts: 60
|
Posted: Mon May 06, 2024 6:05 pm Post subject: |
|
|
pietinger wrote: | This is very strange ... because ... you have/use:
1. Our Gentoo dist-kernel (which has all necessary modules; it works out of the box)
2. All necessary run-scripts in the correct runlevels
3. Corrrect setting of PLASMA profile
4. No error messages in dmesg
5. No error message when booting for rc-scripts
... my last advice would be: Please check if/where you have deviated from these steps:
( a) https://wiki.gentoo.org/wiki/User:Pietinger/Draft/Quick_Installation_OpenRC_for_an_UEFI_System )
+
b) ->
Code: | # emerge -vD xorg-server
# emerge -vD plasma-meta kdecore-meta
# rc-update add elogind boot
# rc-update add display-manager default
# nano -w /etc/conf.d/display-manager
=> DISPLAYMANAGER="sddm"
# reboot |
(because these steps are the only ones you will need for a working KDE/PLASMA system; of course you will need also a user account for login but this you can do whenever you want)
Please check also if you have:
Code: | /etc/sddm.conf.d # ls -al
insgesamt 16
drwxr-xr-x 2 root root 4096 11. Sep 2023 .
drwxr-xr-x 80 root root 4096 6. Mai 12:40 ..
-rw-r--r-- 1 root root 73 30. Mär 14:22 01gentoo.conf
-rw-r--r-- 1 root root 146 12. Mai 2023 kde_settings.conf |
Do you had a problem when emerging some packages ? Maybe do before anything else:
Code: | # emerge --sync
# emerge -uUDv @world |
|
Tried everything that you've mentioned here, the problem still remains, haha. Appreciate all the help. _________________ Regards,
ultimeight. |
|
Back to top |
|
|
steveo314 n00b
Joined: 08 Sep 2006 Posts: 56
|
Posted: Wed Oct 09, 2024 2:00 am Post subject: |
|
|
This issue has come up for me in October 2024 also. Lightdm was successful. But not able
to get sddm running. |
|
Back to top |
|
|
|