[arch-general] Grub2
With the latest Grub2 (grub2-efi-x86_64 1:2.00beta2-2), it seems that grub- mkconfig is not picking up my fallback initramfs any more, so there's no fallback option in the boot menu. Has anyone else experienced this? Is there a way of fixing it? Thanks, Paul
Have you tried manually adding it in grub.cfg BTW? On 3/25/12, Paul Gideon Dann <pdgiddie@gmail.com> wrote:
With the latest Grub2 (grub2-efi-x86_64 1:2.00beta2-2), it seems that grub- mkconfig is not picking up my fallback initramfs any more, so there's no fallback option in the boot menu. Has anyone else experienced this? Is there a way of fixing it?
Thanks, Paul
On Monday 26 Mar 2012 02:18:53 Saurav Modak wrote:
Have you tried manually adding it in grub.cfg BTW?
Editing grub.cfg is a naughty thing to do with Grub2 :p The "correct" thing to do would be to add the fallback to /etc/grub.d/41_custom. However, Grub previously automatically detected the fallback correctly. I'm wondering why it doesn't now. Paul
On 03/26/2012 03:08 AM, Paul Gideon Dann wrote:
On Monday 26 Mar 2012 02:18:53 Saurav Modak wrote:
Have you tried manually adding it in grub.cfg BTW?
Editing grub.cfg is a naughty thing to do with Grub2 :p The "correct" thing to do would be to add the fallback to /etc/grub.d/41_custom. However, Grub previously automatically detected the fallback correctly. I'm wondering why it doesn't now.
Paul
After a kernel panic on boot after todays kernel update (unrelated) while doing things to get back up and running I just realized this as well. I do not have a fallback image for either of the 2 kernels I run for arch.
I'm on a fully updated system and I ran grub-mkconfig and I still have an option for the fallback kernel. Josh On Mar 27, 2012 7:44 PM, "Don deJuan" <donjuansjiz@gmail.com> wrote:
On 03/26/2012 03:08 AM, Paul Gideon Dann wrote:
On Monday 26 Mar 2012 02:18:53 Saurav Modak wrote:
Have you tried manually adding it in grub.cfg BTW?
Editing grub.cfg is a naughty thing to do with Grub2 :p The "correct" thing to do would be to add the fallback to /etc/grub.d/41_custom. However, Grub previously automatically detected the fallback correctly. I'm wondering why it doesn't now.
Paul
After a kernel panic on boot after todays kernel update (unrelated) while doing things to get back up and running I just realized this as well. I do not have a fallback image for either of the 2 kernels I run for arch.
På Tue, 27 Mar 2012 23:43:36 -0000, skrev Don deJuan <donjuansjiz@gmail.com>:
On 03/26/2012 03:08 AM, Paul Gideon Dann wrote:
On Monday 26 Mar 2012 02:18:53 Saurav Modak wrote:
Have you tried manually adding it in grub.cfg BTW?
Editing grub.cfg is a naughty thing to do with Grub2 :p The "correct" thing to do would be to add the fallback to /etc/grub.d/41_custom. However, Grub previously automatically detected the fallback correctly. I'm wondering why it doesn't now.
Paul
After a kernel panic on boot after todays kernel update (unrelated) while doing things to get back up and running I just realized this as well. I do not have a fallback image for either of the 2 kernels I run for arch.
I think after a grub2 upgrade first you have to install new grub to MBR and then update grub config. -- /ronny
On 03/28/2012 12:42 AM, Ronny Karrestad wrote:
På Tue, 27 Mar 2012 23:43:36 -0000, skrev Don deJuan <donjuansjiz@gmail.com>:
On 03/26/2012 03:08 AM, Paul Gideon Dann wrote:
On Monday 26 Mar 2012 02:18:53 Saurav Modak wrote:
Have you tried manually adding it in grub.cfg BTW?
Editing grub.cfg is a naughty thing to do with Grub2 :p The "correct" thing to do would be to add the fallback to /etc/grub.d/41_custom. However, Grub previously automatically detected the fallback correctly. I'm wondering why it doesn't now.
Paul
After a kernel panic on boot after todays kernel update (unrelated) while doing things to get back up and running I just realized this as well. I do not have a fallback image for either of the 2 kernels I run for arch.
I think after a grub2 upgrade first you have to install new grub to MBR and then update grub config.
I had no issue installing grub2, I only noticed it was missing the fallback image when I needed it as both my kernel and arch paniced on boot so was going to try one of those. I ran grub-mkconfig after the install and it does not find them. I just tried running os-prober and grub-mkconfig again a couple hours ago with still not luck so just added them in myself. Also the stated kernel panic and grub2 install did not happen at the same time I only noticed it was missing due to the panic, grub2 was done each time it came from the repo's that day.
On Wed, Mar 28, 2012 at 12:51 PM, Don deJuan <donjuansjiz@gmail.com> wrote:
On 03/28/2012 12:42 AM, Ronny Karrestad wrote: I had no issue installing grub2, I only noticed it was missing the fallback image when I needed it as both my kernel and arch paniced on boot so was going to try one of those. I ran grub-mkconfig after the install and it does not find them. I just tried running os-prober and grub-mkconfig again a couple hours ago with still not luck so just added them in myself. Also the stated kernel panic and grub2 install did not happen at the same time I only noticed it was missing due to the panic, grub2 was done each time it came from the repo's that day.
Can you show us output of following commands: ls /boot grub-mkconfig -o /boot/grub/grub.cfg -- Kirill Churin Jabber: reflexing@reflexing.ru
On 03/28/2012 12:00 AM, Kirill Churin wrote:
On Wed, Mar 28, 2012 at 12:51 PM, Don deJuan<donjuansjiz@gmail.com> wrote:
On 03/28/2012 12:42 AM, Ronny Karrestad wrote: I had no issue installing grub2, I only noticed it was missing the fallback image when I needed it as both my kernel and arch paniced on boot so was going to try one of those. I ran grub-mkconfig after the install and it does not find them. I just tried running os-prober and grub-mkconfig again a couple hours ago with still not luck so just added them in myself. Also the stated kernel panic and grub2 install did not happen at the same time I only noticed it was missing due to the panic, grub2 was done each time it came from the repo's that day.
Can you show us output of following commands:
ls /boot grub-mkconfig -o /boot/grub/grub.cfg
ls /boot grub lost+found initramfs-linux-fallback.img memtest86+ initramfs-linux.img root initramfs-linux-qosmio-fallback.img vmlinuz-linux initramfs-linux-qosmio.img vmlinuz-linux-qosmio Generating grub.cfg ... Found linux image: /boot/vmlinuz-linux-qosmio grep: /etc/os-release: No such file or directory Found initrd image: /boot/initramfs-linux-qosmio.img grep: /etc/os-release: No such file or directory grep: /etc/os-release: No such file or directory Found linux image: /boot/vmlinuz-linux grep: /etc/os-release: No such file or directory Found initrd image: /boot/initramfs-linux.img grep: /etc/os-release: No such file or directory grep: /etc/os-release: No such file or directory grep: /etc/os-release: No such file or directory Found memtest86+ image: /boot/memtest86+/memtest.bin No volume groups found Found Windows 7 (loader) on /dev/sda1 I did not notice the grep output the other times, I think I saw something on the boards about that.
On Wed, Mar 28, 2012 at 1:30 PM, Don deJuan <donjuansjiz@gmail.com> wrote:
ls /boot grub lost+found initramfs-linux-fallback.img memtest86+ initramfs-linux.img root initramfs-linux-qosmio-fallback.img vmlinuz-linux initramfs-linux-qosmio.img vmlinuz-linux-qosmio
Generating grub.cfg ... Found linux image: /boot/vmlinuz-linux-qosmio grep: /etc/os-release: No such file or directory Found initrd image: /boot/initramfs-linux-qosmio.img grep: /etc/os-release: No such file or directory grep: /etc/os-release: No such file or directory Found linux image: /boot/vmlinuz-linux grep: /etc/os-release: No such file or directory Found initrd image: /boot/initramfs-linux.img grep: /etc/os-release: No such file or directory grep: /etc/os-release: No such file or directory grep: /etc/os-release: No such file or directory Found memtest86+ image: /boot/memtest86+/memtest.bin No volume groups found Found Windows 7 (loader) on /dev/sda1
I did not notice the grep output the other times, I think I saw something on the boards about that.
Obviously, there are no fallback kernels, so grub-mkconfig doesn't find it. -- Kirill Churin Jabber: reflexing@reflexing.ru
On 03/28/2012 12:49 AM, Kirill Churin wrote:
On Wed, Mar 28, 2012 at 1:30 PM, Don deJuan<donjuansjiz@gmail.com> wrote:
ls /boot grub lost+found initramfs-linux-fallback.img memtest86+ initramfs-linux.img root initramfs-linux-qosmio-fallback.img vmlinuz-linux initramfs-linux-qosmio.img vmlinuz-linux-qosmio
Generating grub.cfg ... Found linux image: /boot/vmlinuz-linux-qosmio grep: /etc/os-release: No such file or directory Found initrd image: /boot/initramfs-linux-qosmio.img grep: /etc/os-release: No such file or directory grep: /etc/os-release: No such file or directory Found linux image: /boot/vmlinuz-linux grep: /etc/os-release: No such file or directory Found initrd image: /boot/initramfs-linux.img grep: /etc/os-release: No such file or directory grep: /etc/os-release: No such file or directory grep: /etc/os-release: No such file or directory Found memtest86+ image: /boot/memtest86+/memtest.bin No volume groups found Found Windows 7 (loader) on /dev/sda1
I did not notice the grep output the other times, I think I saw something on the boards about that.
Obviously, there are no fallback kernels, so grub-mkconfig doesn't find it.
ok well not obvious to me as they were there and working before grub2's most recent 2 updates that came through. Now no longer, sorry if its just noise
On Wed, Mar 28, 2012 at 1:52 PM, Don deJuan <donjuansjiz@gmail.com> wrote:
ok well not obvious to me as they were there and working before grub2's most recent 2 updates that came through. Now no longer, sorry if its just noise
You can try to regenerate them: mkinitcpio -p linux mkinitcpio -p linux-qosmio grub-mkconfig -o /boot/grub/grub.cfg -- Kirill Churin Jabber: reflexing@reflexing.ru
On 03/28/2012 01:00 AM, Kirill Churin wrote:
On Wed, Mar 28, 2012 at 1:52 PM, Don deJuan<donjuansjiz@gmail.com> wrote:
ok well not obvious to me as they were there and working before grub2's most recent 2 updates that came through. Now no longer, sorry if its just noise
You can try to regenerate them: mkinitcpio -p linux mkinitcpio -p linux-qosmio grub-mkconfig -o /boot/grub/grub.cfg
i did a link to /etc/arch-release and solved the grep message. I ran mkinitcpio again like you said and still the same in boot. Neither the arch kernel or mine is generating the fallback vmlinuz. Maybe it is a different problem in relation to today's I think it was mkinitcpio update. Guess mines is unrelated to OP.
On Wed, Mar 28, 2012 at 13:34, Don deJuan <donjuansjiz@gmail.com> wrote:
On 03/28/2012 01:00 AM, Kirill Churin wrote:
On Wed, Mar 28, 2012 at 1:52 PM, Don deJuan<donjuansjiz@gmail.com> wrote:
ok well not obvious to me as they were there and working before grub2's most recent 2 updates that came through. Now no longer, sorry if its just noise
You can try to regenerate them: mkinitcpio -p linux mkinitcpio -p linux-qosmio grub-mkconfig -o /boot/grub/grub.cfg
i did a link to /etc/arch-release and solved the grep message. I ran mkinitcpio again like you said and still the same in boot. Neither the arch kernel or mine is generating the fallback vmlinuz. Maybe it is a different problem in relation to today's I think it was mkinitcpio update. Guess mines is unrelated to OP.
On Wednesday 28 Mar 2012 13:45:46 Keshav P R wrote:
https://bugs.archlinux.org/task/29037?getfile=8444
- Keshav
This looks like exactly what is needed; thank you. Paul
On Wednesday 28 Mar 2012 13:49:15 Kirill Churin wrote:
Obviously, there are no fallback kernels, so grub-mkconfig doesn't find it.
There never were any fallback kernels. The term "fallback" has always referred to the initramfs image, yet it used to detect them. Paul
participants (7)
-
Don deJuan
-
Josh Silard
-
Keshav P R
-
Kirill Churin
-
Paul Gideon Dann
-
Ronny Karrestad
-
Saurav Modak