| 1 |
Neil Bothwick wrote: |
| 2 |
> On Tue, 17 Feb 2009 06:17:07 +0200, Nikos Chantziaras wrote: |
| 3 |
> |
| 4 |
>> I've no idea how it broke, but after an emerge --sync, a kernel |
| 5 |
>> (gentoo-sources) update was there. After I compiled the kernel, I did |
| 6 |
>> the usual "make modules_install && make install". I edited grub.conf |
| 7 |
>> only to the point of changing the booted kernel to the |
| 8 |
>> new one (just a matter of changing -r1 to -r2 at the end of the kernel |
| 9 |
>> filename). I reboot, Grub stops working. It just displays "GRUB" and |
| 10 |
>> hangs there. |
| 11 |
> |
| 12 |
> Could you have inadvertently made more of a change to grub.conf than |
| 13 |
> that? Grub is notoriously fragile when it comes to its config file? |
| 14 |
|
| 15 |
No, the change was a simple change of 1 byte ("1" -> "2"). |
| 16 |
|
| 17 |
|
| 18 |
> Why did you edit it in the first place? As you used make install,you will |
| 19 |
> have symlinks from vmlinuz and vmlinuz.old to the new and previous |
| 20 |
> kernels. Use these in GRUB and there's no need to edit anything. |
| 21 |
|
| 22 |
That won't work for me because I keep two different kernels (one for |
| 23 |
vmware and one for native) and I sometimes rebuild one of them after |
| 24 |
reconfiguring. With that approach I would end up with the "Native" Grub |
| 25 |
entry trying to boot the vmware kernel. |
| 26 |
|
| 27 |
One thing that could be at fault is that I had grub installed into hd0,2 |
| 28 |
(sda3) which is an ext4 partition. /boot is sda4 and is ext3. But I'm |
| 29 |
sure grub should work no matter where you install it. I can even |
| 30 |
install it on sda1 which is NTFS and it works. Hell, I can even install |
| 31 |
it on the swap partition. |
| 32 |
|
| 33 |
I guess the reason it broke will remain a mystery :P |
Archives