You are not logged in.
Pages: 1
I don't know what caused the breakage, but I get this kernel panic whenever I boot my computer:
If I disable systemd from the kernel parameters, I can get to a login prompt, but GDM won't start.
Any ideas on where I should start looking for solutions?
The boatcake is coming for you…
Offline
Can you explain "GDM won't start" if systemd is disabled? Does this kernel panic happen every time the computer is started up with systemd enabled? Try disabling it, trying to start gdm (via command line, not automatically) (does it get errors?), then check /var/log/Xorg.0.log and dmesg for any possible errors (and post them here).
Did you upgrade to systemd from initscripts? Or is this a fresh install with systemd stock from the new release?
You can also try to boot with systemd disabled, remove gdm from auto startup, reboot and see if it still happens (if its a problem with your gdm/gnome setup).
Offline
I can confirm this. Happens sometimes on my T420s on boot or shutdown. Unfortunately I can not say which update introduced this since I reinstalled arch recently.
Offline
Can you explain "GDM won't start" if systemd is disabled? Does this kernel panic happen every time the computer is started up with systemd enabled? Try disabling it, trying to start gdm (via command line, not automatically) (does it get errors?), then check /var/log/Xorg.0.log and dmesg for any possible errors (and post them here).
I was mistaken. It does start, it just didn't work at first because dbus wasn't started.
Did you upgrade to systemd from initscripts? Or is this a fresh install with systemd stock from the new release?
It's a hybrid upgrade. I kept an rc.conf because bumblebee doesn't have a systemd profile, but all other daemons are started directly (not legacy).
You can also try to boot with systemd disabled, remove gdm from auto startup, reboot and see if it still happens (if its a problem with your gdm/gnome setup).
So if I have to revert to initscripts, is there a way to find out what daemons I had enabled in systemd? I can't use systemctl since systemd isn't on.
Last edited by impiaaa (2012-10-25 21:52:30)
The boatcake is coming for you…
Offline
It's a hybrid upgrade. I kept an rc.conf because bumblebee doesn't have a systemd profile, but all other daemons are started directly (not legacy).
Standard bumblebee package from the AUR does have Systemd support. /Offtopic
Last edited by doug piston (2012-10-25 22:04:46)
Offline
Standard bumblebee package from the AUR does have Systemd support. /Offtopic
Huh, okay. Maybe I was thinking about bbswitch? Anyway, I'll take a look once I figure out how to fix my current problem.
The boatcake is coming for you…
Offline
So, I switched back to initscripts (I found out I still had my old Daemons array commented out), and I can boot up now, but I just got this after waking up and trying to log in:
It appears to be the same one as before. So, that leads me to believe that it's not a problem with systemd. Where can I start looking for the real origin of the problem? Is it possible this is a bug?
Last edited by impiaaa (2012-10-29 19:35:39)
The boatcake is coming for you…
Offline
https://www.archlinux.org/news/consolek … by-logind/
Well then, it looks like I'll have to upgrade somehow. Does anybody have any ideas? Is a complete re-install the best option at this point?
Edit: Never mind, it fixed itself.
Somehow.
Last edited by impiaaa (2012-10-31 13:34:21)
The boatcake is coming for you…
Offline
Pages: 1