Howto : GfxBoot ( Grub like suse )

[raul_]

Kudos.

Awesome!

[raul_]

Oops. Double post. Don't know how that happened =\ sorry

[Beastboy26]

Step1:
download http://quasarfreak.googlepages.com/grub-gfxboot_0.97-5_i386.deb

Step2:
Download a 'theme'. See the first post (http://ubuntuforums.org/showpost.php?p=1212505&postcount=1) for this.

Step3:
Remove the old GRUB.
Open a terminal and type:
sudo apt-get remove grub

Step4:
Install gfxboot. Find the downloaded .deb and dubbleclick it. A graphical installer will take over.

Step5:
We are going to move the 'theme' we just downloaded.
Open a terminal, cd to the folder where you downloaded the theme and type:
sudo cp message.suse /boot/grub/
Offcourse "message.suse" can be replaced by the one you downloaded

Step6:
Backup menu.lst and edit the original to use gfxboot.
sudo cp /boot/grub/menu.lst /boot/grub/menu.lst_backup
sudo gedit /boot/grub/menu.lst
This will open up a textfile.
Insert a new first line that says:
gfxmenu /boot/grub/message.suse
Once again: the message.suse can be replaced

Step7:
sudo su
grub
Now you are in the "grub-console".
grub> find /boot/grub/stage1
(hd0,1) # this is my output, yours may be different, you may even get multiples if you've lots of versions of linux.
grub> root (hd0,1)
grub> setup (hd0,1)
grub> quit

Now we are back in the normal console.
Just 1 more command to go...
take a look at the output. it has the form: (hdx,y)
the x:
0 =a
1 = b
2 = c
....

grub-install /dev/hdxy

An example:
*) if your output was (hd0,1) then what you have to type is: grub-install /dev/hda1
*) if your output was (hd1,6) then what you have to type is: grub-install /dev/hdb6

Get the idea?

Step8:
reboot and enjoy your gfxboot :)


I followed these steps up to the point where you use the command

grub-install /dev/hda2 #hda2 is what i got from the grub> find /boot/grub/stage1

instead i had to use

grub-install /dev/sda

beause i have a serial ATA hdd ??? anyways it worked ... except for one minor inconvenience... when i try to boot into windoze xp , it just loops back to the grub menu.... any ideas?

[Malac]

I followed these steps up to the point where you use the command

grub-install /dev/hda2 #hda2 is what i got from the grub> find /boot/grub/stage1

instead i had to use

grub-install /dev/sda

beause i have a serial ATA hdd ??? anyways it worked ... except for one minor inconvenience... when i try to boot into windoze xp , it just loops back to the grub menu.... any ideas?
You should have done grub-install /dev/sda2You've over-written the Windows boot code. You need to run the fixboot/fixmbr fix from the recovery console.

[frying_fish]

I have recently just tried this gfxboot, I have gotten it to the stage where it is installed and will attempt to load. But for some unknown reason, no matter what I try and reference the message files as it refuses to load them, saying the file is missing.

Either trying the /boot/grub/message.suse (for suse message in this case) or (hd0,1)/grub/message.suse (as sugessted earlier in the thread) fails to work, I still get the "graphics file FOO missing" error

any help is appreciated

[rei_t_ex]

Followed the instructions in the first post verbatim. When doing:

grub> find /boot/grub/stage1
(hd0,0) # this was returned so I did:
grub> root (hd0,0)
grub> setup (hd0)

Everything went without a problem but when I rebooted, I got the same old GRUB.

Read further down the thread and saw bohboh having the same problem. Trying to follow the resolution ran:

sudo fdisk -l

and got something along the lines of

Device Boot Start End Blocks Id System
/dev/sda1 * 1 **** ******* 83 Linux
/dev/sda2 **** **** ******* 5 Extended
/dev/sda5 **** **** ******* 82 Linux swap / Solaris

Entered GRUB from the terminal again and tried:

grub> root (sda,1)

Error 23: Error while parsing number

grub> root (sda1,0)

Error 23: Error while parsing number

So I figured that this part was fine as per original instructions, and back in the terminal entered:

sudo grub-install /dev/sda1

It returned a message saying something to the extent of "installation was successful, no errors returned".

Then I rebooted again, only to find

GRUB Loading stage1.5.

GRUB loading. please wait...

And the system HANGS!!!

This is my first foray into Linux from the Apple world (I installed Ubuntu on an old laptop about a week ago), so perhaps I have done something very stupid. Any help would be much appreciated. I hope that I did not just kill the system completely...


Edit1
----------------------------------
Booted from my LiveCD, mounted the partition and restored the backed-up menu.lst. No effect on the problem - system still hangs at boot.


Edit2
----------------------------------
Booted from LiveCD and restored GRUB as per http://ubuntuforums.org/showthread.php?t=224351. Still no luck.

[Fabioamd87]

hi, is possible to use the theme in the repositories of ubuntu edgy?

how to change for example the suse theme in the ubuntu theme?

[kvonb]

Anyone tried this on Feisty yet? I'm having a rather odd problem in that Feisty doesn't seem to know what my hard disk is!

Grub reports it as /dev/hda and fdisk thinks it's /dev/sda!

Subsequently I cannot perform a grub-install as each device lists as "Not found or not a block device."

Very odd :confused:.

[Fabioamd87]

Feisty can't have it by default? :(

[tuxbear]

Can I get install GfxBoot on a AMD64 ??? All packages they I found are for i386 infrastructure.
It isn't possible to install that with dpkg.

I installed gfxboot with synaptic, but I don't know what's that.:confused:

[kvonb]

Feisty can't have it by default? :(

That would look too nice! Feisty is nearly the same as Edgy, I expect most of the work is "under the hood" stuff.

It's a bit disappointing so far, well in looks anyway :(.

Can I get install GfxBoot on a AMD64 ??? All packages they I found are for i386 infrastructure.
It isn't possible to install that with dpkg.

-------------------------------------------------------------------------------------------------------------
I installed gfxboot with synaptic, but I don't know what's that.:confused:

I wouldn't think the boot process (at that early stage) would be in 64bit mode. Maybe try it and see what happens, just make sure you have your Ubuntu CD ready in case of didaster :).

The gfxboot package in synaptic seems to be an editor or creator for the message. files or something. I installed it then removed it again thinking it was the actual boot loader, but it isn't.

[joker806]

Can I get install GfxBoot on a AMD64 ??? All packages they I found are for i386 infrastructure.
It isn't possible to install that with dpkg.

I installed gfxboot with synaptic, but I don't know what's that.:confused:

I found this (http://kanotix.com/debian/pool/main/g/grub-gfxboot/grub-gfxboot_0.97-11_amd64.deb), installed according to first post, but still have the same old black&white grub :( .

[el mariachi]

sudo
grub grub> find /boot/grub/stage1
(hdx,y) # this will be the output
grub> root (hdx,y)
grub> setup (hdx)

after inputing the first command (find) i get this

grub> find /boot/grub/stage1

Error 15: File not found


is it another stage? Grub shows, at startup, two different Ubuntu versions (different Kernels) a Memtest+ ubuntu and my Windows Xp.

[Malac]

sudo
grub grub> find /boot/grub/stage1
(hdx,y) # this will be the output
grub> root (hdx,y)
grub> setup (hdx)after inputing the first command (find) i get this

grub> find /boot/grub/stage1

Error 15: File not found
is it another stage? Grub shows, at startup, two different Ubuntu versions (different Kernels) a Memtest+ ubuntu and my Windows Xp.

That happens if you have just run grub without sudo.
The command should be all on one line sudo grubthen
grub> find /boot/grub/stage1
..................I also recommend running:sudo grub-install /dev/hd-- (replacing your hd numbers for the last two dashes)
Afterwards as well as this only worked on my system if I did both.

[Jarn]

Does the package in the first post still have to be used, or can the gfxboot from the repos be installed?

[el mariachi]

hoe can I know what number is my HD?

[Xappe]

hmm, can I get the automagic list to name the kernels Ubuntu * instead of Debian *?

[Malac]

hoe can I know what number is my HD?
df -Th
or
sudo fdisk -l that's a lowercase L not a digit 1

[chinita96]

Help! I am new to ubuntu and i've got it working except now I think I messed up when I tried to install the graphical grub i've seen from the pics.

i followed someone's directions for typing in "sudo echo gfxmenu /boot/grub/message.suse > /boot/grub/menu.lst" in the terminal and it overwrote my entire menu.lst file. the only thing in it right now is gfxmenu /boot/grub/message.suse and when i restarted, it goes to the grub terminal type screen.

basically it restarts and goes to a black screen with:

grub >

that's it. how do i load into my operating system to get my backup file of menu.lst. i made a backup before i started but i am stuck at grub > and can't get out. i tried "quit" and it didn't do anything. if i totally messed up, how would i go about re-installing everything. seems like everything i type, i can't get out of grub >.

what do i do? can someone help? has anyone else got this problem? i tried searching for it but no luck. also, i'm on a loan computer right now since i screwed up mine. whoops.

any help would be appreciated. thanks.
p.s. how do i get the code to show up in a box like the other replies? (sorry for the idiiot question)

[chinita96]

i figured it out! thanks to everyone else in the ubuntu community who has already posted about re-installing grub through the livecd. that's what i did. after reading many difference threads on the topic i figured out what i needed to do. i popped in my livecd, mounted the drive and edited my menu.lst file to the backup file i had. that solved the problem! i now have the gfxboot working.

if anyone else has the same problem as me, overwriting your menu.lst file, then do what i did. search for reinstalling grub with livecd and you'll find plenty of info.

anyways, i just wanted to say problem solved!

[Xappe]

Ah, I fixed the problem with update-grub naming the kernels Debian instead of Ubuntu. Just edit the update-grub script by hand (/sbin/update-grub). Look for the line:

# Title
title="Debian"

and change it to

# Title
title="Ubuntu"

[Malac]

Ah, I fixed the problem with update-grub naming the kernels Debian instead of Ubuntu. Just edit the update-grub script by hand (/sbin/update-grub). Look for the line:

# Title
title="Debian"

and change it to

# Title
title="Ubuntu"
Thanks, been annoying me for ages.
In case anyone's on Feisty it's moved to the script in /usr/sbin/update-grub .

[5ER]

what about amd64 grub-gfxboot.deb?

And how to use the gxboot package from repositories

[kvonb]

Hey Malac, did you get gfx-boot working on Feisty? I failed at the grub-install part, something about /dev/hda being /dev/sda now or something odd!

[Malac]

Hey Malac, did you get gfx-boot working on Feisty? I failed at the grub-install part, something about /dev/hda being /dev/sda now or something odd!
Yeah worked fine for me using /dev/sd-- notation.
In my case grub-install /dev/sda2

[kvonb]

OK, here is my dilemma:

kev@kev:~$ sudo fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 199 1598436 83 Linux
/dev/sda2 * 200 1729 12289725 7 HPFS/NTFS
/dev/sda3 1730 9729 64260000 5 Extended
/dev/sda5 1730 2875 9205213+ 83 Linux
/dev/sda6 2876 9673 54604900 83 Linux
/dev/sda7 9674 9729 449788+ 82 Linux swap / Solaris
kev@kev:~$ sudo grub
Probing devices to guess BIOS drives. This may take a long time.
kev@kev:~$

This is my grub output:

GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]

grub> find /boot/grub/stage1
(hd0,4)

grub> Where do I "grub-install" to?

As far as I understand, hd0,4 is the 4th partition on /dev/hda -or- /dev/hd0, but there is no 4th partition!

I'm extremely confused! :confused:, KEv

[Malac]

OK, here is my dilemma:

kev@kev:~$ sudo fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 199 1598436 83 Linux
/dev/sda2 * 200 1729 12289725 7 HPFS/NTFS
/dev/sda3 1730 9729 64260000 5 Extended
/dev/sda5 1730 2875 9205213+ 83 Linux
/dev/sda6 2876 9673 54604900 83 Linux
/dev/sda7 9674 9729 449788+ 82 Linux swap / Solaris
kev@kev:~$ sudo grub
Probing devices to guess BIOS drives. This may take a long time.
kev@kev:~$

This is my grub output:

GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]

grub> find /boot/grub/stage1
(hd0,4)

grub> Where do I "grub-install" to?

As far as I understand, hd0,4 is the 4th partition on /dev/hda -or- /dev/hd0, but there is no 4th partition!

I'm extremely confused! :confused:, KEv
(hd0,4) is the fifth partition grub starts at 0, so in your case that's /dev/sda5

[kvonb]

Malac: (hd0,4) is the fifth partition grub starts at 0, so in your case that's /dev/sda5

Hmm, this is very odd, this is what I get:

kev@kev:~$ sudo grub-install /dev/sda5
Password:
/dev/sda5 does not have any corresponding BIOS drive.
kev@kev:~$

See this is what I don't get, my drive is IDE not SATA or SCSI! It seems they've changed something in the way drives are used now. The simple old /dev/hdx system has gone and now we have this dev/sdx system, but it doesn't seem to work on my computer.

I get the same thing when using vmware, my CDROM drive has vanished because it's expecting /dev/hdc and it is now /dev/sdx!

Any ideas?

Thanks, KEv :)

[ptitpoul]

what about amd64 grub-gfxboot.deb?
There is a recent binary package on sidux.com, 0.97-14, for i386 and amd64 : http://sidux.com/debian/pool/main/g/grub-gfxboot/

[Malac]

Hmm, this is very odd, this is what I get:

kev@kev:~$ sudo grub-install /dev/sda5
Password:
/dev/sda5 does not have any corresponding BIOS drive.
kev@kev:~$ See this is what I don't get, my drive is IDE not SATA or SCSI! It seems they've changed something in the way drives are used now. The simple old /dev/hdx system has gone and now we have this dev/sdx system, but it doesn't seem to work on my computer.

I get the same thing when using vmware, my CDROM drive has vanished because it's expecting /dev/hdc and it is now /dev/sdx!

Any ideas?

Thanks, KEv :)
Try :sudo grub-install hd0,4
This should still work even if they have been playing around with the standard naming conventions. :)

[kvonb]

Thanks for that Malac, however this is what I get:

kev@kev:~$ sudo grub-install hd0,4
Password:
/dev/sda5 does not have any corresponding BIOS drive.
kev@kev:~$

This is driving me nuts, I can't seem to find a logical sequence in all this!

I installed Feisty from the Beta ISO and have done every update since it came out, hopefully it will be resolved soon.

I have a 60 meg update coming down as I type so maybe there is some hope :).

[abraxxas]

i installed it exactly as ya told in the tutorial on page one.. but my grub is still the same

[Malac]

i installed it exactly as ya told in the tutorial on page one.. but my grub is still the same
Did you also try sudo grub-install hdx,x as well.

[abraxxas]

thx now it works perfectly:lolflag:

[kvonb]

Did you also try sudo grub-install hdx,x as well.

Hey Malac,

Yeah I tried a heap of combinations but keep getting the same thing.

I started another thread asking about this, so I'll link to that as it seems a bit rude to have 2 on the go :)

http://ubuntuforums.org/showthread.php?t=401840

If you have the time to have a quick look I would be grateful.

Thanks, KEv :)

[patrickfromspain]

Hi there!

I've made my own gfxboot theme. it's very simple, but I think it fits well into ubuntu. Thanks to Footissimo, as I started the theme basing on the one he made (http://ubuntuforums.org/showpost.php...&postcount=61).

Bellow I attach a photo I've taken (quite bad quality, but you should get the idea) and the background image.

Hope you like it!

[andreyvul]

If you want to compile grub-gfxboot from source, get the grub-0.97 source, patch, and compile:

#Get grub
wget http://kanotix.com/debian/pool/main/g/grub-gfxboot/grub-gfxboot_0.97.orig.tar.gz
#Get the gfxboot patch
wget http://kanotix.com/debian/pool/main/g/grub-gfxboot/grub-gfxboot_0.97-11.diff.gz
#Get documentation
wget http://kanotix.com/debian/pool/main/g/grub-gfxboot/grub-gfxboot-doc_0.97-11_all.deb


#Uninstall old grub
sudo apt-get remove grub
#Unpack grub
tar xvf grub-gfxboot_0.97.orig.tar.gz
#cd to unpacked grub source
cd grub-0.97
#patch grub source for gfxboot support
patch -Np1 < gzip -dc ../grub-gfxboot_0.97-11.diff.gz
#compile
./configure
make
sudo make install

Then install grub according to the instructions in the first post

[Marktrix]

Another GFXboot theme - this time to go with the blue usplash theme here (http://ubuntuforums.org/showthread.php?t=82835&highlight=usplash) by SilentCacophony. It's a very basic black background with the glowy logo and lettering from the usplash image. If anyone likes it, I can do the other colours.

It does not fit exactly :(

i have to edit menu.lst now ok

[Io-Loki]

Hey guys,

tried to get the gfx-splash to work without success.

I removed grub and installed the grub-gfxboot for amd64. After that i added the gfxmenu line to the menu.lst

gfxmenu /grub/message.ububrown

Guess this is right, cos grubs installed on an extra partition.
Then i did run the commands in grub.

grub> find /grub/stage1
find /grub/stage1
(hd0,0)
grub> root (hd0,0)
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
setup (hd0)
Checking if "/boot/grub/stage1" exists... no
Checking if "/grub/stage1" exists... yes
Checking if "/grub/stage2" exists... yes
Checking if "/grub/e2fs_stage1_5" exists... yes
Running "embed /grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install /grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/grub/stage2 /grub/menu.lst"... succeeded
Done.


Worked fine for me too, but if i restart there's no result.

fstab:

Disk /dev/sda: 100.0 GB, 100030242816 bytes
255 heads, 63 sectors/track, 12161 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 122 979933+ 83 Linux
/dev/sda2 123 608 3903795 82 Linux swap / Solaris
/dev/sda3 609 12161 92799472+ 5 Extended
/dev/sda5 609 3647 24410736 83 Linux
/dev/sda6 3648 8510 39062016 83 Linux
/dev/sda7 8511 12161 29326626 b W95 FAT32


I use feisty fawn. Does anybody know what i'm doing wrong? I would be thankful if somebody could help.

Greetz, rijndael

[Malac]

@lo-Loki
sudo grub-install hd0

[Io-Loki]

hi,

ty malac for your reply. but this doesn't work for me. grub-install output tells me that there's an error in the script file.

/usr/sbin/grub-install: 272: Syntax error: redirection unexpected


I looked up the file, but there apparently no mistake for me.

rijndael

[Malac]

hi,

ty malac for your reply. but this doesn't work for me. grub-install output tells me that there's an error in the script file.

/usr/sbin/grub-install: 272: Syntax error: redirection unexpected
I looked up the file, but there apparently no mistake for me.

rijndael
try:
sudo grub-install /dev/sda1 instead

[Io-Loki]

already tried. same error :(

[Malac]

already tried. same error :(
Okay first try explicit pointer to gfxfile by inserting (hd0,1)/ after the "gfxmenu " line in menu.lst
Sorry if you have already posted these but post with menu.lst and device.map as attachments.

[DeeTee]

Hi... I couldn't get it working by using the "sudo grub"-command because of my sata drives (I think, I'm noob). Instead I had to log in as root and use "grub-install /dev/sda2". First I tried "sudo grub-install /dev/sda2" but this returned a lot of errors and I didn't dare rebooting. I tried root and it installed with no errors. I really liked this feature in Suse, but I like it even more when it serves Ubuntu...

Again, I should note that I only used this method because of my sata drives. As far as I have understood, the folks with IDE drives can use the guide as is.

To gain root-privileges I entered this in the terminal:

sudo passwd root
(set the password)

Here's my "session" from the terminal:

def@maskine:/$ sudo grub-install /dev/sda2
Due to a bug in xfs_freeze, the following command might produce a segmentation
fault when /boot/grub is not in an XFS filesystem. This error is harmless and
can be ignored.
xfs_freeze: specified file ["/boot/grub"] is not on an XFS filesystem


GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]
grub> root (hd0,1)
Filesystem type is reiserfs, partition type 0x83
grub> setup --stage2=/boot/grub/stage2 --prefix=/boot/grub (hd0,1)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/reiserfs_stage1_5" exists... yes
Running "embed /boot/grub/reiserfs_stage1_5 (hd0,1)"... 18 sectors are embedde d.
succeeded
Running "install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0,1) (hd0,1)1+ 18 p (hd0,1)/boot/grub/stage2 /boot/grub/menu.lst"... failed

Error 6: Mismatched or corrupt version of stage1/stage2
grub> quit


def@maskine:/$ su
Password:
root@maskine/# grub-install /dev/sda2
Due to a bug in xfs_freeze, the following command might produce a segmentation
fault when /boot/grub is not in an XFS filesystem. This error is harmless and
can be ignored.
xfs_freeze: specified file ["/boot/grub"] is not on an XFS filesystem
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

(hd0) /dev/sda
(hd1) /dev/sdb
root@maskine:/#

Please tell me if any of my conclussions, especially that one about root (and not sudo), is incorrect. My goal is to help anyone having the same problems, not to throw them into even worse trouble. I'm also sorry if any of this has been noted before in this thread, but since the custom themes showed up, it's like the support-asspect in the thread disappeared.

Oh, and do back up your menu.lst. Justin Case...


The device.map is what did it for me.

Thanks a million.

[Io-Loki]

hi,

i reinstalled feisty in 32-bit architecture, because i had problems getting everything to work and in need a running system.
I tried to install grub-gfxboot again and command

sudo grub-install /dev/sda1

worked. Don't know what the problem was under amd64.
Thanks for your help. :D

greetz, rijndael

[Ireclan]

Gfxboot makes grub look nicer but with the same features
In this howto you will install gfxboot and a suse theme for it, soon I'll make an ubuntu one ;)
Ok, let's start

Download the grub-gfxboot.deb (http://quasarfreak.googlepages.com/grub-gfxboot_0.97-5_i386.deb)
And the message.suse (http://quasarfreak.googlepages.com/message.suse)

First remove your old grub
sudo apt-get remove grubThen Install the gfxboot-grub
sudo dpkg -i grub-gfxboot_0.97-5_i386.debthen we're going to move the message
sudo cp message.suse /boot/grub/ # the suse can be replaced by the one you downloaded Then edit your menu.lst


sudo cp /boot/grub/menu.lst /boot/grub/menu.lst_backup
sudo gedit /boot/grub/menu.lstand make it use gfxboot
gfxmenu /boot/grub/message.suse # the suse can be replaced
Then do : sudo grub

grub> find /boot/grub/stage1
(hdx,y) # this will be the output
grub> root (hdx,y)
grub> setup (hdx)-- Howto make you own theme --


mkdir /home/name/whatever
cpio -i < /boot/grub/message.suse # replace it by the name of you message
edit the pictures
sudo ls . |cpio -o > /boot/grub/message.newReboot and enjoy ;)
Thanks to Quasar_freak and kno

here are some themes posted in this thread ;) ( ty :KS )

Light Green generic theme [message.gobo] | Link (http://ubuntuforums.org/showpost.php?p=1214274&postcount=12) | Screenshot (http://ubuntuforums.org/attachment.php?attachmentid=12251&d=1152089288)
Dark Brown (Dapper look) generic theme [message.new] | Link (http://ubuntuforums.org/showpost.php?p=1239724&postcount=55) | Screenshot (http://www.ubuntuforums.org/attachment.php?attachmentid=12549&d=1152600544)
Medium blue kubuntu theme [message.kubuntu] | Link (http://ubuntuforums.org/showpost.php?p=1234300&postcount=54) | Screenshot (http://files.upl.silentwhisper.net/upload5/gfxboot.jpg)
Dark grey ubuntu theme [message.ubugrey] | Link (http://ubuntuforums.org/showpost.php?p=1251236&postcount=61) | Screenshot (http://www.ubuntuforums.org/attachment.php?attachmentid=12875&d=1153129717)
Medium brown ubuntu theme [message.ububrown] | Link (http://ubuntuforums.org/showpost.php?p=1252317&postcount=63) | Screenshot (http://ubuntuforums.org/attachment.php?attachmentid=12874&d=1153129657)
Light orange ubuntu theme [message.ubu] | Link (http://ubuntuforums.org/showpost.php?p=1254642&postcount=64) | Screenshot (http://ubuntuforums.org/attachment.php?attachmentid=12873&d=1153128852)
Red ubuntu theme [message.new] | Link (http://ubuntuforums.org/showpost.php?p=1265601&postcount=65) | Screenshot (http://ubuntuforums.org/attachment.php?attachmentid=12870&d=1153128852)
Fuzzy blue and black ubuntu theme [message.bluspash] | Link (http://ubuntuforums.org/showpost.php?p=1272301&postcount=71) | Screenshot (http://www.ubuntuforums.org/attachment.php?attachmentid=12947&d=1153265746)
White / Grey Snowish generic theme [message.snow] | Link (http://ubuntuforums.org/showpost.php?p=1292317&postcount=84) | Screenshot (http://ubuntuforums.org/attachment.php?attachmentid=13161&d=1153730506)
Linspire-style blue kubuntu theme [message.kubu] | Link (http://ubuntuforums.org/showpost.php?p=1294120&postcount=86) | Screenshot (http://ubuntuforums.org/attachment.php?attachmentid=13176&d=1153757390)
Old- Grub style dark blue and light blue [message.kubu] | Link (http://mitglied.lycos.de/atoth/ubuntuusers/message.napo) | Screenshot (http://mitglied.lycos.de/atoth/ubuntuusers/screenshot_message_napo.png)
Light blue / grey Xubuntu theme [message.xubu] | Link (http://ubuntuforums.org/showpost.php?p=1297486&postcount=97) | Screenshot (http://ubuntuforums.org/attachment.php?attachmentid=13211&d=1153828350)


Grtz PingunZ[/quote]

I have followed this guide to the letter, yet all I see is the regular text GRUB screen. Am I missing something?

[Malac]

I have followed this guide to the letter, yet all I see is the regular text GRUB screen. Am I missing something?
Also try sudo grub-install hdx,xPlease can the OP put this in the first post as an extra step as this has solved a lot of the people on here's problems and I'm getting fed up typing it in. :)

[kvonb]

Also try sudo grub-install hdx,xPlease can the OP put this in the first post as an extra step as this has solved a lot of the people on here's problems and I'm getting fed up typing it in. :)

Hahahah, yeah but I bet you're getting fast at typing it though :D

[mrfuzzemz]

Also try sudo grub-install hdx,xPlease can the OP put this in the first post as an extra step as this has solved a lot of the people on here's problems and I'm getting fed up typing it in. :)

I agree that it should be included in original post as I had tried so many different things before and nothing else worked. Thanks.

[Jolly Roger]

I like nimes red grub theme but wanted to make it fit with my green desktop so I changed the background from red to green. I figured he wouldn't mind if I reposted his theme in a green version.

Credit goes to nimes for making the great grub theme in the first place, I just modified it.

[mrfuzzemz]

I don't know how many of you have gfxboot on a widescreen display, but I thought I might ask if anyone has created a theme for widescreen aspect ratio. Using the regular themes, one will get stretched images so a proportionately correct squished theme must be made they stretches appropriately when used. As for the stretching of the text, I don't know what can be done.

[pingpongboss]

I'd like to remind everyone to be VERY VERY careful when choosing what to put for the (hdx,y) or (sdx) when installing grub-gfxboot over grub. You can destroy your windows partition very easily, as I have done :(

This is what you could potentially end up with if you type in the wrong thing:
http://img352.imageshack.us/img352/3997/screenshotvy4.th.png (http://img352.imageshack.us/my.php?image=screenshotvy4.png)

So if you don't feel like having headaches, then either make absolutely certain that your inputs are correct, or just hold off on grub-gfxboot until more documentation and experimentation comes out for it.

and if anyone feels like helping me with my problem please go here http://ubuntuforums.org/showthread.php?p=2464478

[Ireclan]

Also try sudo grub-install hdx,xPlease can the OP put this in the first post as an extra step as this has solved a lot of the people on here's problems and I'm getting fed up typing it in. :)

You're QUITE SURE it's "hdx,x" and not "hdx,y"?

[Malac]

You're QUITE SURE it's "hdx,x" and not "hdx,y"?
In this instance both "x" stands for a number but yes any substitution would be permissible as they may be different numerical values. :)

[ShirishAg75]

interesting thread, would have try sometime. There should be a big place though where all the themes are listed

[bootsbradford]

I've installed GfxBoot with the ubugrey theme and it's all working fine and dandy :KS

In synaptic, I've installed something called 'gfxboot-theme-ubuntu'. What does it do? How do I get gfxboot to work with it.

[u-foka]

Hy! I trying to make gfxboot work on a fresh feisty install, but it seems i out of luck :S

I done the steps in the first post without any error, bot when i reboted, i only can see the old grub screen...
I read this thread and try anything without succes... The most interesting thing is this error message: u-foka@u-foka-laptop:~$ sudo grub-install hd0
/dev/sda1 does not have any corresponding BIOS drive.

I can get it with many grub install parameters, tryed: "hd0" "hd0,0" "/dev/sda" "/dev/sda1"

Anyone some ideas?

[patrickfromspain]

I have the same problem on my laptop.. it's a pitty, and I don't think you'll get gfx-boot to work. I have tried running sudo grub, root (hd0,5) setup (hd0) and it works, but gfx-boot won't work..

I have even tried using gfxmenu (hd0,5)/boot/grub/message.ubuntu instead of /boot/grub..

Nothing works..

[Neobuntu]

Why doesn't this work with Feisty?

[4Play]

Well, like several other ppl, i followed the guide, and nothing happened, same old lame boot screen. I am running Fiesty Fawn on a Toshiba M45-S351 Satellite Laptop. I have installed and uninstalled glxgrub two times, and tried several message.xyz screens, but nothing happens.

Did anyone on Fiesty get this to work? Will try this on my desktop, which is still running Edgy Eft...will probably work there.

Thanks :)

Update: Did not work on the 6.10 desktop installation, nothing happened, just as with the laptop....very weird. The instructions are way too simple 4 mistakes, I got no error messages whatsoever, everything went smoothly, but the black grub screen remains unaltered. And it seems that other ppl got it working on Fiesty...

any ideas on what might possibly be happening here!? Thanks

[Ace2016]

Not woring in feisty, followed everything perfectly but it just doesn't work, could it be the deb? could someone post instructions on how to compile it from source?

[ayoli]

i confirm that it does not work in Feisty, what a shame :(
New instructions and/or adapted package would be appreciated
thx.

[mrfuzzemz]

i confirm that it does not work in Feisty, what a shame :(
New instructions and/or adapted package would be appreciated
thx.

I've had it running in Feisty for a while now without a problem.

Uninstall grub > install this deb > edit the menu.lst > put your message file in the appropriate place > use the grub setup (this is all on the first page).

The part that isn't on the first page that made it work is this (which is posted every so often in this thread):

sudo grub-install hdx,y

with the numbers for the appropriate partition.

I hope this helps!

[ayoli]

lol, i ve just done that and i was back to post the trick also :)
this:
sudo grub-install hdx,y
should be added in the first post of this thread.

[mrfuzzemz]

lol, i ve just done that and i was back to post the trick also :)
this:
sudo grub-install hdx,y
should be added in the first post of this thread.

Haha! Excellent! Well I'm glad it worked for you. I don't know if the creator of the thread visits back much as I believe it's been suggested before. It would certainly clear up a lot of confusion, though.

[4Play]

Thank you 4 the tip, I thought that "sudo grub-install hdx,y" did the same thing as "root (hdx,y) >> setup (hdx)"

Thanks very much :)

[Ace2016]

ace@Linux:~$ sudo grub-install hd0,1
/dev/hda2 does not have any corresponding BIOS drive.
ace@Linux:~$

How do i fix this???

[EDIT]

I solved it, i was using the wrong deb :)

[4Play]

Erm...got another problem...when I was installing gfxgrub on another PC (amd64, sata drive) all went well except the "grub-install" part:

me@Tornado:~/gfx-grub$ sudo grub-install hd1,2
/usr/sbin/grub-install: 272: Syntax error: redirection unexpected

I get this error no matter what I try, even sudo grub-install --help gives the same redirection error...I have uninstalled gfxgrub (sudo apt-get remove grub-gfxboot) and reinstalled it....to no avail.

I am installing grub on the 3d partition of a SATA drive, since grub sees sata drives as hdX, the syntax is, i believe, correct.

[mrfuzzemz]

Be sure to include the parentheses in the appropriate places. (hd1,2) for example. Also be sure that the drive you are trying to set up grub on is found when you do:
find /boot/grub/stage1

(hd1,2) is the 3rd partition on the second hard disk. (hd0,2) is the 3rd partition on the first hard disk.

[4Play]

Thanks 4 the quick reply!

i believe the grub-install command dosent use the ( ). it's just "grub-install hdx,y"

And yes, i need do install it to the 3d partition of the secont drive (according to grub),
"find /boot/grub/stage1" yields (hd1,2), and the "root (hd1,2) and setup (hd1) do not return errors.
I've even checked the partitions with "geometry (hd1)" / "geometry (hd0)" and "fdisk -l" It seems the problem is with the grub-install command itself :(

especially because the grub-install command should return something with the "grub-install --help", this is written in the grub-install command usage page of the grub manual, instead i get:

me@Tornado:~$ grub-install --help
/usr/sbin/grub-install: 272: Syntax error: redirection unexpected


UPDATE: Problem solved, as I had thought, the problem was the .deb package, I uninstalled it and downloaded the package from another site, it's working fine now :)

[kvonb]

UPDATE: Problem solved, as I had thought, the problem was the .deb package, I uninstalled it and downloaded the package from another site, it's working fine now :)


Can you tell us where you got the fixed package please?

.

[u-foka]

Hy!

I googled for "gfxboot deb" and the first match was an other guide...

I downloaded the deb from there, and it works with grub-install command (it's still missing from the guide)

Sorry :$ the link is http://doc.gwos.org/index.php/GfxBoot

[ayoli]

it's the same guide posted by the same guy : PingunZ
so it miss the same line : sudo grub-install hdx,y

[u-foka]

I known that, but the deb on that guide working!
(The one on this post wasn't for me :S)

[ayoli]

that was your first download which failed/corrupted the file, because the deb is the same on the two pages (same link http://quasarfreak.googlepages.com/grub-gfxboot_0.97-5_i386.deb )

[u-foka]

Hmm... This is interesting... How I can download it corrupted but working?

[mrfuzzemz]

It's the same file in the same exact location. It just so happened that the first time you downloaded it it was corrupted (due to a blip in your connection or something). The time you downloaded it and it worked (from the same place, because the link goes to the same file on the same server!) it just so happened to go through normally.

[lucasvm]

Hi there!, it works great for me, but i get a message that says: "Cool computer, but, you are running 32bits in a 64bits" or something like that, i got AMD64 Athlon Dual Core, where can i download a package for my pc?

[bootmaker]

Hello!

I tried to install it on my new feisty .. but i've got that errors:

grub> find /boot/grub/stage1

Error 15: File not found

could someone help me?

Grub works fine, but it can't load the message-file ...

Greetz bOOt

[Malac]

Hello!

I tried to install it on my new feisty .. but i've got that errors:

grub> find /boot/grub/stage1

Error 15: File not found

could someone help me?

Grub works fine, but it can't load the message-file ...

Greetz bOOt
looks like you are just entering "grub" instead of "sudo grub"

[Neobuntu]

With Feisty, I followed all posts and new suggestions and this does not work.

Anyone with feisty have this working?

I'm guessing the package is not compatible.

[mrfuzzemz]

With Feisty, I followed all posts and new suggestions and this does not work.

Anyone with feisty have this working?

I'm guessing the package is not compatible.

It works just fine in Feisty. Many people on this thread have reported it working, including myself. Look a few pages back to see if you can find something that helps.

[ayoli]

With Feisty, I followed all posts and new suggestions and this does not work.

Anyone with feisty have this working?

I'm guessing the package is not compatible.

works like a charm under feisty with the first post instruction + the missing one:
sudo grub-install hdx,y

[Neobuntu]

This is a NIGHTMARE!

After 2am in the morn and it still doesn't work. (after days trying)

I've poured over all these pages AGAIN, for new tips and nothing works.

I use Feisty. This box has One drive and Kubuntu is on (hd0,1) AKA hda2.

I've noticed too many people have trashed the first part of their (non-MBR) partitions. (I haven't)

Most people do NOT use grub only in a partition without using the MBR (The Master Boot Record before your "partitions"). So with one drive (and usually all the time also, with more than one) it should be setup (hd0) for the MBR ONLY! (and "stage Two" goes in your main "root" Linux partition, AKA /boot/grub.) It's the root designation that uses Two numbers. Like "root (hd0,1)"

There are ERRORS in some of these posts that say (for example) to use hda1 for (hd0,1) and that's wrong. Please check your posts. Also; again, posts with more than one number with "setup (hd0)" will lead people to make mistakes, and write over the first part of an OS! I DON'T KNOW WHY GRUB DOESN'T GIVE A WARNING.

Anyway, somethings amiss here.

Thank you for reporting success with Feisty, I've having none with gfxboot.

Is anyone who has specifically upgraded to Feisty (not clean) seen this gfxboot working yet?

I looked at spelling, file placement, syntax, correct directories, using sudo, not using sudo, and nothing works.

Once I get to the new added step of also running "sudo grub-install hd0,1" or "sudo grub-install hd0" I get the same message: /dev/hda2 does not have any corresponding BIOS drive.

What the heck? I'm using it now AND grub tells me "hd(0,1)".

[kvonb]

It's something to do with the new SATA lib, my guess is that if you didn't do a clean install of Feisty, OR you kept any partitions from a previous installation rather than creating new ones, the lib gets confused.

I have the same errors as you, and I tried about 50 combinations of everything that has been suggested so far.

The confusion comes in the sdx or hdx designation, grub sees one type, and the system sees another, but they are the same thing!

Maybe we can get people to tell us if they created ALL new partitions when installing Feisty, or they kept an old one, and whether it worked or failed.

[Malac]

On Feisty the "missing command" is always:
sudo grub-install /dev/sdxy where x is "a,b,c, etc." and y is "1,2,3, etc." not hd anything regardless of whether it was hd when Edgy was installed.
This applies to fresh Feisty install or upgrade from Edgy.

[kvonb]

grub> find /boot/grub/stage1
(hd0,4)

grub>

kev@kev:~$ sudo grub-install /dev/sd0,4
/dev/sd0,4: Not found or not a block device.
kev@kev:~$ sudo grub-install /dev/sd04
/dev/sd04: Not found or not a block device.
kev@kev:~$

[Malac]

grub> find /boot/grub/stage1
(hd0,4)

grub> kev@kev:~$ sudo grub-install /dev/sd0,4
/dev/sd0,4: Not found or not a block device.
kev@kev:~$ sudo grub-install /dev/sd04
/dev/sd04: Not found or not a block device.
kev@kev:~$
No, it should be:sudo grub-install /dev/sda5
If you get the "no corresponding BIOS drive" message then you are trying to boot from an extended partition and your BIOS doesn't support that.

[Marktrix]

Another GFXboot theme - this time to go with the blue usplash theme here (http://ubuntuforums.org/showthread.php?t=82835&highlight=usplash) by SilentCacophony. It's a very basic black background with the glowy logo and lettering from the usplash image. If anyone likes it, I can do the other colours.

Wonderfull Image thx for that.

[Neobuntu]

On Feisty the "missing command" is always:
sudo grub-install /dev/sdxy where x is "a,b,c, etc." and y is "1,2,3, etc." not hd anything regardless of whether it was hd when Edgy was installed.
This applies to fresh Feisty install or upgrade from Edgy.

Yields:
sudo grub-install /dev/sda2
Password:
/dev/sda2: Not found or not a block device. With or without sudo.

[Neobuntu]

also sudo grub-install hd0,1
/dev/hda2 does not have any corresponding BIOS drive.

[Neobuntu]

and grub> find /boot/grub/stage1
(hd0,1) FYI

[Neobuntu]

OK, I even changed fstab to /dev/sda2 rebooted, tried all. Then /dev/hda2 rebooted, tried all and back to the UUID and rebooted and nothing gives a gfxboot graphic.

Does anyone know what the problem is. Again, I have tried all suggestions here.

At least for those of us, where this does not work, I have an easy way to do a grub image here: http://ubuntuforums.org/showthread.php?t=402971

I understand this is a tack on deb package and not official but it's still wasted way too much time.

In the interest of not driving people away from open software, what the heck is going on here?

[Malac]

@Neobuntu
These are specific instructions for you.

Remove grub, install new .deb then,
sudo nano /etc/fstabChange the device to /dev/sda2 for your / partition.
Reboot.

In the following code "grub>" is the prompt don't type this.

sudo grub
grub> find /boot/grub/stage1
(should give) (hd0,1)
grub> root (hd0,1)
grub> setup (hd0,1)
grub> quit

sudo grub-install /dev/sda2If find /boot.grub/stage1 give just (hd0) (it shouldn't) or (hd0,0)
then change the instructions after the "find" to :
grub> root (hd0,0)
grub> setup (hd0,0)
grub> quit

sudo grub-install /dev/sda
After all that you could try :
sudo update-grub for good measure. :)

If this doesn't work then there is the possibility that the "message" file is corrupt or too large or the entry in the menu.lst is wrong.

Hope this helps.

[Neobuntu]

Thank you so much for trying to help.

I did each and everyone one those exact things already. Really! Including "entry in the menu.lst".

I'm looking for something else to try and I don't think I am the only one.

[Neobuntu]

Can you explain why anyone would use "setup (hd0,1)" or "setup (hd0,1)" (and write stage1) over an installed OS; when they boot GRUB normally from the MBR "setup (hd0)"?

Wouldn't "setup (hd0,1)" or "setup (hd0,1)" write over the first part of my XP /dev/hda1 partition or the first part of my Kubuntu /dev/hda2 partition causing boot damage??

I went back and did everything again with ("setup (hd0)"); no graphic seen.

[Neobuntu]

No joy.

[mrfuzzemz]

Can you explain why anyone would use "setup (hd0,1)" or "setup (hd0,1)" (and write stage1) over an installed OS; when they boot GRUB normally from the MBR "setup (hd0)"?

Wouldn't "setup (hd0,1)" or "setup (hd0,1)" write over the first part of my XP /dev/hda1 partition or the first part of my Kubuntu /dev/hda2 partition causing boot damage??


Someone would do that if they were installing grub to the beginning of a partition rather than to the master boot record. This would make for a slightly more complex boot configuration, but some people do it.

Be sure your menu.lst entry is point to the right file and the file is not corrupt. You may also want to try
sudo grub -install (hd0,1)
with the appropriate partition (where /boot is.)

[Neobuntu]

Someone would do that if they were installing grub to the beginning of a partition rather than to the master oot record. This would make for a slightly more complex boot configuration, but some people do it.

So you agree that most would NOT have a custom (MBR) menu that goes to a sub-GRUB menu(s) per partition then? Can you say less than 1% perhaps?

Would you also agree that any OS already installed would then be trashed? Thus, anything other than "setup (hd0)" would be done BEFORE an OS install; into that partition(as it would write GRUB stage 1 over the boot sector of the partition and not just the MBR)? Yes, I know "setup (hd1)" could be used for another drive but that's not the point. Trying other than "setup (hd0)" will most likely trash peoples systems.

Be sure your menu.lst entry is point to the right file and the file is not corrupt. You may also want to try

with the appropriate partition (where /boot is.)

You know, I really do appreciate anyone who takes their time to help; in any case. Yet, how many times do I have to indicate that I did that.

I make mistakes and would NEVER assume to be 100% correct or infallible but at this point I believe we have a GFXboot problem.

I'm asking for help and suggestions; for the benefit of those of us experiencing this no gfxboot graphic. Specifically not being able to do a gfxboot grub-install; on known partition.

How can I say this? I've been assuming it's me and my errors but it doesn't look that way.

I'm also very concerned that many of you guys are trashing your install trying to make this work.

I'm very curious about the undefined cause of the (no gfxboot graphic, probably due to grub-install failure) problem.

[kvonb]

No, it should be:sudo grub-install /dev/sda5

kev@kev:~$ sudo grub-install /dev/sda5
Password:
/dev/sda5 does not have any corresponding BIOS drive.
kev@kev:~$
If you get the "no corresponding BIOS drive" message then you are trying to boot from an extended partition and your BIOS doesn't support that.Well I have booted from it, and it is working because I am writing this from my unsupported partition, and have been booting from this same partition since Dapper I believe! Unless I'm actually dead and living a ghost life! :lolflag:

Here is my partition table:

kev@kev:~$ sudo fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 199 1598436 83 Linux
/dev/sda2 * 200 1729 12289725 7 HPFS/NTFS
/dev/sda3 1730 9729 64260000 5 Extended
/dev/sda5 1730 2875 9205213+ 83 Linux
/dev/sda6 2876 9673 54604900 83 Linux
/dev/sda7 9674 9729 449788+ 82 Linux swap / Solaris
kev@kev:~$

[Malac]

kev@kev:~$ sudo grub-install /dev/sda5
Password:
/dev/sda5 does not have any corresponding BIOS drive.
kev@kev:~$ Well I have booted from it, and it is working because I am writing this from my unsupported partition, and have been booting from this same partition since Dapper I believe! Unless I'm actually dead and living a ghost life! :lolflag:

Here is my partition table:

kev@kev:~$ sudo fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 199 1598436 83 Linux
/dev/sda2 * 200 1729 12289725 7 HPFS/NTFS
/dev/sda3 1730 9729 64260000 5 Extended
/dev/sda5 1730 2875 9205213+ 83 Linux
/dev/sda6 2876 9673 54604900 83 Linux
/dev/sda7 9674 9729 449788+ 82 Linux swap / Solaris
kev@kev:~$
No, you are booting from /dev/sda2 that's what the * under Boot means.

[ZodiacfreaK]

gah I am such an idiot, I will try to explain this as best as I can. I have a tri-boot setup, Windows Vista, Mac OS X86, and Ubuntu 7.04 Feisty Fawn. I had grub installed and working perfectly, but then I wanted this graphical boot. Bad idea, I should have just been satisfied with what I had :) but that neever works. So I went through the install steps on either page 30 in this thread, well I got to this part

sudo grub

grub> find /boot/grub/stage1
(hdx,y) # this will be the output
grub> root (hdx,y)
grub> setup (hdx)
ANd I accidently did the setup on my hd(0,2) partition instead of (0,3)
My 0,2 partition is My Mac OS X86 install. I rebooted. Well nothing changed so I went back through the steps again and this time put in the correct numbers. Everything worked but when I tried to boot into my Mac OS X partition it stalls about two seconds and then goes back to the GRUB boot screen. What I found out is that I now have GRUB installed on two partitions, I put it on my mac os partition and the other one I think is vista or linux, I dont remember :(. So all I need to do is figure out a way to uninstall GRUB from my mac partition. Can anyone help me with that? If you need any more info just ask!

Basically long story short, if you can tell me how to remove GRUB from a specified partition that would be the way to fix it.

[ZodiacfreaK]

^Edit^ bump

[kvonb]

No, you are booting from /dev/sda2 that's what the * under Boot means.

OK, so if I did a grub-install to sda2 that would work?

[Malac]

OK, so if I did a grub-install to sda2 that would work?
Should do if it were linux yes. not sure what it would do with it being NTFS.
I still can't see how your booting to linux at all if you're saying that GRUB isn't in your MBR. :)
If GRUB is in MBR then "sudo grub-install hd0" should do it.

[kvonb]

Should do if it were linux yes. not sure what it would do with it being NTFS.
I still can't see how your booting to linux at all if you're saying that GRUB isn't in your MBR. :)
If GRUB is in MBR then "sudo grub-install hd0" should do it.

kev@kev:~$ sudo grub-install hd0
Password:
/dev/sda5 does not have any corresponding BIOS drive.

kev@kev:~$ sudo grub-install sda
Format of install_device not recognized.


I don't understand either :S

[Malac]

kev@kev:~$ sudo grub-install hd0
Password:
/dev/sda5 does not have any corresponding BIOS drive.

kev@kev:~$ sudo grub-install sda
Format of install_device not recognized.
I don't understand either :S
Looks like you're scuppered. I seem to remember from a previous post you saying the first partition on your disk is corrupt.
You can't boot from an extended partition which is what the "does not have any corresponding BIOS drive" message is indicating.

The only other thing I can suggest is to run through the whole thing again using root (hdo) and setup (hd0) in GRUB and see if that installs it to the MBR successfully then "sudo grub-install hd0" for good measure.

I still can't figure out how you're managing to boot into Ubuntu at all. :)

[kvonb]

I still can't figure out how you're managing to boot into Ubuntu at all. :)

...that's the magic of Ubuntu baby ;)

[Neobuntu]

No look. We have a real problem here.

It's not extended partitions, it's probably not our user commands. Myself, kvonb and other are NOT seeing the gfxboot and we have tried all suggested tips (thank you).

People are trashing other OS installs when manually attempting the GRUB setup command with anything other than "setup (hd0) to the MBR. While there is some very advanced uses for this, it HAS to be done BEFORE the OS is installed to said fancy multiboot, multi-menu setup partition. GRUB should warn and it doesn't. Generally, only install GRUB stage 1 into the MBR via "setup (hd0)".

If you really must set up an advanced mutil-menu system for you multi-booting. I suggest you make up an independent "boot" partition, separate from all others, that holds the GRUB stage 2 (menu.lst etc). This way you don't have to back up or remember which Linux partition that GRUB stage 2 is in. For most people, their only or main Linux install is where GRUB stage 2 is installed (AUTOMATED BY THE INSTALLER) . So really, you might as well just store GRUB stage 2 in your Linux installed partition and if you wipe the whole thing, you can make up a new menu. None of this is critical, writing stage *1* over a partition (other than the MBR) where an existing OS boot sector already exists, IS critical and your best course of action then would be to reinstall (after retrieving anything you can't live without).

We need new direction and explanation about why (with respect that we have double, tripple etc.., checked our attempts) the gfxboot is not working at the grub-install point.

I know that my (stage 2) partition is /dev/hda2 AKA (hd0,1). I've tried /dev/sda and /dev/sda2 with grub-install as well and NOTHING works.

We have posted, over and over the output of these trials. GRUB works, why not gfxboot, for us?

[Neobuntu]

I noted that Feisty's GRUB would set menu.lst back to UUIDs when "sudo update-grub" was run so I did the whole shebang again with grub-gfxboot and made sure the "menu.lst" used my /dev/hda2 and I got the exact same results.

No graphic!

Anyone know why gfxboot just does not work?

P.S. BTW, the asterisk on the "sudo fdisk -l" output just means the boot flag, not the partition that one has booted.

[kvonb]

You certainly have a point Neobuntu as this how-to worked perfectly for me (using the exact same hard drive with the same partitions) under Edgy.

It is only since I did a clean install of Feisty BETA, keeping ALL the original partitions and formatting my / partition (/dev/hda5), which Feisty now calls /dev/sda5.

So as far as I can tell, my grub stage 2 is sitting on /dev/sda5, although grub tells me that it is on hd0,4 which doesn't exist!

Now, I'm not 100% sure where my MBR is located.

The thing with my hard disk is that it contains bad sectors at the start of the drive, hence /dev/sda1 is simply an unused partition that I made in order to skip the bad bits, and has nothing on it (I think :confused:).

Now although /dev/sda2 is my active partition (it is NTFS) I don't believe that the MBR is on that partition, as the MBR can be in only one location and that is at the start of the physical disk as I understand it. PLEASE correct me if I'm wrong on that one!

So to sum up, gfxboot worked under Edgy, but not Feisty! Why?

[mrfuzzemz]

So as far as I can tell, my grub stage 2 is sitting on /dev/sda5, although grub tells me that it is on hd0,4 which doesn't exist!

You do realize that hd0,4 and /dev/sda5 are the same exact thing, right? GRUB just uses a different naming scheme. hda or sda is hd0, hdb or sdb is hd1. Partitions go like this: hda1 or sda1 is hd0,0, hdb3 or sdb3 is hd1,2..

GRUB starts counting from 0 rather than 1.

[Neobuntu]

Yes, but why doesn't this work for Feisty?

[mrfuzzemz]

Yes, but why doesn't this work for Feisty?

Well, uh. I'm using Feisty right now and gfxboot works perfectly. Feisty uses UUID as it is more uniquely set. The partition in the /dev/sda1 format should be commented out just above the UUID in the GRUB menu.lst.

[Psicolonia]

Hi everyone, i've got it up and running. Looks pretty nice but I have a question...

Is your grub quiet? That is, when you boot normal grub you see a "Starting up..." message and then the usplash of ubuntu shows up! In this one this does not happend! I get the entire grub dump. Basically it prints out all the messages of the entry it's booting.

Does this happen to you too? Or it's just me. My menu.lst have the option quiet in all my entries. And this happens in all of them instead the normal "Starting up..."


Can someone help me correct this?

[mrfuzzemz]

Hi everyone, i've got it up and running. Looks pretty nice but I have a question...

Is your grub quiet? That is, when you boot normal grub you see a "Starting up..." message and then the usplash of ubuntu shows up! In this one this does not happend! I get the entire grub dump. Basically it prints out all the messages of the entry it's booting.

Does this happen to you too? Or it's just me. My menu.lst have the option quiet in all my entries. And this happens in all of them instead the normal "Starting up..."


Can someone help me correct this?

You have quiet as a separate line and in the kernel boot line?

[Psicolonia]

here goes :) thanks for the reply!

## ## End Default Options ##

title Ubuntu
root (hd0,1)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=74ace9fa-0a1f-422b-b145-1a240e6f24c0 ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
quiet

title Ubuntu (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=74ace9fa-0a1f-422b-b145-1a240e6f24c0 ro single
initrd /boot/initrd.img-2.6.20-15-generic

title Ubuntu (memtest86+)
root (hd0,1)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title ----------------------
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Windows XP Professional
root (hd0,0)
makeactive
chainloader +1

[Neobuntu]

Well, uh. I'm using Feisty right now and gfxboot works perfectly. Feisty uses UUID as it is more uniquely set. The partition in the /dev/sda1 format should be commented out just above the UUID in the GRUB menu.lst.

I'm aware that some are getting gfxboot to work with Feisty. We are not.

Are you aware that some of us have repeatedly gone over all directions and ideas?

Somethings stopping the graphic. I've tried other graphic files. They are in the correct and designated place.

root (hd0,1)
setup(hd0)

...seems to work but it does not indicate the graphic file was found like regular GRUB does.

For you guys with a working Feisty gfxboot, does your install indicate the graphic file was found?

I'm not sure "grub-install" should be needed at all but it yields said errors. "update-grub" only seems to work as with regular GRUB, listing the old grub splash (which I also tested without) and does not fix gfxboot.

What's going on?

[Psicolonia]

i'm a fiesty working fine ;)

here's how i did it (it will sound very wierd)

I tried everything and nothing, so i started dumbly installing on EVERY single partion I've got!

Big mistake! BIG! I tried to boot windows. But windwos partition had a grub! and on that grub if I tried to run windows... I had a grub! I was in a loop. So here's what I did:

Grabbed the WindowsXP boot disc. and ran:

fixmbr
fixboot

both.

Afterwards I ran ubuntu live CD (fiesty) and made grub-install again

everything started to work fine...

Please don't give this a try unless you are crazy but... mine's working...

[phansiizwe]

I think that when you have grub running in the Master Boot record, you need to use the grub-install command to get it working.

I have one SATA harddrive (sda) and had grub installed in the master boot record. Following the steps in the how-to did not give me a graphical grub, but after doing:

sudo grub-install /dev/sda

everything worked!

[Psicolonia]

basically you have to reinstall grub. otherwise the grub on the mbr is still the old one and does not recognize the graphical line on menu.lst.

But quite honestly i've tried that dozens of times. only when i cleared the mbr and re-install it worked.

On fiesty i wasn't able to get it to run before removing it... but it was just me!

[Neobuntu]

How many people have it working by clearing the MBR first?

[u-foka]

Hy!

Now i find out what was the problem on my feisty computer... It's have an ide hdd, but feisty uses it with a fake scsi driver (/dev/sda), when i try to run "grub-install hd0,0" it's told my: /dev/sda1 does not have any corresponding BIOS drive. But when i loaded feisty with an old 2.6.17 kernel, it's using the generic ide driver for my hdd (/dev/hda), and grub-install work's fine :)

I hope it's can help anybody :)

[Neobuntu]

I tried work-arounds (sda, no UUID, etc) for "2.6.20-15-generic #2 SMP".

Does this mean gfxboot graphic does not work with anyones Fiesty and "2.6.20-15-generic #2 SMP"?

[mrfuzzemz]

The kernel should have nothing to do with it as the kernel is loaded by grub.

[fooman]

running fiesty on my 2nd ide drive (hdb) ...i followed the guide in the first post , but could not get it to work.

used the command:

sudo grub-install /dev/hdb

and hey....IT WORKS !! :D

thanks

[manishk]

Can anyone please tell me how to get back the old grub (assuming that I have the Feisty Live CD)??

No, I haven't broke my system...I haven't even started installing gfx-grub. I just wanted to make sure I know how to get back before getting my hands dirty!! ;)

[mrfuzzemz]

manishk:
Using the livecd you'll open a terminal and run
sudo grub
find /boot/grub/stage1
root [whatever it returns above]
setup [whatever drive it says above. (hd0) for example

Let me know if you have any more questions

[Thusitha]

hello everybody!!
my problem is this ...........
I did everything u hav told to me..........
but @ da booting it says cannot find grafics file......
so wat do i do?
is there a proper place in the menu.1st to place that "gfxmenu .............." line.........

thnx.

[oGGe]

Hello people! Thanks for the lovley guide.

But I have a problem. I followed all your steps, but got the same GRUB look as always. So I checked if other ppl got this output, and they had it installed on an other HD. But I have only one HD! What can I do ?

[LKRaider]

your menu.lst is probably wrong:

put the gfxboot onption on the first line of the file
disable password protection if it is enabled (gfxboot won't work with password protection and you'll get the normal grub screen)

see if that fixes it.

[oGGe]

your menu.lst is probably wrong:

put the gfxboot onption on the first line of the file
disable password protection if it is enabled (gfxboot won't work with password protection and you'll get the normal grub screen)

see if that fixes it.

First line now, i have no passwd on. Lets see it it works ^^

[oGGe]

Ok, that didn't work. Ill give you 2 outcomes to find out what i shall do.

Here's 'fdisk -l'
Disk /dev/hda: 10,0 GB, 10056130560 byte
255 huvuden, 63 sektorer/spår, 1222 cylindrar
Enheter = cylindrar av 16065 · 512 = 8225280 byte

Enhet Start Början **** Block Id System
/dev/hda1 1 1161 9325701 83 Linux
/dev/hda2 1162 1222 489982+ 5 Utökad
/dev/hda5 1162 1222 489951 82 Linux växling / Solaris

And here we go with 'menu.lst'
gfxmenu /boot/grub/message.xubu

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)


# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash locale=sv_SE

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##

title Ubuntu, kernel 2.6.20-16-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-16-386 root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro quiet splash locale=sv_SE
initrd /boot/initrd.img-2.6.20-16-386
quiet
savedefault

title Ubuntu, kernel 2.6.20-16-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-16-386 root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro single
initrd /boot/initrd.img-2.6.20-16-386

title Ubuntu, kernel 2.6.20-16-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro quiet splash locale=sv_SE
initrd /boot/initrd.img-2.6.20-16-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-16-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro single
initrd /boot/initrd.img-2.6.20-16-generic

title Ubuntu, kernel 2.6.20-15-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-386 root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro quiet splash locale=sv_SE
initrd /boot/initrd.img-2.6.20-15-386
quiet
savedefault

title Ubuntu, kernel 2.6.20-15-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-386 root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro single
initrd /boot/initrd.img-2.6.20-15-386

title Ubuntu, kernel 2.6.20-15-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro quiet splash locale=sv_SE
initrd /boot/initrd.img-2.6.20-15-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro single
initrd /boot/initrd.img-2.6.20-15-generic

title Ubuntu, kernel 2.6.17-11-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-11-386 root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro quiet splash locale=sv_SE
initrd /boot/initrd.img-2.6.17-11-386
quiet
savedefault

title Ubuntu, kernel 2.6.17-11-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-11-386 root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro single
initrd /boot/initrd.img-2.6.17-11-386

title Ubuntu, kernel 2.6.17-11-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-11-generic root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro quiet splash locale=sv_SE
initrd /boot/initrd.img-2.6.17-11-generic
quiet
savedefault

title Ubuntu, kernel 2.6.17-11-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-11-generic root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro single
initrd /boot/initrd.img-2.6.17-11-generic

title Ubuntu, kernel 2.6.17-10-386
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-386 root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro quiet splash locale=sv_SE
initrd /boot/initrd.img-2.6.17-10-386
quiet
savedefault

title Ubuntu, kernel 2.6.17-10-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-386 root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro single
initrd /boot/initrd.img-2.6.17-10-386

title Ubuntu, kernel 2.6.17-10-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro quiet splash locale=sv_SE
initrd /boot/initrd.img-2.6.17-10-generic
quiet
savedefault

title Ubuntu, kernel 2.6.17-10-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic root=UUID=ae9524e5-c83f-4cd8-802d-ad2b73ea519d ro single
initrd /boot/initrd.img-2.6.17-10-generic

title Ubuntu, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

That's it. Is something wrong ?

[phansiizwe]

Hello people! Thanks for the lovley guide.

But I have a problem. I followed all your steps, but got the same GRUB look as always. So I checked if other ppl got this output, and they had it installed on an other HD. But I have only one HD! What can I do ?

If you have GRUB installed in the master boot record, try:

sudo grub-install /dev/hda

[Cyclist]

I'm a total Newbie, but I think this step is missing at the end:

sudo grub-install /dev/hda (or whatever the name of your Ubuntu disk may be: sda, hdc etc.)

I spend hours on it yesterday and didn't get it working, till I ended your instructions with the command in the line above.

Gr, Cyclist

I just see someone else gave the same reply......I found it out myself and it worked for me. NOTE however that your drive may have a different name than hda!

[mrfuzzemz]

I'm a total Newbie, but I think this step is missing at the end:

sudo grub-install /dev/hda (or whatever the name of your Ubuntu disk may be: sda, hdc etc.)

I spend hours on it yesterday and didn't get it working, till I ended your instructions with the command in the line above.

Gr, Cyclist

I just see someone else gave the same reply......I found it out myself and it worked for me. NOTE however that your drive may have a different name than hda!

That's absolutely right. We've been saying that for a while, but the starter of the tread has not updated it at all.

[Thusitha]

your menu.lst is probably wrong:

put the gfxboot onption on the first line of the file
disable password protection if it is enabled (gfxboot won't work with password protection and you'll get the normal grub screen)

see if that fixes it.

tired but no success........ always says missing graphic file........ and another thing ......
FIND command in the grub shell is not working...... I hav given the right path but it says cannot find the file........

[bernerbits]

Hey,

I seem to be having the same old story. However, I haven't seen my exact symptoms here, it seems to be actually trying to load the graphical grub file but finding it corrupted. For starters, PLEASE don't tell me to "sudo grub-install /dev/sda and it will just work."

That said, I'm running a Dell Inspiron 1501 laptop with an AMD64 processor.

Here's my fdisk -l output:

root@delllaptop-ubuntu:/home/dcberner# fdisk -l

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 9 72261 de Dell Utility
/dev/sda2 10 1315 10485760 7 HPFS/NTFS
/dev/sda3 * 1315 11407 81060864 7 HPFS/NTFS
/dev/sda4 11407 14376 23855861 5 Extended
/dev/sda5 * 11407 11414 63595+ 83 Linux
/dev/sda6 11415 12720 10490413+ 83 Linux
/dev/sda7 12721 12785 522081 83 Linux
/dev/sda8 12786 12916 1052226 82 Linux swap / Solaris
/dev/sda9 12917 13979 8538516 83 Linux
/dev/sda10 13980 14110 1052226 83 Linux
/dev/sda11 14111 14376 2136613+ 83 Linux


Here's my menu.lst:

root@delllaptop-ubuntu:/home/dcberner# cat /boot/grub/menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 15

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
color cyan/blue white/blue
foreground 000000
background ffffff

gfxmenu /grub/message.ubugrey

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=64d033c9-ccac-4a2a-9d75-f781e18614c2 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,4)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##

title Windows Vista
root (hd0,2)
makeactive
chainloader +1

title Debian GNU/Linux, kernel 2.6.20-15-generic
root (hd0,4)
kernel /vmlinuz-2.6.20-15-generic root=UUID=64d033c9-ccac-4a2a-9d75-f781e18614c2 ro quiet splash
initrd /initrd.img-2.6.20-15-generic

title Debian GNU/Linux, kernel 2.6.20-15-generic (recovery mode)
root (hd0,4)
kernel /vmlinuz-2.6.20-15-generic root=UUID=64d033c9-ccac-4a2a-9d75-f781e18614c2 ro single
initrd /initrd.img-2.6.20-15-generic

title Debian GNU/Linux, kernel memtest86+
root (hd0,4)
kernel /memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root



Here's the contents of /boot/grub:

root@delllaptop-ubuntu:/home/dcberner# ls /boot/grub
default iso9660_stage1_5 menu.lst.bak reiserfs_stage1_5
device.map jfs_stage1_5 message.suse stage1
e2fs_stage1_5 menu.lst message.ubugrey stage2
fat_stage1_5 menu.lst~ message.wide xfs_stage1_5
installed-version menu.lst_backup minix_stage1_5


And here's the output of my setup:

root@delllaptop-ubuntu:/home/dcberner# grub
Probing devices to guess BIOS drives. This may take a long time.


GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]
grub> find /grub/stage1
find /grub/stage1
(hd0,4)
grub> root (hd0,4)
root (hd0,4)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,4)/boot/grub/stage2 /boot/grub/menu.lst"... succeeded
Done.
grub> quit
quit


So, when I boot up, I get the following message:

/grub/message.ubugrey: Invalid file format

Then it waits 5 seconds and gives me the standard text GRUB menu. I have tried three themes so far and it's done this for each and every one. A quick glance at the source code confirms that it did indeed FIND the file, but was unable to find a file contained inside it that started with the right magic number (magic number being a standard file format indicator like GIF89a and CAFEBABE).

Anyone run into this particular problem?

[kvonb]

Hey,

when I boot up, I get the following message:

/grub/message.ubugrey: Invalid file formatThen it waits 5 seconds and gives me the standard text GRUB menu. I have tried three themes so far and it's done this for each and every one. A quick glance at the source code confirms that it did indeed FIND the file, but was unable to find a file contained inside it that started with the right magic number (magic number being a standard file format indicator like GIF89a and CAFEBABE).

Anyone run into this particular problem?

Read the following line, note anything wrong?

gfxmenu /grub/message.ubugrey

It should be:

gfxmenu /boot/grub/message.ubugrey

It's easy to make a mistake, I've done it many many times :(

[Robert98374]

sorry had to look at an example to figure it out :-)

[Neobuntu]

OK now. Still not working and others here, seem to be having the same frustration.

I realize the details must be followed. No syntax or step can be missed and I know what my drive is called by GRUB and otherwise.

It seems like every time I assert this predicament, someone says "Oh I just fixed it by doing X". I really don't think I have failed to accurately attempt every suggestion (and some of my own). So this is turning away SOME (not all) of us.

Somethings incompatible.

Perhaps it is the Nvidia card and it's modules I am using?

[frying_fish]

By the time grub is being loaded it isn't even at a stage of looking at graphics card drivers or modules for anything. It hasn't started an OS, so that won't be the cause.

[DizzyTech]

Is there a repo for this anywhere?

[nbayiha]

Just want to say that i follow the thread and i get it worked ,
i am using a amd64bit, and i recommended everyone who want to make it work to be really carefull and to read all the post from the beginning, I know it's too long but sometimes messing up with Grub can just bring to one solution...... reinstalling and i am sure no one want it. :-p

For those with 64bit don't forget to had this command sudo grub-install hdx,y

Anyway let me resume you what you should do , for those who don't want to read all the post.
actually this should work for everyone, especially for those with 64bit architecture, please go step by step and read carefully

1) download gfxboot

http://quasarfreak.googlepages.com/grub-gfxboot_0.97-5_i386.deb

2) download the theme you want u can take the one from the first post
(actually i'm using this one http://ubuntuforums.org/attachment.php?attachmentid=12874&d=1153129657)

http://ubuntuforums.org/showpost.php?p=1212505&postcount=1

3)Remove the old Grub

sudo apt-get remove grub

4) install the gfx boot from the step one(it's a debian package so there is nothing to say here it is GUI)

those with 64bit will have to force the architecture cause this deb is for 32bit, so for those with (for example amd64 ) do this in a terminal.

sudo dpkg -i --force-architecture grub-gfxboot_0.97-5_i386.deb

just say yes if something is asked.

5) now copy your theme to the grub

sudo cp message.suse /boot/grub/

of course message.suse can be message.xxxxxx for me for example it was message.ububrown
xxx is depending on which theme you are using and like i the beginning we consider using the theme from the first page so it should be message.suse

6) backup you grub file.

sudo cp /boot/grub/menu.lst /boot/grub/menu.lst_backup

7)now edit your menu.ls in the grub, you should be careful about this place cause depending on where u are going to put the line , you theme is going to be seen or not. actually i put in the first line

gksudo gedit /boot/grub/menu.lst

this will open a textfile, insert at the beginning this new line. gfxmenu /boot/grub/message.suse

save

8 ) 8) now open a terminal
and write

sudo grub
u should be now in the grub console and you should be receiving something looking like this grub>
so write this first

find /boot/grub/stage1 press enter
you will have an output looking like this (hdx,y) of course x, and y represent number in my case they were 0 and 6. anyway remenber those number.

write now this
root (hdx,y)

and after this
setup (hdx)

when it says completed hit ctrl+c

9) now this step is actually for those using feisty fawn like me,
you soul make this at the end

sudo grub-install hdx,y

and that's it.


I make it as much easier so even someone who don't know a lot about grub loader can make it work(even my Grand Ma) reading this will make it work ;) ummmmmmmmmmmmmmm maybe :D

[Neobuntu]

It worked!

T H A N K Y O U !

[rollps]

worked for me too !!

i had given up any hope to make this thing work again....

i think the important part is to do :
sudo grub-install hdx,y

at the end (it wasn't in the original post)

thanks guys :D

[kvonb]

Anyone know what this means:

kev@kev:~$ sudo grub-install hd0,0

GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]
grub> root (hd0,0)
Filesystem type is reiserfs, partition type 0x83
grub> setup --stage2=/boot/grub/stage2 --prefix=/boot/grub (hd0,0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/reiserfs_stage1_5" exists... yes
Running "embed /boot/grub/reiserfs_stage1_5 (hd0,0)"... 18 sectors are embedded.
succeeded
Running "install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0,0) (hd0,0)1+18 p (hd0,0)/boot/grub/stage2 /boot/grub/menu.lst"... failed

Error 6: Mismatched or corrupt version of stage1/stage2
grub> quit
kev@kev:~$
...apart from that it is broken :)

OK, I tried this as well and it didn't give any error messages at least:

kev@kev:~$ sudo grub-install --recheck /dev/sda
Probing devices to guess BIOS drives. This may take a long time.
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

(fd0) /dev/fd0
(hd0) /dev/sda
kev@kev:~$

I have yet to reboot and try iy, I'll report back.....

[oGGe]

If you have GRUB installed in the master boot record, try:

sudo grub-install /dev/hda


Thank you ^^' That was the missing step. The Grub-terminal stuff didnt rly work ;D

[ShareBuntu]

Works perfectly with the addition of sudo grub-install hdx,y to the original instructions. :D

[4tro]

maybe this comes in handy

http://www.kanotix.com/files/debian/pool/main/g/grub-gfxboot/grub-gfxboot_0.97-11_amd64.deb

only problem is you'll need to backup your /usr/sbin/update-grub before installing, because there are some differences from debian to ubuntu

to backup
sudo cp /usr/sbin/update-grub /usr/sbin/update-grub.oldto install the package
sudo dpkg -i grub-gfxboot_0.97-11_amd64.debafter you installed the package, run:
sudo cp /usr/sbin/update-grub.old /usr/sbin/update-grubthese steps just replace the steps about installing the package, nothing else.

[msch]

So, when I boot up, I get the following message:

/grub/message.ubugrey: Invalid file format

Then it waits 5 seconds and gives me the standard text GRUB menu. I have tried three themes so far and it's done this for each and every one. A quick glance at the source code confirms that it did indeed FIND the file, but was unable to find a file contained inside it that started with the right magic number (magic number being a standard file format indicator like GIF89a and CAFEBABE).

Anyone run into this particular problem?

I'm getting the same thing here bernerbits. This is on a Dell D820 with core2duo running amd64. Has anyone successfully figured this out?

I've tried 5 different message files, unpacked and repacked assorted ones, nothing seems to work. Any suggestions would be appreciated!

[ESPOiG]

gfxgrub works in fiesty fine for me

[4tro]

I'm getting the same thing here bernerbits. This is on a Dell D820 with core2duo running amd64. Has anyone successfully figured this out?

I've tried 5 different message files, unpacked and repacked assorted ones, nothing seems to work. Any suggestions would be appreciated!

i could be mistaken but isn't the standard grub directory /boot/grub/?
dunno if it is related though.

[msch]

I'm getting the same thing here bernerbits. This is on a Dell D820 with core2duo running amd64. Has anyone successfully figured this out?

I've tried 5 different message files, unpacked and repacked assorted ones, nothing seems to work. Any suggestions would be appreciated!

Hello, I've finally figured this out.

It isn't realated to the path name. The fact that it's reporting invalid file format indicates that it has successfully found the file, but isn't able to process it correctly. The difference between /boot/grub/message and /grub/message has to do with if you have a seperate boot partition. I have a seperate boot partition that mounts at /boot. Thus when looked at indiviudually the pathing on that partition starts with /grub.

As far as fixing the error, I'm using the sidux amd64 debs mentioned earlier in this thread. I installed gfxboot-theme-sidux-2006 from the same repo. You then have to:


claudia:~# cd /usr/share/gfxboot-theme-sidux-2006/sidux-2006/
claudia:/usr/share/gfxboot-theme-sidux-2006/sidux-2006# make
claudia:/usr/share/gfxboot-theme-sidux-2006/sidux-2006# cp boot/message /boot/grub/


And this gives me a properly formatted message file. I assume this is a difference in the amd64 debs from sidux vs. the i386 deb using the force-arch.

So to cap, it appears that if you use the debs mentioned earlier in the thread from

http://sidux.com/debian/pool/main/g/grub-gfxboot/

you need to follow the make procedure to get a valid file format for this verision.

[4tro]

Hello, I've finally figured this out.

It isn't realated to the path name. The fact that it's reporting invalid file format indicates that it has successfully found the file, but isn't able to process it correctly. The difference between /boot/grub/message and /grub/message has to do with if you have a seperate boot partition. I have a seperate boot partition that mounts at /boot. Thus when looked at indiviudually the pathing on that partition starts with /grub.

As far as fixing the error, I'm using the sidux amd64 debs mentioned earlier in this thread. I installed gfxboot-theme-sidux-2006 from the same repo. You then have to:


claudia:~# cd /usr/share/gfxboot-theme-sidux-2006/sidux-2006/
claudia:/usr/share/gfxboot-theme-sidux-2006/sidux-2006# make
claudia:/usr/share/gfxboot-theme-sidux-2006/sidux-2006# cp boot/message /boot/grub/
And this gives me a properly formatted message file. I assume this is a difference in the amd64 debs from sidux vs. the i386 deb using the force-arch.

So to cap, it appears that if you use the debs mentioned earlier in the thread from

http://sidux.com/debian/pool/main/g/grub-gfxboot/

you need to follow the make procedure to get a valid file format for this verision.


i pasted a link to amd64 packages a few posts ago. those work perfectly for me.


http://www.kanotix.com/files/debian/pool/main/g/grub-gfxboot/grub-gfxboot_0.97-11_amd64.deb


have a go at it

somebody should really add these to the howto in the first post.

[mrfuzzemz]

Since no one (the thread starter hasn't) has added to the first post then maybe we should just start a new thread that is complete. Referencing this thread, of course.

[4tro]

i can start a new one, but i would like to include the complete guide into it.
that way it'll stay readable

i made the new one, posted it for acceptance by the moderators, it will be visible soon i hope.
please comment in the thread if you have ideas or comments on the howto.

or just drop me a pm

*edit*
addendum to this thread on:
http://ubuntuforums.org/showthread.php?t=481957
mostly useful for people running in 64 bit mode.

[kraigory]

okay, so i feel kindof dumb for asking this, but...

kraigory@elihu:~$ sudo fdisk -l
Password:

Disk /dev/sda: 98.5 GB, 98522403840 bytes
255 heads, 63 sectors/track, 11978 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 6 48163+ de Dell Utility
/dev/sda2 * 7 8517 68364607+ 7 HPFS/NTFS
/dev/sda3 8518 11306 22402642+ 5 Extended
/dev/sda4 11372 11977 4867695 db CP/M / CTOS / ...
/dev/sda5 8583 11306 21880530 83 Linux
/dev/sda6 8518 8582 522049+ 82 Linux swap / Solaris

Partition table entries are not in disk order


does this change how I need to configure gfxboot? Since it says sda instead of hda, as implied in the tutorial?

I followed everything closely but still get the same 'ol grub. And, no error messages to tell me whats wrong =/

thanks for any help!

[unconcrete]

I've installed gfxboot by following step-by-step the instructions of the current Howto. At least I thought to have done it correctly but probably not. Actually at the system reboot, [Ubuntu edgy eft - Nvidia Geforce FX5500- Athlon 64 3700+processor] Nothing happens. Only the same black/blue screen with os choices as used before gfxboot. I've put message.suse in my boot/grub dir without success then I've tried other themes but the problem is the same: gfxboot doesn't work.
This is my current menu.lst.
gfxmenu /boot/grub/message.blusplash
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=a6515639-89a1-4753-a488-94309cc1ec80 ro
# kopt_2_6=root=/dev/sda6 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,5)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##
# Splashimage - uncommented since I've installed gfxmenu
# foreground = 0000ff
# background = ffffff
# splashimage=(hd0,5)/boot/grub/splashimages/hpp.xpm.gz

title Ubuntu, kernel 2.6.17-10-generic
root (hd0,5)
kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda6 ro quiet splash
initrd /boot/initrd.img-2.6.17-10-generic
quiet
savedefault
boot

title Ubuntu, kernel 2.6.17-10-generic (recovery mode)
root (hd0,5)
kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda6 ro single
initrd /boot/initrd.img-2.6.17-10-generic
boot

title Ubuntu, memtest86+
root (hd0,5)
kernel /boot/memtest86+.bin
quiet
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1
...
========endfile=================================== ==============================
This is my partition table:
armonica@persik-desktop:~$ sudo fdisk -l
Password:

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 9249 74292561 7 HPFS/NTFS
/dev/sda2 9250 11531 18330165 c W95 FAT32 (LBA)
/dev/sda4 16145 24321 65681752+ 5 Extended
/dev/sda5 16145 16291 1180746 82 Linux swap / Solaris
/dev/sda6 16292 24321 64500943+ 83 Linux
armonica@persik-desktop:~$
I've seen my linux partition is /dev/sda6 which has been mounted on (hd0,5). I've used these values in the grub environment:
sudo grub
grub> find /boot/grub/stage1
(hdx,y) # this will be the output
grub> root (hd0,5)
grub> setup (hd0,5)
...I've tried to install other themes but nobody work.Please help.

unconcrete

[kraigory]

^^ i'm in pretty much the same predicament. Any ideas?

[Malac]

@kraigory (http://ubuntuforums.org/member.php?u=180363) and unconcrete (http://ubuntuforums.org/member.php?u=176792)
sudo grub-install /dev/sdxyWhere x is a,b,c,etc. y is 1,2,3,etc.

[kraigory]

kraigory@elihu:~$ sudo fdisk -l
Password:

Disk /dev/sda: 98.5 GB, 98522403840 bytes
255 heads, 63 sectors/track, 11978 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 6 48163+ de Dell Utility
/dev/sda2 * 7 8517 68364607+ 7 HPFS/NTFS
/dev/sda3 8518 11306 22402642+ 5 Extended
/dev/sda4 11372 11977 4867695 db CP/M / CTOS / ...
/dev/sda5 8583 11306 21880530 83 Linux
/dev/sda6 8518 8582 522049+ 82 Linux swap / Solaris

Partition table entries are not in disk order

Disk /dev/sdb: 2048 MB, 2048729600 bytes
64 heads, 63 sectors/track, 992 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 992 1999749+ 6 FAT16
kraigory@elihu:~$


@kraigory and unconcrete
Code:

sudo grub-install /dev/sdxy

Where x is a,b,c,etc. y is 1,2,3,etc.

Which one do I do? sda5 for the linux partition, or sdb1 for the "device boot" ?

[unconcrete]

Ops... I've lost the most important part of the process.
Now I've done sudo grub-install sda1 and now gfxboot works correctly. I'll update my little how to.
Thanks a million, kraigory
:)
unconcrete

[unconcrete]

There's another problem now. It happened my ntfs partition was lost as I 've installed grub in my dev/sda1 device. The vfat partion is still visible but i've lost Windos XP.
How can I recover it?

Thanks in advance
I know I should not be so hurried to avoid to backup my mbr with dd but I have not done it. :frown:
unconcrete

Some information...
--------------------------------------------------------CURRENT PARTITIONS------------------------------------------
armonica@persik-desktop:~$ sudo fdisk -l
Password:
Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 9249 74292561 7 HPFS/NTFS # no more neither visible nor mounted #
/dev/sda2 9250 11531 18330165 c W95 FAT32 (LBA) #ok
/dev/sda4 16145 24321 65681752+ 5 Extended #ok
/dev/sda5 16145 16291 1180746 82 Linux swap / Solaris #ok
/dev/sda6 16292 24321 64500943+ 83 Linux #ok

---------------------------------------------------------CURRENT EDGY FSTAB----------------------------------------
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda6
UUID=a6515639-89a1-4753-a488-94309cc1ec80 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda1
UUID=E4C0300AC02FE212 /media/pippo ntfs defaults,nls=utf8,umask=0222,gid=46 0 0
# /dev/sda2
UUID=1006-16B2 /media/pluto vfat defaults,utf8,umask=0000,gid=46 0 0
# /dev/sda3
# UUID=c0ec6d7e-f4b4-40d5-ab11-a04b99ec3392 /media/sda3 ext3 defaults 0 2
# /dev/sda5
UUID=9206b41a-6f52-477e-8394-bdfadc71329e none swap sw 0 0
/dev/hdd /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hdc /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/sda2 /media/pluto vfat defaults 0 0
/dev/sda1 /media/pippo ntfs nls=iso8859-1,users,umask=0222,user,ro 0 0
/dev/sda5 /media/sda5 swap defaults 0 0

------------------------------------ MOUNT ERRORS-------------------------------------------------------------
armonica@persik-desktop:~$ sudo mount -a
Password:
mount: special device /dev/disk/by-uuid/E4C0300AC02FE212 does not exist
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
----------------------------------------------DMSG OUTPUT ----------------------------------------------------------
armonica@persik-desktop:~$ dmesg | tail
[17180099.296000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[17180099.296000] NTFS-fs error (device sda1): ntfs_fill_super(): Not an NTFS volume.
[17180216.748000] NTFS-fs warning (device sda1): is_boot_sector_ntfs(): Invalid boot sector checksum.
[17180216.748000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Primary boot sector is invalid.
[17180216.748000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[17180216.748000] NTFS-fs error (device sda1): ntfs_fill_super(): Not an NTFS volume.
[17180247.524000] NTFS-fs warning (device sda1): is_boot_sector_ntfs(): Invalid boot sector checksum.
[17180247.524000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Primary boot sector is invalid.
[17180247.524000] NTFS-fs error (device sda1): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[17180247.524000] NTFS-fs error (device sda1): ntfs_fill_super(): Not an NTFS volume.
---------------------------------------------------------------------------------------------------

[Malac]

If you have an XP Install CD insert that and boot from it.
When asked for options choose "Repair Using Recovery Console" from the options. (I am not sure of the exact wording.)

You will be asked which XP you want to log on to then asked for the administrator password. If you haven't set up a password just press Enter.
When you get to the prompt type:
fixbootThen
fixmbrThis should restore your XP boot sector and MBR.

If you have no install CD but can access another XP machine then;
Format a floppy
Copy the ntldr, ntdetect.com and boot.ini to it.
Alter the boot.ini on the floppy to point at where your XP partition is.
e.g.[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(1)\Window s
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\Windows="Microsoft Windows XP Professional" /fastdetect /noexecute=optinThen boot off the floppy.
This is a handy disk to let you boot XP if anything happens again.

[mrfuzzemz]

If you don't have a windows install CD the free alternative is to download SuperGrub. You can repair your MBR with grub and even with the windows bootloader. It's free, it's a small image and it is extremely helpful.

[Haama]

Hi! I've also tried to install the gfxboot. Everything else has gone well except when i run sudo grub
grub> setup (hd0,0) i get Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal)
Running "embed /boot/grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal)
Running "install /boot/grub/stage1 (hd0,0) /boot/grub/stage2 p /boot/grub/menu
.lst "... succeeded
Done.

when i reboot it starts a non-graf grub titled GRUB stage 1.5
how can I make the gfx work?

[kvonb]

If you don't have a windows install CD the free alternative is to download SuperGrub. You can repair your MBR with grub and even with the windows bootloader. It's free, it's a small image and it is extremely helpful.

Do you actually understand that super grub disk?

I've tried it several times, it might as well be written entirely in Chinese, it makes no sense to me :/

It asks nonsensical questions then just seems to go around in circles doing unfathomable things and failing miserably!

[mrfuzzemz]

I had no idea what I was doing until I looked at the documentation on the website:

http://users.bigpond.net.au/hermanzone/SuperGrubDiskPage.html

After browsing through its many menus I became forever indebted to it.

[mlock]

when I try to run command find /boot/grub/stage1 I get a error 15 code : file not found HELP and yes I'm new too linux

[4tro]

try running any alternatives to that command

find /boot/stage1

find /grub/stage1

the idea is you find where your grub is installed.

[kvonb]

when I try to run command find /boot/grub/stage1 I get a error 15 code : file not found HELP and yes I'm new too linux

You have to run that command from inside grub.

Open a terminal (menu->accessories) and type:

sudo grub

then you can type:

find /boot/grub/stage1

[bootsbradford]

What is the easiest way of removing GfxBoot?

Thanks.

[4tro]

the easiest way to remove the graphical screen is to remove the entry from your menu.lst.

the slightly more difficult way is to remove the installed gfxboot, reinstalling normal grub and then reinstalling it to your MBR, which are basically the same steps as followed for the how-to

[bootsbradford]

the easiest way to remove the graphical screen is to remove the entry from your menu.lst.

the slightly more difficult way is to remove the installed gfxboot, reinstalling normal grub and then reinstalling it to your MBR, which are basically the same steps as followed for the how-to

Thanks for the reply.

What is MBR? How do I install normal grub to it?

Thanks in anticipation!

[4tro]

Thanks for the reply.

What is MBR? How do I install normal grub to it?

Thanks in anticipation!

sudo grub

grub> find /boot/grub/stage1
(hdx,y) # this will be the output
grub> root (hdx,y)
grub> setup (hdx)

[epgui]

I've got a 64 bit architecture and gfxboot refuses to install.
Any way to fix that?
epgui@epgui:~/Desktop$ sudo dpkg -i grub-gfxboot_0.97-5_i386.deb
dpkg: error processing grub-gfxboot_0.97-5_i386.deb (--install):
package architecture (i386) does not match system (amd64)
Errors were encountered while processing:
grub-gfxboot_0.97-5_i386.deb
epgui@epgui:~/Desktop$


edit -
i gave up on x64 and installed i386 version of Ubuntu.
After trying out a combination of solutions i happened to be able to work it out.
Works well now, i'm trying to get a good theme to show up.

[mrfuzzemz]

I have gfxboot wokring fine, but from the package available on this thread. What is up with the gfxboot package in the ubuntu repositories? If we could explain how to get that going, it shouldn't depend on the architecture. Heck, we could start a new thread for it that includes ALL the necessary instructions (such as grub-install).

[Ub1476]

Hi, I did something wrong any when booting I know end up in the grub command line. Could anyone tell me how to restore all settings, or at least tell me how to get into a normal command line I need to edit menu.lts)? Thanks in advance.

[mrfuzzemz]

I would say boot up an Ubuntu or Knoppix Live CD and mount your boot or root partitiion (whichever one has menu.lst). Then you can edit to your hearts content.

[Ub1476]

Yep fixed it. Edited from /menu/disk/boot/grub

[Ub1476]

Still nothing changes. I followed the instructions correctly, and got no errors.

Here's my menu.lst if of any help:

gfxmenu /boot/grub/message.ubugrey
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
## password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,2)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##

title Ubuntu, kernel 2.6.20-16-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro quiet splash
initrd /boot/initrd.img-2.6.20-16-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-16-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro single
initrd /boot/initrd.img-2.6.20-16-generic

title Ubuntu, kernel 2.6.20-15-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro single
initrd /boot/initrd.img-2.6.20-15-generic

title Ubuntu, memtest86+
root (hd0,2)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Windows Vista/Longhorn (loader)
root (hd0,0)
savedefault
makeactive
chainloader +1

[ayoli]

Still nothing changes. I followed the instructions correctly, and got no errors.

Here's my menu.lst if of any help:

gfxmenu /boot/grub/message.ubugrey
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
## password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,2)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##

title Ubuntu, kernel 2.6.20-16-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro quiet splash
initrd /boot/initrd.img-2.6.20-16-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-16-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro single
initrd /boot/initrd.img-2.6.20-16-generic

title Ubuntu, kernel 2.6.20-15-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=cf4a2202-f314-4e26-83a5-926fb442e101 ro single
initrd /boot/initrd.img-2.6.20-15-generic

title Ubuntu, memtest86+
root (hd0,2)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Windows Vista/Longhorn (loader)
root (hd0,0)
savedefault
makeactive
chainloader +1


i think you miss a line like this at the begining og your menu.lst:
gfxmenu (hd0,1)/boot/grub/message.blusplash
replace message.blusplash with your theme

[TravMan63]

Thanks for the 'how to'.

Observations:

It's interesting - grub is uninstalled, yet called on later - I'm guessing that gfxmenu takes over. Also - running grub as user gives 'command not found', where as sudo or su allows the editing to take place. (sudo is n/a in Elive...)

On a dual-boot machine (Elive, Ubuntu) - I had two 'boot' folders (actually Ubuntu's boot I placed on separte partition (hda,5) - and is mounted to /boot - so does 'boot folder' exist? , Elive has two partitions (Home and Root - Elive's boot is in it's root partition in /boot/grub/...(hda,14) - Installed Ubuntu lastly (Elive has it's own message.elive) - which 'destroyed' the gfxmenu (all OS choices were availible in the 'Ubuntu grub' menu.lst).

If I recall correctly - Elive's installer didn't allow for a choice as to where the /boot partition was.... (how does that work - what's the best way - install all OS's /boot to the same area - Linux's usually play nicely and pick up other OS's - some windows installs do (at least with thier own 'brethern' (have XP and 98 on another machine)

While in Ubuntu, I did the 'grub (0,x)' (<-syntax is incorrect) - it showed the grub on the Elive install... installed to that - and - got the message.elive to show - just had to copy the menu.lst from the 'ubuntu grub'...
(that was in Elive - the Elive menu.lst - had just Elive in it...)
(had to mount the 'ubuntu grub' parition - I used gparted to accomplish that)

It was my intent (I did most of this work from the Ubuntu install) - to have the 'ubuntu grub' be used - (edited that menu.lst .... made a symbolic link to the original message.elive, copied the original file - neither worked... changed the directory to /grub/message.elive etc etc etc... didn't work)

In the end - it works - :KS just not the way I had tried to force it (to use the 'ubuntu grub'... :confused: (maybe I needed to do the install to the hda,5 - that seems obvious - but everything else was in place - perhaps by doing that it allows the gfxmenu to actually be active - and I guess that is why it must be installed - in ubuntu - when it existed already in elive...)

Now I'll be working on designing a 'message' or two...
I've seen some tuts/howtos -

----
oh the joys... (if it sounds cornfusing - well...IT WAS :lolflag:)
-----

Is there a way to position the text (from the menu.lst)?
The text goes off screen to the right...
and when it is scrolled - the rightmost becomes garbled...

--------
TM

[kvonb]

Anyone know what this means?

kev@kev:~$ sudo grub-install --recheck /dev/sda2
Probing devices to guess BIOS drives. This may take a long time.


GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]
grub> root (hd0,1)
Filesystem type is reiserfs, partition type 0x83
grub> setup --stage2=/boot/grub/stage2 --prefix=/boot/grub (hd0,1)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/reiserfs_stage1_5" exists... yes
Running "embed /boot/grub/reiserfs_stage1_5 (hd0,1)"... 18 sectors are embedded.
succeeded
Running "install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0,1) (hd0,1)1+18 p (hd0,1)/boot/grub/stage2 /boot/grub/menu.lst"... failed

Error 6: Mismatched or corrupt version of stage1/stage2
grub> quit

GFXboot will NOT take on this damned computer, it works perfectly on my laptop which has the same partition/software setup.

I'm starting to think that the problem is the hard disk controller on this mainboard, it just will not take!

Here is the output of fdisk -l

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 5099 40957686 7 HPFS/NTFS
/dev/sda2 5100 24259 153902700 83 Linux
/dev/sda3 24260 24321 498015 82 Linux swap / Solaris

This is a completely new install of both Windows and Linux, fresh partitions too.

:confused:

[kvonb]

Well for some unknown reason it worked this time!!!!

I really don't know what I did differently, but here is what I did:

The message. files in /boot/grub were permissions: 1600744, so I made them 600644 which is the same as the other files in that folder.

Next I opened a terminal and instead of running the command with su, I used a real root prompt:

sudo su

then ran the command again

grub-install /dev/sda2

.....and it took!

Maybe it was the small animal I accidentally sacrificed to the god of binary during the reboot!

[tapash]

I want to make my own gfxboot screen. Is there any posibiliy that i can make my own package. Please reply

[4tro]

I want to make my own gfxboot screen. Is there any posibiliy that i can make my own package. Please reply
have a look at one of the first posts, it's all there ;-)

[merlwiz79]

Here is one that I made for Linux Mint 3.0.
Click to Enlarge
http://farm2.static.flickr.com/1117/1191230849_e31e6f2c33_m.jpg (http://farm2.static.flickr.com/1117/1191230849_68d271ee85_o.png)
http://www.MegaShare.com/260297
http://rapidshare.com/files/50290971/message.mint1.2

[matiit]

Hi,
I cant use any theme from this topic...
I have issue:
Invalid file format.
/place/of/message

[merlwiz79]

Hi,
I cant use any theme from this topic...
I have issue:
Invalid file format.
/place/of/message

Which ones are you using?
Are you putting the right line in menu.lst?
gfxmenu /boot/grub/message.xxxx
replacing xxxx with the name of your file.
Mine is mint1.2 on the previous page.
So it would begfxmenu /boot/grub/message.mint1.2

[RaZer0r]

I need some help with this...
I can't get it to work, or I'm missing something, or I'm doing something wrong, but every time i reboot, i get the ordinary grub menu, and not the graphical one....

what I did:
sudo apt-get remove grub2 (as i had that package installed instead of grub)
installed the downloaded package and installed it (dpkg -i package.deb)
downloaded the message.ubugrey and moved it to the /boot/grub/ folder
gfxmenu /boot/grub/message.ubugrey --> this is the first line in my menu.lst
sudo grub

grub> find /boot/grub/stage1
(hd0,0) # this will be the output
grub> root (hd0,0)
grub> setup (hd0)

and rebooted...

tried the grub-install /dev/sda too... allways the messages never errored whatsoever, always no problem, but never the graphical menu came...

Truely need some help, never had this before, a guide was most of the time clear and understandfull (and this one is too, but what's wrong i'm not sure :)

[ayoli]

I need some help with this...
I can't get it to work, or I'm missing something, or I'm doing something wrong, but every time i reboot, i get the ordinary grub menu, and not the graphical one....

what I did:
sudo apt-get remove grub2 (as i had that package installed instead of grub)
installed the downloaded package and installed it (dpkg -i package.deb)
downloaded the message.ubugrey and moved it to the /boot/grub/ folder
gfxmenu /boot/grub/message.ubugrey --> this is the first line in my menu.lst
sudo grub

grub> find /boot/grub/stage1
(hd0,0) # this will be the output
grub> root (hd0,0)
grub> setup (hd0)

and rebooted...

tried the grub-install /dev/sda too... allways the messages never errored whatsoever, always no problem, but never the graphical menu came...

Truely need some help, never had this before, a guide was most of the time clear and understandfull (and this one is too, but what's wrong i'm not sure :)

Did you do that at the end ?
sudo grub-install hdx,y
In your case it should be 0,0 for x,y (hda, first partition):
sudo grub-install hd0,0

[RaZer0r]

yes I allready did that too, without any results...

[Yes]

I did everything in the first post, plus

sudo echo gfxmenu /boot/grub/message.suse > /boot/grub/menu.lst

grub-install /dev/hda

(Replacing hda with sda, which was what fdisk -l said my hard drive was). Wen I rebooted, it just gave me the command prompt that you get when you type "sudo grub" in the terminal. Any reason why this might be?

I should also mention that I'm running a clean install of Feisty (So I don't have any partitions left over from previous installations).

Ok, I just booted from the live CD, and now I can boot into Ubuntu. Now this is what happens: I get the same GRUB screen, except at the top it says the GRUB version. When I chose the operation system, it says stuff like the kernal, root(0,0), initrd (I think that's what it was), and stuff like that. Then it goes into the normal boot process. So it seems as though what I've done has changed something, but I still don't have the graphics. I'm using the message.blusplash, if that matters.

I tried running the sudo grub-install, and I got some errors. First, I tried

sudo grub-install /dev/hd0
(0 was the 'x' value for hd(x,y)). That gave me the error

/dev/hd1: Not found or not a block device.
Then I tried using sdb (I'm connected to my network now, so my Ubuntu hard drive is sdb, not sda), and I got this error:

/dev/sdb1 does not have any corresponding BIOS drive.

Can anyone help me with these errors?

Thanks.

[Malac]

I did everything in the first post, plus

sudo echo gfxmenu /boot/grub/message.suse > /boot/grub/menu.lst

grub-install /dev/hda(Replacing hda with sda, which was what fdisk -l said my hard drive was). Wen I rebooted, it just gave me the command prompt that you get when you type "sudo grub" in the terminal. Any reason why this might be?

I should also mention that I'm running a clean install of Feisty (So I don't have any partitions left over from previous installations).

Ok, I just booted from the live CD, and now I can boot into Ubuntu. Now this is what happens: I get the same GRUB screen, except at the top it says the GRUB version. When I chose the operation system, it says stuff like the kernal, root(0,0), initrd (I think that's what it was), and stuff like that. Then it goes into the normal boot process. So it seems as though what I've done has changed something, but I still don't have the graphics. I'm using the message.blusplash, if that matters.

I tried running the sudo grub-install, and I got some errors. First, I tried

sudo grub-install /dev/hd0(0 was the 'x' value for hd(x,y)). That gave me the error

/dev/hd1: Not found or not a block device.Then I tried using sdb (I'm connected to my network now, so my Ubuntu hard drive is sdb, not sda), and I got this error:

/dev/sdb1 does not have any corresponding BIOS drive.Can anyone help me with these errors?

Thanks.
The last step should be this for you :
sudo grub-install hd0,0or possibly just:
sudo grub-install hd0There is no /dev/ if you are using grub notation, which is what this is if it uses numerals.

No corresponding BIOS drive usually means your computer BIOS can't boot off that drive/partition. Sometimes this is just a setting in the BIOS, other times it's hard coded.

Hope this helps

[Yes]

Shouldn't the numbers be the same numbers that I got when from "find /grub/stage1"? So it would be "sudo grub-install hd1,0" ?

[ayoli]

Shouldn't the numbers be the same numbers that I got when from "find /grub/stage1"? So it would be "sudo grub-install hd1,0" ?

yes it should, so yes it would if find /grub/stage1 outputs grub> root (hd1,0)

[Malac]

yes it should, so yes it would if find /grub/stage1 outputs grub> root (hd1,0)
Sorry my mistake if that's the output of grub then that's it.

[Yes]

Well, I tried
sudo grub-install hd1,0

and I got the same
/dev/sdb1 does not have any corresponding BIOS drive.

error. Any other ideas?

Thanks.

[kvonb]

Well, I tried
sudo grub-install hd1,0and I got the same
/dev/sdb1 does not have any corresponding BIOS drive.error. Any other ideas?

Thanks.

Try doing the whole thing again, but use a pure root account instead.

sudo su

.....then go through the whole process again:

grub
grub> find /boot/grub/stage1
(hdx,y) # this will be the output
grub> root (hdx,y)
grub> setup (hdx)
grub> quit
grub-install /dev/sdb1

If you get an error about stage2, run that last command a second time, it worked for me, and I have no clue why!

You should get:

Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

I'm still of the belief that it's something to do with having old partitions on your drive that were NOT created by the latest version of Ubuntu, ie left over from an earlier install.

Even ones created by the beta version of Feisty gave me problems, but if I wiped the entire drive and created new partitions it worked EVERY time!

The problem seems to stem from when they merged the IDE and SCSI drivers into the same lib (release of Feisty or last few updates to Feisty beta), ie we all of a sudden started calling /dev/hdx, /dev/sdx.

I have gfxboot working on all of my machines now, but I had to trash the partitions and create new ones. ](*,)

[Yes]

Well, for some reason this time the output for
find /grub/stage1

was (hd0,0). Anyways, I tried
grub-install /dev/sdb1

, and it gave me the
/dev/hd1: Not found or not a block device.

error. I tried
grub-install hd0,0

and it said that the installation was completed successively, but when I restarted my computer, nothing had changed with GRUB.

Also, it's not old partitions left over from previous installations, because I've only installed Ubuntu once on this computer.

Thanks for the help.

[kvonb]

OK, all I can suggest is to make sure that the message.xxxx that you are using (in /boot/grub) is set to be owned by root, group root.

Then have a look at /boot/grub/menu.lst and make sure that hiddenmenu IS commented out, like so:

#hiddenmenu

....and change the time to 10 seconds (not sure if that will make any difference though!)

Oh,and also colours:

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color white/blue

Again not sure if it makes a difference, but that is from my menu.lst and it works :)

[Yes]

Yeah, all my settings are the same as yours, and my message.blusplash was owned by root. Thanks, though.

What does the stuff in /boot/grub/devices.map do? I switched the numbers, and that didn't seem to do anything at all.

[kvonb]

Yeah, all my settings are the same as yours, and my message.blusplash was owned by root. Thanks, though.

What does the stuff in /boot/grub/devices.map do? I switched the numbers, and that didn't seem to do anything at all.

No idea, but I think that file is created/modified when you do a grub-install.

GFXboot is problematic to say the least, I've had hit and miss success with it over the last year or so, and can't seem to find any rhyme or reason in it's workings :/

Here is EXACTLY what I did if it helps at all:

sudo apt-get remove grub
sudo dpkg -i grub-gfxboot_0.97-5_i386.deb
sudo cp message.ubugrey /boot/grub/
sudo chown root:root /boot/grub/message.ubugrey
sudo chmod 644 /boot/grub/message.ubugrey
sudo cp /boot/grub/menu.lst /boot/grub/menu.lst_backup
sudo gedit /boot/grub/menu.lst....made sure that hiddenmenu was commented out, and
also added: gfxmenu /boot/grub/message.ubugrey as the very first line.

sudo su
grub
grub>find /boot/grub/stage1
(hd0,1)
grub> root (hd0,1)
grub> setup (hd0)
grub> quit

fdisk -l
Disk /dev/sda: 20.0 GB, 20003880960 bytes
255 heads, 63 sectors/track, 2432 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 638 5124703+ 7 HPFS/NTFS
/dev/sda2 639 2351 13759672+ 83 Linux
/dev/sda3 2352 2432 650632+ 5 Extended
/dev/sda5 2352 2432 650601 82 Linux swap / Solaris

grub-install /dev/sda1 spat out some error about stage2!
grub-install /dev/sda1 spat out:
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

Rebooted and it was there!

I attached a .gz file containing my fstab/device.map/message.ubugrey/menu.lst just in case you can get any useful info from them :)

[Yes]

Could anyone tell me where I want to install Grub (/dev/xxxxx) based on fdisk output? I really don't want to overwrite my Windows MBR...

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 30401 244196001 7 HPFS/NTFS

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 12 96358+ 83 Linux
/dev/sdb2 19263 19457 1566337+ 82 Linux swap / Solaris
/dev/sdb3 18335 19262 7454160 83 Linux
/dev/sdb4 13 18334 147171465 83 Linux

Partition table entries are not in disk order

Thanks.

[ayoli]

Could anyone tell me where I want to install Grub (/dev/xxxxx) based on fdisk output? I really don't want to overwrite my Windows MBR...

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 30401 244196001 7 HPFS/NTFS

Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 12 96358+ 83 Linux
/dev/sdb2 19263 19457 1566337+ 82 Linux swap / Solaris
/dev/sdb3 18335 19262 7454160 83 Linux
/dev/sdb4 13 18334 147171465 83 Linux

Partition table entries are not in disk order

Thanks.

according to your fdisk output , you should do:
grub-install /dev/sda1
whath's the output for this ?
grub>find /boot/grub/stage1

[Yes]

grub>find /boot/grub/stage1

Gives me "Error 15: File not found".
grub>find /grub/stage1

Gives me "hd(1,0)".

grub-install /dev/sda1
Gives me "/dev/sdb1 does not have any corresponding BIOS drive."

Thanks.

[ayoli]

grub>find /boot/grub/stage1

Gives me "Error 15: File not found".
grub>find /grub/stage1

Gives me "hd(1,0)".

grub-install /dev/sda1
Gives me "/dev/sdb1 does not have any corresponding BIOS drive."

Thanks.
Actually grub have not the same numeration as /dev
hd0 stands for hda or sda
hd1 for hdb or sdb
so in your case that should be (as root, or with sudo) :

grub-install hd1,0
or
grub-install /dev/sdb1

[Yes]

Nope, same errors.

[Yes]

Edit: Success!!!! I followed everything in this (http://ubuntuforums.org/showpost.php?p=2827955&postcount=395) post, with a few changes: Instead of
find /boot/grub/stage1
I used
find /grub/stage1
instead of
sudo grub-install hdx,y
I used
sudo grub-install /dev/sda1
and instead of adding "gfxmenu /boot/grub/message.xxxx" to menu.lst, I added "gfxmenu /grub/stage1".

Thank you so much to everyone who helped =D .

[sirsean1227]

well... thanks for having it make no sense..... like the menu.list... what part of it do i edit... i got to there.... had no f****** clue where to put the thing.... thanx for the half *** walk through... i hope i can restart this thing now!!!

[4tro]

well... thanks for having it make no sense..... like the menu.list... what part of it do i edit... i got to there.... had no f****** clue where to put the thing.... thanx for the half *** walk through... i hope i can restart this thing now!!!

maybe you should read more carefully, and don't start yelling and ranting first....

[franco07-chaosad]

Thanks, it's great :)

[WishMaster]

erhm...

Your first 'command' is "remove grub"
A few steps later, we need to type "grub"
We just removed it??!

[jw5801]

You remove the default grub and then install a graphical grub. That's what the second step is :p

[Yes]

I would highly suggest using the method laid out in this post: http://ubuntuforums.org/showpost.php?p=2827955&postcount=395. The OP's process seems to be missing a key step that gives a lot of people trouble.

[ScarfaceIII]

-- Howto make you own theme --


mkdir /home/name/whatever
cpio -i < /boot/grub/message.suse # replace it by the name of you message
edit the pictures
sudo ls . |cpio -o > /boot/grub/message.new

Reboot and enjoy ;)

Hi! Great How to, thanks. But: I got a question. I can't quite understand the part up here in quotes. How do I edit your and build one mine? =)

Could you explain a little bit more, for example:
-why do I have to build a new directory if I don't enter it? (cd /home/name/whatever)
-what does the command cpio -i ? I don't know it, could you explain what happens?
- How do I edit pictures? And most of all, WHAT pictures? The output of the command cpio -i is just "250 blocks" and then? thanks, bye

[4tro]

Hi! Great How to, thanks. But: I got a question. I can't quite understand the part up here in quotes. How do I edit your and build one mine? =)

Could you explain a little bit more, for example:
-why do I have to build a new directory if I don't enter it? (cd /home/name/whatever)
-what does the command cpio -i ? I don't know it, could you explain what happens?
- How do I edit pictures? And most of all, WHAT pictures? The output of the command cpio -i is just "250 blocks" and then? thanks, bye
you indeed have to enter the directory before you execute the cpio
the cpio command makes and reads a sort of archive of the files, a single file...

let's just say it's somewhat similar to tar... but don't use tar for this :P

[WishMaster]

You remove the default grub and then install a graphical grub. That's what the second step is :p
hmm... I uninstalled "grub" via Synaptic and installed "gfxboot" via Synaptic.

The proposed package here is "grub-gfxboot", I guess it is something different from the "gfxboot" in Synaptic

[theff]

EDIT: nevermind

[light-angel]

i've followed all in the guide you provided but still have no efect. When i boot i get the same ugly screen.

this is What i've done:

First remove your old grub


sudo apt-get remove grub
Then Install the gfxboot-grub




sudo dpkg -i grub-gfxboot_0.97-5_i386.deb
then we're going to move the message




sudo cp message.suse /boot/grub/ # the suse can be replaced by the one you downloaded
Then edit your menu.lst




sudo cp /boot/grub/menu.lst /boot/grub/menu.lst_backup
sudo gedit /boot/grub/menu.lst
and make it use gfxboot



gfxmenu /boot/grub/message.suse # the suse can be replaced


Then do :


sudo grub
grub> find /boot/grub/stage1
(hdx,y) # this will be the output
grub> root (hdx,y)
grub> setup (hdx)
-- Howto make you own theme --


Code:

mkdir /home/name/whatever
cpio -i < /boot/grub/message.suse # replace it by the name of you message
edit the pictures
sudo ls . |cpio -o > /boot/grub/message.new

[mjpoetic]

i've followed all in the guide you provided but still have no efect. When i boot i get the same ugly screen.

I find the easiest way to use gfxboot is to:

REMOVE OLD GRUB
sudo apt-get remove grubDOWNLOAD & INSTALL GRUB-GFXBOOT
wget http://quasarfreak.googlepages.com/grub-gfxboot_0.97-5_i386.debsudo dpkg -i grub-gfxboot_0.97-5_i386.debGET THE ANIMATED IMAGE & COPY IT TO YOUR GRUB DIRECTORY
(You can also get some from gnome-look.org or from the bottom of post #1 in this thread)
wget http://quasarfreak.googlepages.com/message.susesudo cp message.suse /boot/grub/EDIT YOUR GRUB MENU TO USE THE ANIMATED IMAGE
(good practice to backup the file first and then edit)
sudo cp /boot/grub/menu.lst /boot/grub/menu.lst_backupsudo gedit /boot/grub/menu.lstADD THE FOLLOWING LINE (IN RED) TO THE TOP OF THE FILE SO IT LOOKS LIKE THIS...
gfxmenu /boot/grub/message.suse

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.THEN, INSTALL THE BOOT-LOADER
(this may vary based on your computer)
sudo grub-install hd0
OR
sudo grub-install /dev/sda

:KS:KS:KS
ENJOY!!! Keep in mind that this is just a template and you can edit it to your liking. Also, these are general instructions but you may have to edit the lines to fit your computer.

Check out the GRUB editing script called "GrubEd" as it will help with this too:
http://ubuntuforums.org/showthread.php?t=228104&highlight=Script+for+grub

[Sonic Reducer]

i have followed the instructions twice, and i still get the default GRUB setup.

heres some terminal outputs:

Removed GRUB: (keep in mind i did all this three reboots ago, so these terminal commands are in past-tense)
ryan@ryan-desktop:~$ sudo apt-get remove grub
Password:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package grub is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Dpkg'ed grub-gfxboot:
ryan@ryan-desktop:~$ sudo dpkg -i grub-gfxboot_0.97-5_i386.deb
(Reading database ... 129013 files and directories currently installed.)
Preparing to replace grub-gfxboot 0.97-5 (using grub-gfxboot_0.97-5_i386.deb) ...
Unpacking replacement grub-gfxboot ...
Setting up grub-gfxboot (0.97-5) ...

moving message.blusplash:
sudo cp message.suse /boot/grub/

Backed up and editing menu.lst:
ryan@ryan-desktop:~$ sudo cp /boot/grub/menu.lst /boot/grub/menu.lst_backup
ryan@ryan-desktop:~$ sudo gedit /boot/grub/menu.lst

here is my menu.lst (note the first line, did i do that right?):
gfxmenu /boot/grub/message.blusplash
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=cf3dbb90-6e5d-4560-a89a-6b1ebdc01697 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,1)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##

title Ubuntu, kernel 2.6.20-16-generic
root (hd0,1)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cf3dbb90-6e5d-4560-a89a-6b1ebdc01697 ro quiet splash
initrd /boot/initrd.img-2.6.20-16-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-16-generic (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=cf3dbb90-6e5d-4560-a89a-6b1ebdc01697 ro single
initrd /boot/initrd.img-2.6.20-16-generic

title Ubuntu, kernel 2.6.20-15-generic
root (hd0,1)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=cf3dbb90-6e5d-4560-a89a-6b1ebdc01697 ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
quiet
savedefault

title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=cf3dbb90-6e5d-4560-a89a-6b1ebdc01697 ro single
initrd /boot/initrd.img-2.6.20-15-generic

title Ubuntu, memtest86+
root (hd0,1)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Home Edition
root (hd0,0)
savedefault
makeactive
chainloader +1

then i sudo GRUB'ed:
ryan@ryan-desktop:~$ sudo grub
Probing devices to guess BIOS drives. This may take a long time.


GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ]

grub> grub> find /boot/grub/stage1 (NOTE: this was a copy/pasting typo)

Error 27: Unrecognized command

grub> find /boot/grub/stage1
(hd0,1)

grub> root (hd0,1)
Filesystem type is ext2fs, partition type 0x83

grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,1)/boot/grub/stage2 /boot/grub/menu.lst"... succeeded
Done.

i followed all this a third time in order to get the text to copy/paste here, i'm going to reboot again right after i post this. if i don't post again sounding very embarrassed assume it is still not working. thank you for anyone that can help me.

[mjpoetic]

Everything looks fine except for one thing: I see you have message.blusplash instead of message.suse which you have earlier in the instructions...just make sure that you are using the correct one.

Also, I really recommend using sudo grub-install rather than sudo grub. I have never had to use sudo grub. So in your case, just do

sudo grub-install hd0

then your problem should go away

[Sonic Reducer]

Everything looks fine except for one thing: I see you have message.blusplash instead of message.suse which you have earlier in the instructions...just make sure that you are using the correct one.

i want to use the blusplash (which is one of the alternatives listed in the bottom of the first post of this thread)

i did the sudo grub-install hd0 in the terminal and this came up:
ryan@ryan-desktop:~$ sudo grub-install hd0
Installation finished. No error reported.
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/sdc

so i hope this worked. thank you for the help

[mjpoetic]

Yea it should work. In fact that message is for you to check if you wanted it to go to that specific boot sector or another. Without confusing the situation, I think you got what you needed to get done.

[Sonic Reducer]

it looks so freaking cool. thank you PingunZ!

[#Reistlehr-]

anyone know a good tutorial, or the file format that these grubgfx images use?

[satsura]

Hi!
Pls, tell me, how delete bottom text in grub?
http://img223.imageshack.us/img223/1152/102431mv5.th.jpg (http://img223.imageshack.us/my.php?image=102431mv5.jpg)

[4tro]

Hi!
Pls, tell me, how delete bottom text in grub?
http://img223.imageshack.us/img223/1152/102431mv5.th.jpg (http://img223.imageshack.us/my.php?image=102431mv5.jpg)

follow the how to on page 1, what you have here is a standard grub with splashimage, not gfxboot-grub
in gfxboot the text is gone

[shinji257]

Then do : sudo grub

grub> find /boot/grub/stage1
(hdx,y) # this will be the output
grub> root (hdx,y)
grub> setup (hdx)


When I do this I get the message "Error 15: File Not Found". Why am I getting this error and what can I do to resolve this? This is a relatively new install. Grub boots just fine otherwise.

This is a new install of Ubuntu. I'll try another install inside of a virtual machine and see where it goes with that so I don't mess up the current one badly. Thanks for any assistance.

P.S. - This is Ubuntu Gutsy 7.10 that I am running. It is dual booting with Windows XP right now. I can post the menu.lst if you want. On that note I might just try a reinstall anyways and see if it corrects it by combining the boot and root partitions together...

EDIT: Nevermind on this. I reinstalled Ubuntu taking a new partiton layout and now I don't have this issue anymore. My partition layout was originally as follows

47MB Dell Diag (primary)
200GB Windows XP (primary - active)
100MB /boot (primary)
500MB Mozilla profile space (logical)
29GB / (logical)
1GB swap (logical)

This was done to keep the boot area from getting too big or out of hand. Now for some reason it doesn't work. The root was set to (hd0,2) which is correct but grub didn't like it. So I changed it to this...

47MB Dell Diag (primary)
200GB Windows XP (primary)
29GB / (primary)
500MB Mozilla profile space (logical)
1GB swap (logical)

And now I don't get that error anymore. I'm going to apply the updates and see what happens from here...

EDIT: I got it working. The error reappeared as soon as I installed gfxboot but I went ahead and tried to do it anyways. I reinstalled the boot loader and it works fine now. I also had backed up the update-grub files from both /sbin and /usr/sbin and then restored it after installing gfxboot.

[4tro]

When I do this I get the message "Error 15: File Not Found". Why am I getting this error and what can I do to resolve this? This is a relatively new install. Grub boots just fine otherwise.

This is a new install of Ubuntu. I'll try another install inside of a virtual machine and see where it goes with that so I don't mess up the current one badly. Thanks for any assistance.

P.S. - This is Ubuntu Gutsy 7.10 that I am running. It is dual booting with Windows XP right now. I can post the menu.lst if you want. On that note I might just try a reinstall anyways and see if it corrects it by combining the boot and root partitions together...

EDIT: Nevermind on this. I reinstalled Ubuntu taking a new partiton layout and now I don't have this issue anymore. My partition layout was originally as follows

47MB Dell Diag (primary)
200GB Windows XP (primary - active)
100MB /boot (primary)
500MB Mozilla profile space (logical)
29GB / (logical)
1GB swap (logical)

This was done to keep the boot area from getting too big or out of hand. Now for some reason it doesn't work. The root was set to (hd0,2) which is correct but grub didn't like it. So I changed it to this...

47MB Dell Diag (primary)
200GB Windows XP (primary)
29GB / (primary)
500MB Mozilla profile space (logical)
1GB swap (logical)

And now I don't get that error anymore. I'm going to apply the updates and see what happens from here...

EDIT: I got it working. The error reappeared as soon as I installed gfxboot but I went ahead and tried to do it anyways. I reinstalled the boot loader and it works fine now. I also had backed up the update-grub files from both /sbin and /usr/sbin and then restored it after installing gfxboot.

the error was that your stage1 wasn't located at /boot/grub/stage1 , but probably at /grub/stage1 on the partition mounted as /boot, there's a difference there

[shinji257]

the error was that your stage1 wasn't located at /boot/grub/stage1 , but probably at /grub/stage1 on the partition mounted as /boot, there's a difference there

That was just it. I had tried that one too. Both /boot/grub/stage1 and /grub/stage1 produced this error. Regardless I did get it working and it works great now. Thanks for the reply though!

[lotacus]

Am I missing something here? I am reading posts that describe commands and such that are not even listed in the tutorial. Is the tutorial incomplete? I find it amazing that there are 49 pages of posts for a small installation of gfxboot, which for the most part doesn't seem to work on a whole lot of systems. mine, being one of them. Of couerse I do understand that every system, kernel and distros may be different, but seeing as this is posted in the ubuntu forums, i would expect the tutorial somewhat generic. I see nothing about grub or grub2 install/remove etc.. in the tutuorial, perhaps it can be modified to include a little more then what is already there.

my "grub" hd0,5 however when I "find" grub and then do the sudo grub hd0,5 I see some out put of Sda... wierd

[Eriksmits596]

I have done EXACTLY as I should and tried 3 times but it's still the old menu. What do I do wrong :( Here's my menu.lst

P.S. I run gutsy

# gfxmenu /boot/grub/message.new
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.


## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=e97d6f4c-9a37-465c-bbdf-298d4f0ce66c ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,1)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd0,1)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=e97d6f4c-9a37-465c-bbdf-298d4f0ce66c ro quiet splash
initrd /boot/initrd.img-2.6.22-14-generic
quiet

title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=e97d6f4c-9a37-465c-bbdf-298d4f0ce66c ro single
initrd /boot/initrd.img-2.6.22-14-generic

title Ubuntu 7.10, memtest86+
root (hd0,1)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Professional
root (hd0,0)
savedefault
makeactive
chainloader +1

[4tro]

I have done EXACTLY as I should and tried 3 times but it's still the old menu. What do I do wrong :( Here's my menu.lst


# gfxmenu /boot/grub/message.new
# menu.lst - See: grub(:cool:, info grub, update-grub(:cool:
# grub-install(:cool:, grub-floppy(:cool:,
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.P.S. I run gutsy

uncomment the # gfxmenu /boot/grub/message.new

[Eriksmits596]

Haha I forgot to do grub-install after:p But now it works!!! Nice

[Eriksmits596]

Somebody who knoms where I can find this theme?
http://www.pro-linux.de/berichte/jpgs/suse10/suse10-boot.jpg

[PurposeOfReason]

I got it to work, but it doesn't take up my full resolution (1280x800) but more is just a centered 800x600. The VGA= options didn't change anything and I even tried resizing the images in the theme.

[merlwiz79]

Here is a new one I compiled.
http://farm3.static.flickr.com/2094/2097093584_776e7ffe38.jpg (http://farm3.static.flickr.com/2094/2097093584_78763709de_o.png)
message.red
http://www.4shared.com/file/31585981/9e6e2573/message.html
Source:
http://www.4shared.com/file/31936439/693eb95d/gfxboot-theme-example.html

[autocrosser]

Somebody who knoms where I can find this theme?

I pulled the theme info from the 10.2 install disc--but don't know how to compile it--you might find someone that has 10.2 installed & get the message from them---The file is too big to post--E me if you want the source.....

EDIT: I found the answer on linuxforums.org--- this uses the message.suse that comes with 10.2---

In /boot/message there is a configuration file that controls the randomness of the "walking penguins". However /boot/message is an archive (http://www.linuxforums.org/forum/#) and you have to decompress.
Open a terminal and Code:
su
cd /boot
cp message message.old
mkdir messagetemp
cd messagetemp
cpio -iv < /boot/message
nano gfxboot.cfg
Then you should change penguin from -1 to 100
it should look like this Quote:
penguin=100
Save and recreate the archive
Code:
ls | cpio -ov > /boot/message
This should be ok. Post if any problems



I have the message & will post it as message.zip

just remove the .zip & do what you need to do to get it in your boot---adapt the instructions above to your use...

EDIT2: message.peng.zip I THINK will work--remove the .zip & insert it--I'll do a reboot with it & report if it works....

EDIT3: gfxboot said that the message is too big--I would guess that it needs to have some of the Suse stuff to work--I'll play with it----

EDIT4: Well--I shrunk the message down to 271k & it still won't work :( I'll try some more this week--I guess that the GfxBoot Suse uses allows bigger file sizes---

[silverdarkness]

Edit gfxboot themes for widescreen:

1)
extract the files using the commands from pg 1

mkdir /home/name/whatever
cpio -i < /boot/grub/message.suse # replace it by the name of you message

2) Open one of the image in gimp. Under image choose scale image and unlock the aspect ratio.

3) You need to shrink the image so when it gets stretched to full screen it looks normal. The new image width is 0.83x the original image width. Calculate the new image width put it in and click scale. Save the image

4) Do the same for any other images.

5) Put the files back in the message file using:
sudo ls . |cpio -o > /boot/grub/message.whatever (from pg 1 again)

Thats it. The text will still be elongated but i dont really mind.

[merlwiz79]

grub-gfxboot 0.97-11 for Ubuntu i386
http://www.gnome-look.org/content/show.php/grub-gfxboot+for+Ubuntu+i386?content=71647

Can't make amd64 if someone want's I can sent the soucre for the amd64 to make into .debs.

[merlwiz79]

EDIT4: Well--I shrunk the message down to 271k & it still won't work :( I'll try some more this week--I guess that the GfxBoot Suse uses allows bigger file sizes---Needs to be less than 170 kbs.

[autocrosser]

Needs to be less than 170 kbs.

Interesting--the "stock" message that comes with 10.2 is about 370k--any idea about what makes their GFXboot work with larger file sizes?

[neoraptor]

Is it possible to put a 1920x1200 image?

[subs]

cool!!!

[merlwiz79]

Is it possible to put a 1920x1200 image?
It depends on the back.jpg.
The end file has to be less than 170k so it won't look that good.
Here is the same back.jpg from message.red but resized @ 1920x1200.
http://www.4shared.com/file/32068519/641202fe/message.html