You are not logged in.
Sounds like a kerne installation issue - did you forget to mount /boot before updating?
https://wiki.archlinux.org/index.php/Ch … rch-chroot
Offline
With loglevel=7 and some CTRL pressions, the system boots normally, so it isn't a boot partition issue: it's the same f***ing issue...
Offline
Just to be sure: w/o "loglevel=7" the system doesn't boot *at all* but w/ "loglevel=7" it boots but requires keyboard interaction? That's the most weird thing I ever heard of (ok - "one of" ;-) ... in case.
Did you try the ata probe timeout parameter from comment #20 (alongside loglevel=7, it seems required...)?
Offline
Just to be sure: w/o "loglevel=7" the system doesn't boot *at all* but w/ "loglevel=7" it boots but requires keyboard interaction?
Yes, it seems very very strange also to me but so it is..
Did you try the ata probe timeout parameter from comment #20 (alongside loglevel=7, it seems required...)?
I think yes, and I remember that id didn't work... now I can't switch off the pc, maybe I'll try tomorrow...
Offline
Smells like some HW takes too long™ to initialize and a slower booting kernel (because being busy printing debug stuff) covers that?
Do you skip kernel selection in the bootmanager? What if you wait and how's the behavior on a warm reboot?
Offline
Sorry but I'm very busy at work. Some fresh updates: with latest kernel, the system doesn't boot anymore, also if I try to disconnect the keyboard, with loglevel=7, etc...
The lts-kernel instead boots if I disconnect the keyboard after the system hangs at "Triggering uevents"... And it also boots if I disconnect the mouse (and not the keyboard) when the system hangs at "triggering uevents" and then I recconect the mouse and press ctrl button on the keyboard...
Well, this problem is very frustrating...
Just another consideration: when I boot the archlinux cd, I've to press some times the ctrl button to resume the boot process...
Last edited by giacombum (2017-04-10 17:27:50)
Offline
Do you understand the problem implied in comment #30? It might not be the keyboard but some other HW (likely wired to the usb bus)
See http://redsymbol.net/linux-kernel-boot-parameters/ and notably boot_delay, io_delay, rootdelay, and virtually every usb* parameter.
Also check lsusb and remove every device you can.
Offline