You are not logged in.
Hello,
I have a similar problem like this guy: https://bbs.archlinux.org/viewtopic.php?id=230877
I start my PC and it is stuck with the message
Starting version 235
A few ACPI errors
and the message, that my root-Partition is clean
I can log in to another terminal and there I can start my GUI via startx and following startkde.
But how can I restore the automatic start at reboot?
Unlike in the other thread I don't get any graphics on my main terminal and I'm using xf86-video-ati instead of the intel-driver.
Obviously I'm starting X11.
Any idea that would help me?
Thanks in advance.
Last edited by Phate (2017-10-14 13:53:28)
Offline
I tried a few things and the problem lies within sddm. The thing is, I just don't understand why there is a problem. When I start my pc, the interface is stuck. So I log in to another terminal.
There I checked the sddm-service, but I couldn't find an error, which would explain the sddm behaviour.
# systemctl status sddm.service
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset:
disable
Active: active (running) since Sat 2017-10-14 08:52:02 CEST; 1min 37s ago
Docs: man:sddm(1)
man:sddm.conf(5)
Main PID: 395 (sddm)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/sddm.service
└─395 /usr/bin/sddm
Okt 14 08:52:02 desktop systemd[1]: Started Simple Desktop Display Manager.
Okt 14 08:52:02 desktop sddm[395]: Initializing...
Okt 14 08:52:02 desktop sddm[395]: Logind interface found
Okt 14 08:52:02 desktop sddm[395]: Starting...
Okt 14 08:52:02 desktop systemd[1]: Started Simple Desktop Display Manager.
Okt 14 08:52:02 desktop sddm[395]: Initializing...
Okt 14 08:52:02 desktop sddm[395]: Logind interface found
Okt 14 08:52:02 desktop sddm[395]: Starting...
and
[root@desktop ~]# journalctl -rx --unit=sddm.service
-- Logs begin at Tue 2017-07-18 21:38:33 CEST, end at Sat 2017-10-14 08:54:52
CEST. --
Okt 14 08:52:02 desktop sddm[395]: Starting...
Okt 14 08:52:02 desktop sddm[395]: Logind interface found
Okt 14 08:52:02 desktop sddm[395]: Initializing...
Okt 14 08:52:02 desktop systemd[1]: Started Simple Desktop Display Manager.
-- Subject: Unit sddm.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sddm.service has finished starting up.
--
-- The start-up result is RESULT.
-- Reboot --
Okt 14 08:51:39 desktop systemd[1]: Stopped Simple Desktop Display Manager.
-- Subject: Unit sddm.service has finished shutting down
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sddm.service has finished shutting down.
Okt 14 08:51:39 desktop sddm[640]: QProcess: Destroyed while process
("/usr/lib/sddm/sddm
Okt 14 08:51:39 desktop sddm[640]: Running display stop script
"/usr/share/sddm/scripts/
Okt 14 08:51:39 desktop sddm[640]: Display server stopped.
Okt 14 08:51:39 desktop sddm-helper[1174]: [PAM] returning.
Okt 14 08:51:39 desktop sddm-helper[1174]: [PAM] Authenticating...
Okt 14 08:51:39 desktop sddm-helper[1174]: [PAM] Starting...
Okt 14 08:51:39 desktop sddm[640]: Display server stopping...
Okt 14 08:51:39 desktop sddm[640]: Socket server stopped.
For now it works, if I just reboot sddm on another terminal. After that I can use it like intended. I just would like it to start automatically again.
Offline
I had similar problem, sddm service was up but all I got was tty. Returning to stock kernel package fixed it for me.
Offline
Stock kernel would mean the linux package, wouldn't it? Because that's the one, that's installed on my system.
Offline
I'm getting the same problem, also on the stock kernel. It seems intermittent, as occasionally it starts up fine, other times needs a restart. From the difference in logs from a successful start and an unsuccessful, my hunch is that it's not finding a display.
Is there a way to increase the logging from sddm to try to figure out what's going on here?
Offline
So the title here is totally wrong and misleading? The problem is actually starting SDDM?
Offline
So the title here is totally wrong and misleading? The problem is actually starting SDDM?
yeah, that was before I knew, that sddm was the culprit, I'll change it
Offline
Come on, you knew it was never getting to KDE/Plasma
Offline
I could solve it thanks to kifuna -> https://bbs.archlinux.org/viewtopic.php … 8#p1742698
I had to add radeon to my initramfs
Offline
Come on, you knew it was never getting to KDE/Plasma
If you say so.
Offline
I could solve it thanks to kifuna -> https://bbs.archlinux.org/viewtopic.php … 8#p1742698
I had to add radeon to my initramfs
I've had the same problem and adding radeon as module to initramfs solved my problem, why this occured though is something i do not know. I't does not help downgrading to an older kernel,some bug with sddm? I've tried with booth the new supplied config-file and the old one i had, no difference.
Offline
Just thought I'd copy this over as the other topic has been deleted as a duplicate of this (it's still visible if you're logged in). The general workaround for this is to enable KMS early start (https://wiki.archlinux.org/index.php/Ke … _KMS_start), which involves adding radeon or another relevant module to initramfs; details in the wiki.
Offline
Heh, I added i915 to initramfs while also reverting to stock kernel. It wasn't kernel after all then.
Offline
This is an unacceptable level of grief for a DM. Here at last, after thinking it was a kernel or systemd problem and downgrading them both from a rescue disk.I chose to downgrade sddm and put it on ignore for a while. Glad to know there is a workaround though, I may try it later.
Offline
This is an unacceptable level of grief for a DM.
We are so terribly sorry that our free software project, run by volunteers in their free time, that provides eye candy with no real functional purpose, does not meet your exacting standards. Perhaps, once you have recovered from your sense of outrage, you might see your way clear to writing something superior?
Offline