[arch-general] Kernel updated to 3.14.5-1. Now my Lenovo IdeaPad hangs on boot...
Hello, I use "gummiboot" to boot my Notebook. So far all kernel updates worked well and I never got any problems, but for some reason the update to 3.14.5 now causes my system to no longer boot up. Can someone help me to find the reason for the problem and to get my Notebook to boot up again? Thanks in advance. Greetings, Manuel
On Tue, Jun 3, 2014 at 12:05 PM, Manuel Reimer <Manuel.Spam@nurfuerspam.de> wrote:
Hello,
I use "gummiboot" to boot my Notebook. So far all kernel updates worked well and I never got any problems, but for some reason the update to 3.14.5 now causes my system to no longer boot up.
Can someone help me to find the reason for the problem and to get my Notebook to boot up again?
Try booting in legacy/bios mode. Inside system, try just recompiling kernel from official pkgbuild. In my HP laptop, some kernels just refuses to boot in UEFI mode, hanging in kernel loading (directly or from any bootloader, as refind). Recompiling kernel or downgrading to previous working fix the issue. -- http://www.google.com/profiles/andre.vmatos
On 06/03/2014 05:11 PM, André Vitor wrote:
Try booting in legacy/bios mode. Inside system, try just recompiling kernel from official pkgbuild. In my HP laptop, some kernels just refuses to boot in UEFI mode, hanging in kernel loading (directly or from any bootloader, as refind). Recompiling kernel or downgrading to previous working fix the issue.
That's the first time, I have issues like this on my laptop. But thanks to all for the help. Downgrading did the trick and I hope that the next kernel will work again... Greetings, Manuel
Hi On Tue, Jun 3, 2014 at 8:05 AM, Manuel Reimer <Manuel.Spam@nurfuerspam.de> wrote:
Hello,
I use "gummiboot" to boot my Notebook. So far all kernel updates worked well and I never got any problems, but for some reason the update to 3.14.5 now causes my system to no longer boot up.
Can someone help me to find the reason for the problem and to get my Notebook to boot up again?
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
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
On Tue, Jun 3, 2014 at 5:38 PM, Manuel Reimer <Manuel.Spam@nurfuerspam.de> wrote:
Does someone here successfully boot 3.14.5 via efistub? Bug in kernel? Or maybe bug in kernel configuration?
works for me, thinkpad x230, syslinux as boot manager
Hi On Tue, Jun 3, 2014 at 8:38 AM, Manuel Reimer <Manuel.Spam@nurfuerspam.de> 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?
You provided zero information about your problem so it is hard to tell what is going on there. It might be a kernel bug, here is a changelog since 3.14.4 https://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.14.5 check if you see changes related to your issue.
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@nurfuerspam.de> 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
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@nurfuerspam.de> 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
On 06/03/14 at 03:51pm, Hong Shick Pak wrote:
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.
Rather than keep an old kernel around, I just keep grub-efi set up. Since the issue Mike Cloaked is referring to is the efistub bug, grub or syslinux (or elilo) continue to work just fine. So I primarily use gummiboot, but in the gummiboot menu I have ne entry to get to grub. From grub I can boot the kernel normally. But I haven't been hit by this bug since about 3.9 I think... -- Curtis Shimamoto
On Wed, Jun 4, 2014 at 1:57 AM, Curtis Shimamoto < sugar.and.scruffy@gmail.com> wrote:
On 06/03/14 at 03:51pm, Hong Shick Pak wrote:
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.
Rather than keep an old kernel around, I just keep grub-efi set up. Since the issue Mike Cloaked is referring to is the efistub bug, grub or syslinux (or elilo) continue to work just fine.
So I primarily use gummiboot, but in the gummiboot menu I have ne entry to get to grub. From grub I can boot the kernel normally. But I haven't been hit by this bug since about 3.9 I think...
If it is any help what I do is to have grub installed as well as my main boot manager, which is rEFInd, which is essentially the corresponding setup to that which Curtis reported for gummiboot in the previous post. I have a rEFInd config stanza that will chainload the grub bootloader to boot the kernel when the efistub fails to boot after any particular kernel update. Grub will always boot the same problematic kernel since it does not use the efistub. I had a thread which details how I chainload grub from rEFInd, when I had an issue setting it up, at https://bbs.archlinux.org/viewtopic.php?id=181906 and the corresponding technique can be employed for gummiboot as Curtis said in the previous post. I too have not had a problem booting kernels with the efistub recently, but it is certainly worthwhile setting up grub as an option so that you can still boot your system quickly in the event that the efistub kernel fails to boot. Then you can stay with the new kernel until the next kernel update so it is then no longer a worry. However it would be ideal if the underlying bug that causes occasional efistub kernels to fail to boot on particular hardware. Thus far nobody has been able to pin down any consistent factors that would allow diagnosing where in the boot code or firmware the problem lies. -- mike c
participants (7)
-
Anatol Pomozov
-
André Vitor
-
Curtis Shimamoto
-
Hong Shick Pak
-
Manuel Reimer
-
Mike Cloaked
-
Simon Hanna