You are not logged in.
Pages: 1
I've managed to boot and get all the way to decrypting my drive. Right after entering my password and pressing enter, the boot procedure gets stuck.
The following link contains screenshots of what the screen looks like when things gets stuck: http://imgur.com/a/bhi6U
EDIT: Added one more image to album.
Last edited by linduxed (2015-01-12 23:09:20)
Offline
Can you switch to another TTY and look at the journal for the failed service?
Offline
No, when it gets stuck, I can't switch to another TTY.
Offline
After unplugging all the USB devices and hubs apart from the USB keyboard, the various messages about USB problems are gone, but it still gets stuck after password entry. The "kvm: disabled by bios" is the last message still.
Offline
Adding the kernel parameters "noapic acpi=off" got me into a TTY, but I haven't figured out why that's necessary.
Offline
I added one more image to the album. This time I removed the "quiet" kernel parameter to see what was printed out (I probably should have started with this). I don't think there's any new information here.
I'll investigate whether this bug report is of any help: https://bugs.archlinux.org/task/42505
Offline
Chroot in and look at the journal for the failed boot.
Offline
Using the kernel parameter "nomodeset" allows me to get to a TTY. Unless I've misunderstood something, I think this could be graphics card related.
Offline
Using the kernel parameter "nomodeset" allows me to get to a TTY. Unless I've misunderstood something, I think this could be graphics card related.
Yep. What card and driver are you using?
Offline
I managed to fix the problem!
After booting up with "nomodeset" I installed the "nvidia-beta" package from AUR (probably could have used the regular "nvidia" package too) I could drop the "nomodeset" kernel parameter. Things seem to be fixed.
Offline
Pages: 1