[arch-general] rEFInd 0.6.4 + linux 3.7.2-1 fail to boot
Hi, everyone. I've a HP Pavilion g4 machine with UEFI, using rEFInd. After a upgraded to refind-efi 0.6.4-1 and linux 3.7.2-1, my system stopped to boot. rEFInd loads properly, and others boot options, like EFI Shell and Windows 8 are working, but trying to boot kernel 3.7.2 froze on the message in begin saying "Starting vmlinuz-linux ...kernel options". initrd was built correctly. This issue only occurs with linux 3.7.2, downgrading to 3.7.1 makes system bootable again (from where I'm writing). rEFInd config file is basically default, only with timeout changed to 5. My boot options: root=/dev/AndreSYS/Arch resume=/dev/AndreSYS/Swap cryptdevice=/dev/disk/by-uuid/e38e188e-f775-41fe-9607-ce977c7716d8:syslvm ro add_efi_memmap rootfstype=ext4 -- https://profiles.google.com/andre.vmatos
On Mon, Jan 14, 2013 at 12:10:31PM -0200, André Vitor de Lima Matos wrote:
Hi, everyone. I've a HP Pavilion g4 machine with UEFI, using rEFInd. After a upgraded to refind-efi 0.6.4-1 and linux 3.7.2-1, my system stopped to boot. rEFInd loads properly, and others boot options, like EFI Shell and Windows 8 are working, but trying to boot kernel 3.7.2 froze on the message in begin saying "Starting vmlinuz-linux ...kernel options". initrd was built correctly. This issue only occurs with linux 3.7.2, downgrading to 3.7.1 makes system bootable again (from where I'm writing). rEFInd config file is basically default, only with timeout changed to 5. My boot options: root=/dev/AndreSYS/Arch resume=/dev/AndreSYS/Swap cryptdevice=/dev/disk/by-uuid/e38e188e-f775-41fe-9607-ce977c7716d8:syslvm ro add_efi_memmap rootfstype=ext4
Oh the irony... Please subscribe to arch-dev-public if you're going to continue to use the testing repository: https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024260....
Oh the irony... Please subscribe to arch-dev-public if you're going to continue to use the testing repository:
https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024260.... Hi, Dave. Thanks for the fast reply. If you are talking about file-5.12 problem, as I said, initrd (a.k.a. initramfs) was built properly, since I had downgraded to file 5.11
Em 14-01-2013 18:39, Dave Reisner escreveu: previously. And I'm subscribed and following discussions in arch-dev-public. My problem persist, preventing me from upgrade to linux 3.7.2. Any ideas? -- http://www.google.com/profiles/andre.vmatos
On Mon, Jan 14, 2013 at 11:33:56PM -0200, André Vitor de Lima Matos wrote:
Oh the irony... Please subscribe to arch-dev-public if you're going to continue to use the testing repository:
https://mailman.archlinux.org/pipermail/arch-dev-public/2013-January/024260.... Hi, Dave. Thanks for the fast reply. If you are talking about file-5.12 problem, as I said, initrd (a.k.a. initramfs) was built properly, since I had downgraded to file 5.11
Em 14-01-2013 18:39, Dave Reisner escreveu: previously. And I'm subscribed and following discussions in arch-dev-public. My problem persist, preventing me from upgrade to linux 3.7.2. Any ideas?
Just a thought: Did you forget to copy the generated kernel image of the 3.7.2 to the EFI partition? Regards.
André Vitor de Lima Matos:
My problem persist, preventing me from upgrade to linux 3.7.2.
I have the same problem (and I don't use *testing*): When I upgraded to 3.6.11, after rebooting, rEFInd froze at the *rEFInd - Booting OS* stage and downgrading to 3.6.10 didn't help. I can boot in BIOS mode though. -- b.d (| |) ^ ^
Em 15-01-2013 05:24, Bill Sun escreveu:
Just a thought: Did you forget to copy the generated kernel image of the 3.7.2 to the EFI partition?
No. If so, would the kernel booted and failed to complete boot process due to mismatch between kernel image/initramfs and installed modules. But the kernel does not even begin starting, stopping just after option is selected in rEFInd and message "Starting vmlinuz-linux ...options" of rEFInd is printed. -- http://www.google.com/profiles/andre.vmatos
On 14 Jan 2013 at 12:10:31 -0200, André Vitor de Lima Matos wrote:
After a upgraded to refind-efi 0.6.4-1 and linux 3.7.2-1, my system stopped to boot.
I'm having this issue with linux 3.7.2-1 too. I use gummiboot-efi and file from core (5.11-1). Linux 3.7.1-2 boots ok. The image of linux 3.7.2-1 builds and is copied to the correct paths. I tried to remove i915 from MODULES and change the compression back to the default gzip, but I still can't boot from 3.7.2-1. My MODULES only has i915, and the HOOKS array is ~~~~~~~~~~ HOOKS="base udev autodetect plymouth modconf block plymouth-encrypt filesystems consolefont usbinput fsck" ~~~~~~~~~~ Regards, Kazuo Teramoto
Em 15-01-2013 08:00, Bastien Dejean escreveu:
I have the same problem (and I don't use *testing*):
When I upgraded to 3.6.11, after rebooting, rEFInd froze at the *rEFInd - Booting OS* stage and downgrading to 3.6.10 didn't help. I can boot in BIOS mode though.
I've not tested in BIOS mode, as I'm sure it works, 'cause if not, a new release fixing problem would have been launched. But I prefer to avoid a upgrade of one release instead of leaving a bleeding corner (UEFI). I've done some tests, including adding kernel image directly to NVRAM via efibootmgr with proper options, and still 3.7.1-2 boots ok, and 3.7.2-1 freezes before any boot message. So, the problem is not with rEFInd, but with kernel and/or EFI implementation. -- http://www.google.com/profiles/andre.vmatos
On 15 Jan 2013 at 18:35:19 -0200, Kazuo Teramoto wrote:
I'm having this issue with linux 3.7.2-1 too. I use gummiboot-efi and file from core (5.11-1). Linux 3.7.1-2 boots ok.
Linux 3.7.3-1 is booting for me. Regards, Kazuo Teramoto
Em 17-01-2013 23:49, Kazuo Teramoto escreveu:
Linux 3.7.3-1 is booting for me.
Regards,
[SOLVED] Confirmed working here too, with 3.7.3-1. Thanks all. -- http://www.google.com/profiles/andre.vmatos
I just upgraded to 3.7.3-1-x86_64 (from 3.6) and my system now fails to boot. I got a Thinkpad T430s (which has Optimus Graphics stuff) and use rEFInd 0.6.4-1. BIOS legacy boot stuff is disabled in efi setup. I tried booting with "nomodeset" but without success. Downgrading to 3.6.11-1 serves as a workaround for now -- View this message in context: http://archlinux.2023198.n4.nabble.com/rEFInd-0-6-4-linux-3-7-2-1-fail-to-bo... Sent from the arch general mailing list archive at Nabble.com.
upgrading to linux 3.7.4-1 from testing fixed the issue for me -- View this message in context: http://archlinux.2023198.n4.nabble.com/rEFInd-0-6-4-linux-3-7-2-1-fail-to-bo... Sent from the arch general mailing list archive at Nabble.com.
Em 22-01-2013 21:20, christophg escreveu:
upgrading to linux 3.7.4-1 from testing fixed the issue for me
I can't boot with 3.8-2 again!! linux 3.8-1 is working fine (I booted from a usb drive in BIOS mode to downgrade), and I'm writing from it, but 3.8-2 freezes in previous rEFInd message. -- /-=| Δ ŋ đ г Σ |=-\ «» ♫♫♫ http://www.google.com/profiles/andre.vmatos
On 25 Feb 2013 at 18:13:14 -0300, André Vitor de Lima Matos wrote:
I can't boot with 3.8-2 again!! linux 3.8-1 is working fine
For me it stopped to boot after > 3.7.7. Linux-3.7.7 is the last version that boot, each version after it don't. Gummiboot stopped to boot in v22, only v17 boots for me. When I choose the arch entry in the boot loader and it become freeze at the boot loader screen. The interaction of bootable and kernel/gummiboot versions is a mess on my system. The versions I cannot boot from form a dense set! I always bring an arch livecd with me (my UEFI mobo wont boot from USB). Currently I'm busy so I don't have time to debug it. As I don't see anyone talking about boot problems I'm blaming my Samsung laptop. I hope to have some time to debug and put the blame in someone else... Regards, Kazuo Teramoto
I can't boot with 3.8-2 again!! linux 3.8-1 is working fine For me it stopped to boot after > 3.7.7. Linux-3.7.7 is the last version
On 25 Feb 2013 at 18:13:14 -0300, André Vitor de Lima Matos wrote: that boot, each version after it don't. Gummiboot stopped to boot in v22, only v17 boots for me.
When I choose the arch entry in the boot loader and it become freeze at the boot loader screen.
The interaction of bootable and kernel/gummiboot versions is a mess on my system. The versions I cannot boot from form a dense set! I always bring an arch livecd with me (my UEFI mobo wont boot from USB).
Currently I'm busy so I don't have time to debug it. As I don't see anyone talking about boot problems I'm blaming my Samsung laptop. I hope to have some time to debug and put the blame in someone else...
Regards, Kazuo Teramoto If you want to avoid to use the livecd, you could install a second kernel, like from repo-ck and have it as an altrenative bootoption (I also have problems with some kernels here, there is allready a thread on
On 02/26/2013 12:17 AM, Kazuo Teramoto wrote: that topic).
linux-3.7.9-2 seems to fix the problem again. Works on my Lenovo T430s -- View this message in context: http://archlinux.2023198.n4.nabble.com/rEFInd-0-6-4-linux-3-7-2-1-fail-to-bo... Sent from the arch general mailing list archive at Nabble.com.
participants (7)
-
André Vitor de Lima Matos
-
Bastien Dejean
-
Bill Sun
-
christophg
-
Dave Reisner
-
Kazuo Teramoto
-
Max Löwen