On Tue, Jun 3, 2014, at 09:13 AM, Mike Cloaked wrote: > It is quite likely you have been hit by the now infamous efistub bug - > see: > > https://bugs.archlinux.org/task/33745?project=1 > > https://bugzilla.kernel.org/show_bug.cgi?id=68761 > > https://bbs.archlinux.org/viewtopic.php?id=156670 > > > > On Tue, Jun 3, 2014 at 4:38 PM, Manuel Reimer > <Manuel.Spam@xxxxxxxxxxxxxx> > wrote: > > > On 06/03/2014 05:16 PM, Anatol Pomozov wrote: > > > >> To recover your machine: > >> 1) Boot from Arch ISO. I always have an USB pan with Arch image and > >> found it useful for emergency cases. > >> 2) Find your system partitions. Use 'lsblk' for this > >> 3) mount your system partition, e.g. 'mkdir system; mount /dev/sda1 > >> system' > >> 4) arch-chroot into your system: 'arch-chroot system' > >> 5) fix your system e.g. downgrade kernel to previous version 'downgrade > >> linux' > >> 6) reboot and enjoy > >> > > > > Did so, now. Now I'm on 3.14.4, again. System boots without any problems. > > > > But why can't I use the current kernel? Does someone here successfully > > boot 3.14.5 via efistub? Bug in kernel? Or maybe bug in kernel > > configuration? > > > > Greetings, > > > > Manuel > > > > > > > -- > mike c I get these boot issues sporadically with kernel updates. I keep a separate boot entry in gummiboot with a kernel I know boots in case I get hit with it again. I haven't found anything useful on this silly bug so I'd say this is your best option if you would like to avoid booting a liveCD every time it happens. Hong
