grub2 = beta?

Gene Heskett gene.heskett at
Fri Dec 11 14:39:24 UTC 2009

On Friday 11 December 2009, Gene Heskett wrote:
>On Friday 11 December 2009, Gene Heskett wrote:
>>On Friday 11 December 2009, Goh Lip wrote:
>>>Gene Heskett wrote:
>>>> On Thursday 10 December 2009, Goh Lip wrote:
>>>> And how was that accomplished?  I have no qualms about using a newer
>>>> grub, if the docs are sufficient to mean it can be easily configured by
>>>> the likes of an old, retired television engineer like me.  If it takes
>>>> voodoo charms & black magic, then I'm not all that interested.
>>>The simplest (non-voodoo and don't require a television engineering
>>>certificate, just maybe rocket science  :) )method is just
>>>sudo apt-get install grub-pc
>I do not have those installed for F10.  I'll see if grub-pc is available.
>No, but a grub2 is available that installs all the grub2 stuff in
>/boot/grub2, and makes a new entry in grub/grub.conf that names it as a
>kernel to load & run.  This could be fun.  It spent about 5 minutes
> hammering on every drive in this box so I'm going to look around and see
> what else it did before retrying a reboot.
Ok, that apparently worked, it brought up a new, black & white menu with my 
old default boot at the top of the list, and then booted it before I had a 
chance to scroll up and down to see what was available.  What do I edit to 
extend that pause time to say 15 seconds?

Looking at /boot/grub2/grub.cfg, it added every old kernel version in my F10 
history, many of which have been removed from the /boot partition because 
anaconda will not allow a more than 200meg /boot.  In other words, a lot of 
trash that won't work is probably in the grub2 menu.  If I go clean all that 
up, how do it restore this to something sane, remove it and reinstall it 
again?  That seems a bit of a kludge.

Also, I note that in a quick scan, it didn't find either the mint 8 or 
mandriva installs although it did hammer on all drives for quite a while 
>>>Watch out during installation when it will initially use chainload, then
>>>further instructions will follow. Follow through to finish.
>>>> I just ran into grub2 again.  Running F10 normally here, but just
>>>> installed Linux Mint 8, 32 bit version on /dev/sdb, which is derived
>>>> from Ubuntu 9.10
>>>> I have this in my /dev/sda1(/boot for F10)/grub/grub.conf:
>>>> title Mint Linux 8 32 bit (from /dev/sdb)
>>>> 	rootnoverify	(hd1,0)
>>>> 	makeactive
>>>> 	chainloader +1
>>And I just found I didn't have a space between chainloader and +1.
>Ok, with the space in there, I now get an error 13, invalid format.  And it
>times out in about 5 seconds and loops back to the sstarting menu from
>/dev/sda, and grub-0.97. I purposely made both Mint partitions /boot and /
>ex3 filesystems so there would not be the sort of thing where F12
> apparently can only be booted from an ext4 system thanks to fedora's
> "forking" of grub-0.97 without even changing the version number.

Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.

Today's scientific question is: What in the world is electricity?

And where does it go after it leaves the toaster?
		-- Dave Barry, "What is Electricity?"

More information about the kubuntu-users mailing list