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

Malac

February 11th, 2007, 03:04 PM

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 ******* 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

February 28th, 2007, 05:28 PM

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

March 4th, 2007, 12:23 AM

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

March 10th, 2007, 05:00 PM

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

March 28th, 2007, 05:24 AM

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

March 28th, 2007, 08:36 AM

Feisty can't have it by default? :(

tuxbear

March 28th, 2007, 08:45 AM

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

March 28th, 2007, 09:09 AM

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

March 28th, 2007, 02:42 PM

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

March 28th, 2007, 08:12 PM

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

March 28th, 2007, 11:15 PM

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

March 28th, 2007, 11:36 PM

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

el mariachi

March 29th, 2007, 07:48 AM

hoe can I know what number is my HD?

Xappe

March 29th, 2007, 05:38 PM

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

Malac

March 29th, 2007, 06:18 PM

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

March 31st, 2007, 12:24 AM

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

March 31st, 2007, 05:41 AM

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

March 31st, 2007, 12:02 PM

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

March 31st, 2007, 01:15 PM

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

April 2nd, 2007, 02:09 PM

what about amd64 grub-gfxboot.deb?

And how to use the gxboot package from repositories

kvonb

April 2nd, 2007, 02:58 PM

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

April 2nd, 2007, 03:34 PM

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

April 2nd, 2007, 06:06 PM

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

April 2nd, 2007, 07:48 PM

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

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

April 3rd, 2007, 05:53 AM

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

April 4th, 2007, 07:41 PM

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

April 4th, 2007, 08:14 PM

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

April 5th, 2007, 04:10 AM

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

April 7th, 2007, 11:14 AM

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

Malac

April 7th, 2007, 12:43 PM

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

April 7th, 2007, 01:49 PM

thx now it works perfectly:lolflag:

kvonb

April 8th, 2007, 05:04 AM

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

April 8th, 2007, 07:36 PM

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

April 10th, 2007, 03:51 AM

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

April 11th, 2007, 01:32 PM

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

April 12th, 2007, 10:20 PM

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

April 13th, 2007, 01:37 AM

@lo-Loki

sudo grub-install hd0

Io-Loki

April 13th, 2007, 02:38 PM

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

April 13th, 2007, 03:40 PM

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

April 13th, 2007, 03:48 PM

already tried. same error :(

Malac

April 13th, 2007, 05:32 PM

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

April 14th, 2007, 03:33 AM

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

April 14th, 2007, 01:42 PM

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

April 15th, 2007, 03:46 AM

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

April 15th, 2007, 11:00 AM

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

April 15th, 2007, 06:17 PM

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

April 15th, 2007, 09:45 PM

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

April 15th, 2007, 10:04 PM

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

April 15th, 2007, 10:15 PM

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

April 16th, 2007, 10:54 PM

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

April 18th, 2007, 01:01 AM

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

April 18th, 2007, 09:10 AM

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

April 18th, 2007, 10:28 PM

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

bootsbradford

April 20th, 2007, 09:25 PM

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

May 1st, 2007, 05:55 PM

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

May 3rd, 2007, 09:59 PM

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

May 4th, 2007, 04:36 PM

Why doesn't this work with Feisty?

4Play

May 5th, 2007, 12:59 AM

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

May 5th, 2007, 10:16 AM

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

May 5th, 2007, 01:12 PM

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

mrfuzzemz

May 5th, 2007, 01:34 PM

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

May 5th, 2007, 01:44 PM

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

May 5th, 2007, 01:46 PM

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

May 5th, 2007, 03:28 PM

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

May 5th, 2007, 03:53 PM

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

May 5th, 2007, 09:03 PM

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

May 5th, 2007, 09:24 PM

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

May 5th, 2007, 10:21 PM

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

May 6th, 2007, 05:23 AM

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

May 6th, 2007, 05:19 PM

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

May 6th, 2007, 10:48 PM

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

u-foka

May 7th, 2007, 12:46 AM

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

ayoli

May 7th, 2007, 12:35 PM

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

May 7th, 2007, 12:58 PM

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

mrfuzzemz

May 7th, 2007, 01:02 PM

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

May 7th, 2007, 10:48 PM

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

May 8th, 2007, 12:29 PM

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

May 8th, 2007, 01:00 PM

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

May 9th, 2007, 05:43 PM

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

May 9th, 2007, 05:50 PM

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

May 9th, 2007, 08:10 PM

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

May 10th, 2007, 07:33 AM

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

May 10th, 2007, 08:39 AM

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

May 10th, 2007, 02:56 PM

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

May 10th, 2007, 03:35 PM

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

May 10th, 2007, 05:36 PM

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

May 10th, 2007, 06:34 PM

Wonderfull Image thx for that.

Neobuntu

May 10th, 2007, 06:37 PM

On Feisty the "missing command" is always:

Yields:

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

Neobuntu

May 10th, 2007, 08:44 PM

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

Neobuntu

May 10th, 2007, 08:53 PM

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

Neobuntu

May 10th, 2007, 09:26 PM

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

May 10th, 2007, 11:07 PM

@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

May 11th, 2007, 04:53 AM

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

May 11th, 2007, 05:29 AM

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

May 11th, 2007, 05:52 AM

No joy.

mrfuzzemz

May 11th, 2007, 03:07 PM

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

May 11th, 2007, 04:24 PM

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

May 11th, 2007, 05:05 PM

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

Malac

May 11th, 2007, 08:43 PM

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

May 11th, 2007, 09:21 PM

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

May 12th, 2007, 01:08 AM

^Edit bump

kvonb

May 12th, 2007, 06:19 AM

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

May 12th, 2007, 01:03 PM

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

May 12th, 2007, 06:40 PM

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

May 13th, 2007, 10:55 AM

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

May 13th, 2007, 06:06 PM

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

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

Neobuntu

May 14th, 2007, 10:03 PM

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

May 15th, 2007, 07:32 AM

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

May 15th, 2007, 08:14 AM

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

May 15th, 2007, 01:01 PM

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

May 16th, 2007, 02:07 AM

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

mrfuzzemz

May 16th, 2007, 02:13 AM

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

May 16th, 2007, 09:17 AM

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

May 16th, 2007, 01:03 PM

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

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

May 16th, 2007, 02:08 PM

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

May 16th, 2007, 08:12 PM

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

May 16th, 2007, 09:08 PM

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

May 17th, 2007, 11:42 AM

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

May 17th, 2007, 12:54 PM

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

May 18th, 2007, 12:01 PM

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

u-foka

May 22nd, 2007, 06:52 PM

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

May 22nd, 2007, 08:30 PM

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

May 22nd, 2007, 09:30 PM

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

fooman

May 22nd, 2007, 09:32 PM

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

May 23rd, 2007, 08:14 PM

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

May 23rd, 2007, 09:29 PM

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

June 2nd, 2007, 05:19 PM

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

June 2nd, 2007, 06:25 PM

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

June 2nd, 2007, 08:12 PM

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

June 3rd, 2007, 10:11 AM

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

June 3rd, 2007, 10:34 AM

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

June 3rd, 2007, 10:47 AM

Hello people! Thanks for the lovley guide.

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

sudo grub-install /dev/hda

Cyclist

June 4th, 2007, 06:26 AM

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

June 4th, 2007, 01:41 PM

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

June 4th, 2007, 04:52 PM

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

June 5th, 2007, 07:54 PM

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.

## 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

# 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

## 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

June 6th, 2007, 07:21 AM

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

June 11th, 2007, 07:06 AM

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

Neobuntu

June 11th, 2007, 11:50 AM

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

June 11th, 2007, 12:37 PM

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

June 11th, 2007, 01:26 PM

Is there a repo for this anywhere?

nbayiha

June 12th, 2007, 08:13 AM

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

download gfxboot

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

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

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.

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

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

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

June 14th, 2007, 09:24 AM

It worked!

T H A N K Y O U !

rollps

June 14th, 2007, 09:57 AM

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

June 14th, 2007, 10:47 AM

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

June 14th, 2007, 10:58 PM

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

June 17th, 2007, 07:41 PM

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

4tro

June 19th, 2007, 06:23 PM

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

June 20th, 2007, 07:11 PM

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

/grub/message.ubugrey: Invalid file format

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

June 21st, 2007, 07:41 AM

gfxgrub works in fiesty fine for me

4tro

June 21st, 2007, 08:39 AM

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

June 21st, 2007, 04:35 PM

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:

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

June 22nd, 2007, 08:59 PM

Hello, I've finally figured this out.

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

June 22nd, 2007, 09:05 PM

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

June 23rd, 2007, 08:28 AM

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

July 1st, 2007, 07:14 AM

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

July 1st, 2007, 04:13 PM

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.

## 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

# 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

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