You are not logged in.
It's been a few years since I used arch. I returned to the fold this morning, and after performing a fresh install and handling some basic system admin stuff using the terminal, I installed plasma-next. This seems to have been an error. I didn't run anything at all, just rebooted. The boot process hangs up early on, while checking /dev/sda3 (which is my /home partition). To clarify: I rebooted several times before the installation of plasma-next and it worked fine; installed plasma-next and no boot. So I used the live media to log into a chroot environment and uninstall plasma-next and all of it's dependencies. Guess what... Still won't boot. Same prob. Can anyone advise?
Last edited by 2handband (2014-11-21 17:31:02)
Offline
Is there anything in the journal/logs when you chroot into the machine? I am definitely not authoritative on the subject, but I fail to see how the system would stop booting because of Plasma-Next -- at least at the "checking /dev/sda3...." stuff.
Matt
"It is very difficult to educate the educated."
Offline
Nothing I can see in the logs that looks relevant. Maybe the easiest thing since this was a fresh install would be to just reinstall, but since the main reason I installed this was to check out plasma 5 I'd be afraid of the same damn thing happening again.
Offline
Okay... I just remembered that I installed sddm as well. I removed that and all of its dependencies and the system now boots. The question now is: what's the next move. Either sddm or one of its dependencies is rendering the system unbootable, and I would like to install it so I can run plasma 5. I should add that I did no configuration to sddm at all; I just installed it.
Offline
I just tried installing sddm only and configuring it as per the wiki page. Same issue.
Offline
I boot into Plasma 5 perfectly fine with the Mate Display Manager. However, there is the caveat that I seem to be one (of very few) person that actually manages to Mate Display Manager to work on Arch...
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
So what packages get installed with SDDM?
Matt
"It is very difficult to educate the educated."
Offline
Mesa-libgl fontconfig icu inputproto libjpeg-turbo libxi libxbcommon libxbcommon-x11 libxrender qt5-base qt5-declarative qt5-xmlpatterns qtchooser renderproto sqlite xcb-util xcb-util-image xcb-util-keysyms xcb-utill-wm xkeyboard-config
Offline
Okay, update. After uninstalling and reinstalling everything, the system will boot with sddm installed. But when I enable sddm, the the problem recurs. It goes away when I chroot in and disable sddm. This cries out to me that I have a configuration issue somewhere.
I enabled sddm with the command:
systemctl enable sddmThe command created the appropriate symlink and as near as I could tell everything was correct but obviously I have something set incorrectly. Any help?
Offline
Hit ctrl-alt-f2, login, check `systemctl status sddm` and /var/log/Xorg.0.log
Last edited by Scimmia (2014-11-21 05:45:54)
Offline
The log file you directed me to says some kernel modules failed to load, specifically ati, vesa, modesetting, and fbdev. apparently the modules do not exist... Aren't those in the stock kernel?
Offline
No, they are not stock. But sometimes that doesn't matter. (For example, vesa failing just means you're not using vesa.) What video card do you have and have you installed the drivers for it? And if you can, maybe post the whole log to one of those online "paste" sites?
Last edited by mrunion (2014-11-21 14:13:57)
Matt
"It is very difficult to educate the educated."
Offline
Just fixed it... Turns out I failed to install the proper display drivers. Thanks for trying to help!
Offline