How to have a graphical GRUB (Updated Package Available)
How to
Hooray
I wish I had spotted this prior to setting up my sons system. This looks awesome I will be trying it out this week. The standard Grub sucks.
Will let you know how it goes. I learnt quickly what not to do in a grub menu, and have his system set up with multiple puplets to choose from. Now I can add a bit of bling for him
Cheers for this
Kazzamozz
I wish I had spotted this prior to setting up my sons system. This looks awesome I will be trying it out this week. The standard Grub sucks.
Will let you know how it goes. I learnt quickly what not to do in a grub menu, and have his system set up with multiple puplets to choose from. Now I can add a bit of bling for him
Cheers for this
Kazzamozz
Fully agree with all the support for this - mainstream it!!
I have called for it's inclusion into 4.4CE
Catdude, do you know if it can be modified to add a list of SFS's to be loaded, maybe as a sub-menu?
I have suggested it in that thread....
4.4CE here
http://www.murga-linux.com/puppy/viewto ... &start=105
Aitch
I have called for it's inclusion into 4.4CE
Catdude, do you know if it can be modified to add a list of SFS's to be loaded, maybe as a sub-menu?
I have suggested it in that thread....
4.4CE here
http://www.murga-linux.com/puppy/viewto ... &start=105
Aitch
Hi
@ droope & kazzamozz
Thanks, you are both very welcome.
In fact i don't think i fully understand the question,
surely Puppy controls what .sfs files gets loaded, doesn't he ?
CatDude
.
@ droope & kazzamozz
Thanks, you are both very welcome.
I honestly wouldn't have a clue about that mate.Aitch wrote: Catdude, do you know if it can be modified to add a list of SFS's to be loaded, maybe as a sub-menu?
In fact i don't think i fully understand the question,
surely Puppy controls what .sfs files gets loaded, doesn't he ?
CatDude
.
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
Hello Roger Hunter
Could you also provide the global section from your menu.lst
Also, do you have a message file: /boot/grub/whatever-message-file
if so, which one is it. (please provide the link)
What Puppy are you using and what kind of install (just so i can do a test, using the same.)
CatDude
.
What .pet package did you use ? (please provide the link)Roger Hunter wrote: I have the same problem. I installed the .pet, reinstalled grub, reboot, and get the same old menu.lst as before.
It looks like gfxmenu isn't being executed.
Could you also provide the global section from your menu.lst
Code: Select all
# Start GRUB global section
What is in this section here
# End GRUB global section
if so, which one is it. (please provide the link)
What Puppy are you using and what kind of install (just so i can do a test, using the same.)
CatDude
.
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
catdude;
gfxmenu /boot/grub/message.pup2
The others are on sdb
My PC is a Compaq Presario,2.80GHz/1Gb RAM/80Gb/250Gb drives
Roger
It's the link on the first post of this thread.What .pet package did you use ? (please provide the link)
No, I've already reset it, sorry. But it was a copy of your example.Could you also provide the global section from your menu.lst
gfxmenu /boot/grub/message.pup2
It's your message.pup2 on /boot/grub of sda3Also, do you have a message file: /boot/grub/whatever-message-file
if so, which one is it. (please provide the link)
I'm multibooting several puppies plus Win XP. Puppy 4.3 is the master boot puppy on sda3.What Puppy are you using and what kind of install (just so i can do a test, using the same.)
The others are on sdb
My PC is a Compaq Presario,2.80GHz/1Gb RAM/80Gb/250Gb drives
Roger
Hello Roger
One for the original package: grub-gfxboot-for-puppy.tar.gz
and another to the NEW updated package: grub-gfxboot-for-puppy-updated.tar.gz
Message files: message.pup1 to message.pup16 (inclusive)
will not work with the package: grub-gfxboot-for-puppy.tar.gz
CatDude
.
There are two links in that first post.Roger Hunter wrote: It's the link on the first post of this thread.
One for the original package: grub-gfxboot-for-puppy.tar.gz
and another to the NEW updated package: grub-gfxboot-for-puppy-updated.tar.gz
Well, if you happened to use the original package, then that is why is did not work.Roger Hunter wrote: It's your message.pup2 on /boot/grub of sda3
Message files: message.pup1 to message.pup16 (inclusive)
will not work with the package: grub-gfxboot-for-puppy.tar.gz
You need to use the updated package.PLEASE NOTE: These messages will not work with my previous .pet package.
They are too big.
CatDude
.
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
Hi
i have made a few changes to my original post, in an effort to make things easier to follow.
Maybe you could take a look and see if things are any better.
I have hopefully removed all references from this thread that refer to my original package,
so there is now only the one package available.
CatDude
.
I am sorry to hear that,Roger Hunter wrote: Never mind. I gave up. Switched the main boot puppy to Puppy 4.3, thus losing the graphics menu stuff.
i have made a few changes to my original post, in an effort to make things easier to follow.
Maybe you could take a look and see if things are any better.
I have hopefully removed all references from this thread that refer to my original package,
so there is now only the one package available.
CatDude
.
Last edited by CatDude on Sat 05 Dec 2009, 20:26, edited 1 time in total.
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
CatDude;
Sorry, no good.
Instead of the menu I get a grub prompt.
I'm using Puppy 4.3 in sda3 for the master boot puppy
Here's the menu.lst
Roger
Sorry, no good.
Instead of the menu I get a grub prompt.
I'm using Puppy 4.3 in sda3 for the master boot puppy
Here's the menu.lst
Code: Select all
# GRUB configuration file '/boot/grub/menu.lst'.
# generated by 'grubconfig'. Sun Dec 6 09:18:38 2009
#
# The backup copy of the MBR for drive '/dev/sda' is
# here '/boot/grub/mbr.sda.16780'. You can restore it like this.
# dd if=/boot/grub/mbr.sda.16780 of=/dev/sda bs=512 count=1
#
# Start GRUB global section
timeout 30
default 3
color light-gray/blue black/light-gray
gfxmenu /boot/grub/pupsta1
# End GRUB global section
# Other bootable partition config begins
title Windows (on /dev/sda1)
rootnoverify (hd0,0)
makeactive
chainloader +1
# Other bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sda3)
root (hd0,2)
kernel /boot/vmlinuz root=/dev/sda3 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sdb3)
root (hd1,2)
kernel /boot/vmlinuz root=/dev/sdb3 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sdb6)
root (hd1,5)
kernel /boot/vmlinuz root=/dev/sdb6 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sdb7)
root (hd1,6)
kernel /boot/vmlinuz root=/dev/sdb7 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sdb8)
root (hd1,7)
kernel /boot/vmlinuz root=/dev/sdb8 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sdb9)
root (hd1,8)
kernel /boot/vmlinuz root=/dev/sdb9 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sdb10)
root (hd1,9)
kernel /boot/vmlinuz root=/dev/sdb10 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/sdb11)
root (hd1,10)
kernel /boot/vmlinuz root=/dev/sdb11 ro vga=normal
# Linux bootable partition config ends
title Install GRUB to floppy disk (on /dev/fd0)
pause Insert a formatted floppy disk and press enter.
root (hd0,2)
setup (fd0)
pause Press enter to continue.
title Install GRUB to Linux partition (on /dev/sda3)
root (hd0,2)
setup (hd0,2)
pause Press enter to continue.
title - For help press 'c', then type: 'help'
root (hd0)
title - For usage examples, type: 'cat /boot/grub/usage.txt'
root (hd0)
Hello Roger
There has been a lot of posts recently concerning inode sizes
and Puppies GRUB being incompatible with partitions with an inode size of 256
Here is just one such post
I am afraid to say, that my package will not work with such partitions.
From my tests,
GParted in both Puppy-4.30 and Puppy-4.31 creates partitions with an inode size of 256
GParted in both Puppy-4.20 and Puppy-4.21 creates partitions with an inode size of 128
in fact both of these versions (4.20 and 4.21) already have my graphical grub installed in them.
So if you used either of those to create your partitions and install GRUB,
you then only need to change the boot message to that which you wish to use.
As to my earlier comment "That is odd"
Well, i used Puppy-4.31 (from LiveCD with puppy pfix=ram)
to totally erase my hard drive, then create 3 partitions (1 for GRUB, 1 for Puppy-4.31 frugal, and a SWAP).
I then installed my package and copied the message file to /boot/grub
and made the necessary edit to the menu.lst
When i rebooted (i created a save file) i was greeted to the graphical GRUB boot screen (see image below)
but i was unable to boot up Puppy, i got an error message:
that is what i meant by odd.
Anyway i think this could be the reason you are having trouble getting this to work,
i have add to my original post to reflect these issues.
Hope this helps
CatDude
.
That is odd. (i'll explain why later)Roger Hunter wrote: Sorry, no good.
Instead of the menu I get a grub prompt.
There has been a lot of posts recently concerning inode sizes
and Puppies GRUB being incompatible with partitions with an inode size of 256
Here is just one such post
I am afraid to say, that my package will not work with such partitions.
From my tests,
GParted in both Puppy-4.30 and Puppy-4.31 creates partitions with an inode size of 256
GParted in both Puppy-4.20 and Puppy-4.21 creates partitions with an inode size of 128
in fact both of these versions (4.20 and 4.21) already have my graphical grub installed in them.
So if you used either of those to create your partitions and install GRUB,
you then only need to change the boot message to that which you wish to use.
As to my earlier comment "That is odd"
Well, i used Puppy-4.31 (from LiveCD with puppy pfix=ram)
to totally erase my hard drive, then create 3 partitions (1 for GRUB, 1 for Puppy-4.31 frugal, and a SWAP).
I then installed my package and copied the message file to /boot/grub
and made the necessary edit to the menu.lst
When i rebooted (i created a save file) i was greeted to the graphical GRUB boot screen (see image below)
but i was unable to boot up Puppy, i got an error message:
Code: Select all
Error 2: Bad file or directory type
Press any key to continue...
Anyway i think this could be the reason you are having trouble getting this to work,
i have add to my original post to reflect these issues.
Hope this helps
CatDude
.
- Attachments
-
- gfxmenu.jpg
- (47.95 KiB) Downloaded 1200 times
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41
CatDude;
That solved the problem.
I had a CD of BoxPup 421 so I deleted sda3, made a new one wit BoxPup, installed BoxPup in it and there was the graphic menu.
Happily, I did not have to recreate the sdb partitions so now I'm back in business except that MacPup won't boot. Error is bad file or directory but that's another thread.
Thanks a bunch. Things look much nicer now.
Roger
That solved the problem.
I had a CD of BoxPup 421 so I deleted sda3, made a new one wit BoxPup, installed BoxPup in it and there was the graphic menu.
Happily, I did not have to recreate the sdb partitions so now I'm back in business except that MacPup won't boot. Error is bad file or directory but that's another thread.
Thanks a bunch. Things look much nicer now.
Roger
Hello Roger
because that Error looks awfully familiar.
CatDude
.
Glad you eventually got it sorted.Roger Hunter wrote: That solved the problem.
The partition that Macpup resides on does not have an inode size of 256 by any chance does it ?Roger Hunter wrote: Happily, I did not have to recreate the sdb partitions so now I'm back in business except that MacPup won't boot. Error is bad file or directory but that's another thread.
because that Error looks awfully familiar.
CatDude
.
Hello vellowax
my package will not work with ext4 partitions.
but i wouldn't mind getting my hands on a copy of it, if you ever manage to recall where you got it from.
CatDude
.
As i state at the top of the first post in this thread,vellowax wrote: For some reason, I should use ext4 as filesystem for my partition, is there any available package, so that my NOP431 have a graphical grub too?
my package will not work with ext4 partitions.
I don't know anything about that .pet,vellowax wrote: I was download and installed the gfx-boot-xxx.ext4-patch.pet ( I have forgotten where i was downloaded that pet ) but still won't work.
but i wouldn't mind getting my hands on a copy of it, if you ever manage to recall where you got it from.
CatDude
.
thanks catdude for your concern about my case, i think someone else might have the same problem,
i found this link.
http://mirror.internode.on.net/pub/pupp ... ackages-4/
i also attach the package that i intend.
i found this link.
http://mirror.internode.on.net/pub/pupp ... ackages-4/
i also attach the package that i intend.
-
- Posts: 218
- Joined: Sat 05 Jan 2008, 17:41