Puppy Linux Discussion Forum

[CatDude]

Hello All

Edit:

The original package i created has now been removed.
The one below is a lot better anyway.

Edit 2:

I have created a new package grub-gfxboot-ext4-and-inode256-compatible.tar.gz (i recommend that you use this one.)
it has support for ext4 partitions, partitions with an inode size of 256, and most importantly a gfxmenu..

Edit 3:

Updated Links:
http://puppylinuxstuff.meownplanet.net/catdude/grub-stuff/grub-gfxboot-ext4-and-inode256-compatible.tar.gz
http://www.smokey01.com/CatDude/grub-stuff/grub-gfxboot-ext4-and-inode256-compatible.tar.gz

Important Note: (This applies to: grub-gfxboot-for-puppy-updated.tar.gz only.)

If you are using partitions formatted as ext4
Then this package is of no use to you, forget it.
this particular version of GRUB cannot boot anything on those partitions.

Also, if you have used either Puppy-4.30 or Puppy-4.31 to create your partitions,
then this package WILL NOT work.
If you used a different linux distro altogether to create your partitions,
then this package MAY NOT work.
Read this post for the reason why, and how to check your own partitions
This package will not work with such partitions (it requires an inode size of 128)

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 you may just want to use one of those rather than this package.

######################################################

After reading this: How to use gfxmenu in grub?
I just had to look into it a little

What i ended up doing is, i took the files from Mepis (Thankyou Mepis )

All of the following is done entirely at your own risk.
Please don't blame me if things go pear shaped. (they shouldn't)

####################################################
# PLEASE BACKUP YOUR menu.lst BEFORE DOING ANYTHING SUGGESTED BELOW. #
####################################################

The following was tested in both:

TEENpup-2008 (FULL install)
and
Puppy Watchdog-v1.1 (Frugal install)

On two different computers.
(It has since been tested on a lot more Puppy versions including: 3.01, 4.00, 4.20, 4.21, 4.31)

In the following Steps,
if you use the grub-gfxboot-ext4-and-inode256-compatible.tar.gz (recommended)
then substitute grub-gfxboot_0.97-36mepis1.pet wherever it mentions grub-gfxboot_0.97-18mepis1.pet

Step 1.

Download the attached file, grub-gfxboot-for-puppy-updated.tar.gz or better yet, use grub-gfxboot-ext4-and-inode256-compatible.tar.gz instead.
and extract it to a directory somewhere.
This file includes the following:


grub-gfxboot_0.97-18mepis1.pet
pupsta1 (note: that is pupsta with a number 1. This is a new one created from the Suse source files.)
pupsta1.jpg (a screengrab, may be useful as a guide if you create your own message file.)
README.txt (installation instructions, and how to create your own message file.)

Step 2.

Make sure you have made a backup of your menu.lst
You may want to rename it to original.menu.lst or good.menu.lst,
anything you like really just to save any confusion in Step 5.
For the purpose of this howto, we will rename it to original.menu.lst
Save it to: /root/my-documents

Now install the pet package: grub-gfxboot_0.97-18mepis1.pet
(Just click on it to install it)

Step 3.

Now Re-install GRUB via the menu (System > Grub Bootloader Config)
to wherever it was installed initially.

##### When asked, i ALWAYS install to the MBR (Master Boot Record) #####
i don't know if it makes a difference or not, it is just MY preference.

Just do whatever it was that worked for you previously.

Step 4.

Now copy the file: pupsta1
to: /somewhere/boot/grub
Where somewhere = the hard drive partition you installed grub to.

Step 5.

Amend your menu.lst (The new one)

Go to the directory where you installed GRUB: somewhere/boot/grub
Where somewhere = the hard drive partition you installed grub to.

Now right click on the file menu.lst and choose Open As Text
Next go to /root/my-documents
and right click on original.menu.lst and choose Open As Text

You now have both menu.lst files open in the text editor.

Select the original.menu.lst file in the text editor,
now select (highlight) with the mouse EVERYTHING BELOW
from and including the line that says:


Code:

# Start GRUB global section


(Basically everything EXCEPT the first 6 or so lines, that look similar to below)


Code:

# GRUB configuration file '/boot/grub/menu.lst'. # generated by 'grubconfig'.  Mon Sep  7 11:40:59 2009 # # The backup copy of the MBR for drive '/dev/hda' is # here '/boot/grub/mbr.hda.21367'.  You can restore it like this. # dd if=/boot/grub/mbr.hda.21367 of=/dev/hda bs=512 count=1


With everything still selected (highlighted)
Press Ctrl + C
to copy it all.

Now select the menu.lst file in the text editor,
and select the same as in the previous file.
EVERYTHING BELOW and including the line that says:


Code:

# Start GRUB global section


With everything still selected (highlighted)
Press Delete

Now
Press Ctrl + V
to paste in what you copied from the file original.menu.lst

Now
Press Ctrl + S
to save your changes

Finally edit the global section
to look like below.

Here's how mine looks:


Code:

# Start GRUB global section timeout 10 default 3 color light-gray/blue black/light-gray gfxmenu /boot/grub/pupsta1 # End GRUB global section


Obviously if you are using a different message file, then make the appropriate change to the gfxmenu line.
Also make any necessary changes to the timeout and default (use whatever was in your original working menu.lst)

Once again, save your changes
Press Ctrl + S

Close both files in the text editor
then close the text editor (and any other windows you may have open)
and reboot.

You should now see similar to the picture pupsta1.jpg below.

##########################################################
If you wanted, instead of using the message file pupsta1
you could use one of the other message files shown below: (they have all been updated and are now configurable.)

Click on an image to see larger image.

message.pup1.............message.pup2.............message.pup3.............message.pup4


message.pup5.............message.pup6.............message.pup7.............message.pup8


message.pup9.............message.pup10...........message.pup11...........message.pup12


message.pup13...........message.pup14...........message.pup15...........message.pup16

You can download them here: puppylinuxstuff.meownplanet.net

You can also find some more in this thread (which explains how to create your own message files) : Message files for the GRUB gfxmenu

There is also a flash howto on how to create your own message here for anyone that wishes to view it. grub-message-howto
It is based on one of the older message files above, not the new one.

For the above links:
User Name = puppy
Password = linux

Thanks to Caneri for providing the space for them. (Cheers Eric)
New thanks should go to Russoodle for providing space now that Erics site no longer exists.
New thanks go to dejan555 for providing space for the above image files. (cheers mate, i hope you don't mind )

##########################################################
Please Note:

Recently i managed to compile a new GRUB gfxboot message, from the Suse source files.
This new message file is configurable, whereas the older ones i had posted were not.

Amongst other things,
we can change:

The colour of the text.
The position of the menu entries on the grub boot screen.
How many entries are displayed before needing to scroll.
The position of the Boot Options text.

The message file pupsta1 included in the package: grub-gfxboot-for-puppy-updated.tar.gz
is based on this new message file.

So if you fancy creating your own message file, (which isn't as difficult as you may think.)
i suggest using this as the basis of your new message file.

Enjoy

CatDude
.
Note to self:
293 previous
.

[prit1]

@CatDude: Thanks for the howto. I will try this out as soon as I get sometime. Maybe within a couple of days and post back. Thanks a lot again.

[accessdenied]

Catdude, this works perfectly!!!

Configured on Muppy 8.2 and looks great...

I curious on how to change/edit the picture contents as I have the same issue as you when the Linux title is too long and goes past the right side of the screen.

Thanks for sharing!!!!

[CatDude]

Hello accessdenied

[Lobster]

Very nice project . . .
Booting up into very diverse Puppys
would be great for many users

What is the code like? What is it based on?
Could it be used in Dingo or Lassie for boot options (screen size, keyboard etc) or is it too big for this?

[CatDude]

Hello Lobster

[Lobster]

[CatDude]

Sorry Lobster

My bad, i was refering to your post in this thread: http://www.murga-linux.com/puppy/viewtopic.php?t=24871&start=120

[accessdenied]

Catdude, thanks for the info. I'll read up on the readme file and see if I can manipulate the picture and shift the puppy logo more to the left to make room for the menu text..

By the way, I like the color scheme on your new and improve picture.
Can you upload the message.puppy file for that if you don't mind?

Thanks again.

[CatDude]

Hello again accessdenied

[Lobster]

[CatDude]

[Tui]

Hi all, I like the idea of the GUI opening window. I think I
have followed the instructions through but can't get the GRUB to open
with a screen like the screenshot.

Starting, I am using the Puppy version EDUPUP, this has the kernel V2.6.21.7

I have got the GRUB installed on a small 25mb part hda2, hda1 being
swap partition.

What I have done, downloaded the file grub-gfxboot-for-puppy.tar.gz
into a directory called NEWGRUB.

Expanded to get :

grub gfxboot_0.97-5_i386.pet
message.puppy
message.suse
readme

then expand the (dot)pet

to where did it go, I don't know ?

what does the: grub gfxboot_0.97-5_i386.pet expand into ?

Only file I could find relating was a file called : grub-gfxboot_0.97-5_i386.files, and located in /root/.packages !

So for me it looks like a bit of a mess!

After doing the edit in menu.1st as suggested, and the adding
of gfxmenu/boot/grub/ after timeout and the #end grub, the rem color
etc. Is the gfxmenu/boot a sub dir somewhere ?

So after a reboot the only thing changed was no more background
BLUE colour, just the text and white border.

How do I solve the problem?

Help help please thanks

Tui

[reddawg]

Catdude -

I really appreciate the notes and the How-To. I am a Linux newbie and was able to follow this easily.

I have since created a number of graphical grub screens. The biggest challenge has been to keep the image "back.jpg" down to around 70K or less. I did receive a couple of errors stating that the message was too large. I have since ensured that before I reboot the message file must be less than 170K and everything works great.

I now have different graphical grub boot screens for my laptop (puppy 3.01) and desktop (Pizza pup 3.01)

Thank You / Windows is toast...

[CatDude]

Hello Tui

Sorry to here that you are having trouble with this.

You did make a copy of your original menu.lst (its best that you do)

Reading your post, i dont see any mention of you RE-INSTALLING GRUB
after installing the pet package. ( in your case re-install it to /dev/hda2 )

Refer to my original post, and try again from Step 3.

If you really want to know where and what was installed via the pet package,
create a copy of it, but change the .pet to .tgz
Then click on it, and it will open with XArchive
click on Select All then Extract
You will now have a new directory called grub-gfxboot_0.97-5_i386
which will show you where everything is being installed to.

Hope you get it working.

To reddawg

Glad to here of your success with it.
Like you have found already, just keep the final message file below 170K and things should be OK.

CatDude
.