You are not logged in.
Using a pure systemd setup, I'm trying to boot directly to a display manager.
If I enable the gdm, slim, or lightdm services, the system will drop to a black screen after boot. This does not seem to be an "empty screen," but rather that the system is shutting off my laptop screen.
To regain control of the system, I must reboot and add "systemd.unit=mutli-user.target" to the boot command and drop down to the terminal. From there I can either call "systemctl start display-manager.service" or "systemctl isolate graphical.target" successfully and boot into any of the display managers.
My graphics hardware is an AMD r600 chipset on the FOSS drivers.
I haven't been able to find any messages in any logs (xorg, dmesg, journalctl, etc.) that mention why this is happening.
Sweet zombie jesus!
Offline
No ideas whatsoever? I've googled all over the damn place, read through lots and lots of forums that are almost helpful. I'm at a loss here.
What would cause something to not work when it's at the end of the systemd boot process but work fine when run from the command line?
Sweet zombie jesus!
Offline
So, disabled the "quiet" flag just to see if I can see what's happening. And it booted right in. So it seems that everything is just happening too fast. Might see if I can slow down the boot process a little, then take it off of verbose mode.
Sweet zombie jesus!
Offline
I'm having the same problem. Eliminating "quiet" helped _some_ of the time. Now I have a fifty fifty chance of being able to log in after boot.
Offline
If disabling the quiet flag magically makes it work sometimes, report a bug.
Steven [ web : git ]
GPG: 327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C
Do not email: honeypot@stebalien.com
Offline
If disabling the quiet flag magically makes it work sometimes, report a bug.
I would, but it doesn't "fix" the problem _all_ the time. Just sometimes.
Offline