You are not logged in.
After updating my system today (with all the new KDE stuff and such), my system hangs during boot, at
[ OK ] Reached target Graphical Interface.
Pressing enter brings me to a terminal login, and I can access others through Ctrl+Alt+F1, F2, etc.
I read through the end of the pacman log, but didn't find anything that seemed pertinent - something about all cabalized packages needing to be reinstalled, but in my reading of ther people's threads on ghc and haskell during the update, I didn't see anyone with the problem I had.
Any thoughts?
EDIT:
okay, as explained below, my system isn't hanging, but it's also not automatically starting kdm which automatically logs me in, and it should be doing that.
ALSO
I am getting at least two error messages during boot. The first goes by too quickly for me to see anything except the existence of red text; the second reads (in part)
see systemctl status systemd-modules-load.service
which eventually leads to me finding that the vboxdrv is not loading properly. My brief research showed no way to fix this, and I removed all virtualbox-related packages with pacman, but a reboot shows no obvious change. I'll continue looking into it tomorrow, I am so done for tonight.
Last edited by nikolardo (2013-02-10 20:03:51)
Offline
If pressing enter brings up a login prompt, it sounds like it's booting just fine and that message is just showing after getty starts. What's the problem? You don't even have to hit enter, just enter your username and go on like normal.
Offline
FWIW, the last time i had my system hang there, i had to uninstall the reinstall a different graphics card driver (in my case, nvidia for nvidia-beta).
If I'm curt with you it's because time is a factor. I think fast, I talk fast and I need you guys to act fast if you wanna get out of this. So, pretty please... with sugar on top. Clean the [censored] car. -The Wolf
Offline
@Scimmia, I totally forgot that my setup is not the only one: what should happen is kdm should automatically log me in and then lock the screen.
@flipper T - reinstalling nvidia (without uninstalling or changing the driver) has entirely solved the problem, thanks.
Offline
Okay actually, it worked exactly one time, and while booted up happily I upgraded linux and linux-headers (and one other thing?) and now I'm back at square one, except uninstalling and reinstalling nvidia doesn't help; more info added to original post.
Offline
What does
systemctl status kdm.service
show?
And can you start X manually?
Offline
systemctl status kdm.service
kdm.service - K Display Manager
Loaded: loaded (usr/lib/systemd/system/kdm.service; disabled)
Active: active (running) since Sun 2013-02-10 07:25:10 EST; 12min ago
Main PID: 374 (kdm)
CGroup: name=systemd:/system/kdm.service
⌙374 /usr/bin/kdm -nodaemon
also, I'm not used to starting X manually, but both +startx" and "xorg-xinit", as suggested by the wiki, return "command not found".
Offline
The kdm systemd unit is disabled, run
sudo systemctl enable kdm.service
and reboot.
"xorg-xinit" is the package that provides "startx", which you don't seem to have.
Offline
After executing the given command, no change at all.
I installed xorg-xinit and ran startx, which returns, after lots in initializing things,
Loading extension GLX
modprobe: ERROR: could not insert 'nvidia': Invalid argument
Fatal server error:
no screens found
(EE)
Please consult The X.Org foundation support
at http://wiki.x.org
for help
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
the seemingly relevant bit of /var/log/Xorg.0.log
(II) LoadModule: "nvidia"
(II) Module nvidia: vendor="Nvidia Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your system's kernel log for additional error messages.
(II) UnloadModule: "nvidia"
(II) Unloading nvidia
(EE) Failed to load module "nvidia" (module-specific error, 0)
(EE) No drivers available
Fatal server error:
no screens found
and the seemingly relevant bit of my kernel.log
nvidia: disagrees about version of symbol efi_enabled
nvidia: Unknown symbol efi_enabled (err -22)
that same code also appears a little later on.
So, it appears to be a nvidia problem. So far I have uninstalled and reinstalled nvidia, and I have run nvidia-xconfig as root, with no change.
Offline
After installing nvidia-beta, things appear to be working.
Offline
Forgot to mention to you previously....I have had to alternate between nvidia & nvidia-beta with each new kernal update. I do not understand why.
To add to the mystery, I would bet that you can now successfully re-install nvidia now. This is why I initially recommended alternating the two.
If I'm curt with you it's because time is a factor. I think fast, I talk fast and I need you guys to act fast if you wanna get out of this. So, pretty please... with sugar on top. Clean the [censored] car. -The Wolf
Offline
I have previously had to reinstall nvidia after kernel updates, but never have I had to install a different version. It's an odd little buggish thing, to be sure, but easily fixed, I guess.
Offline