small problem after using this

[REBELinBLUE]

I used grime to add a menu image but it didn't like the image, the screen was scrabbled until about half way through the bootup, so I used grime to remove it and enabled the hide menu option again but it is still scrabbled on boot now.

Any idea how to fix this?

[Kyral]

I have the same problem, kinda. The problem with mine is that it never displays the bootimage (even after I cleared the "Hide Menu" box), and instead of the bootimage, it scrambles the screen until just after "configuring network interfaces"

[REBELinBLUE]

I have the same problem, kinda. The problem with mine is that it never displays the bootimage (even after I cleared the "Hide Menu" box), and instead of the bootimage, it scrambles the screen until just after "configuring network interfaces"
Yeh thats basically what I have, but even after reverting back

[REBELinBLUE]

Yeh thats basically what I have, but even after reverting back
Well I've solved the issue so I thought I'd let everyone know for anyone else who may have the issue later on.

Open /boot/grub/menu.lst in your editor of choice (with super user access of course) near the top you will see something similar to

splashimage=/grub/24866-UBUNTU.xpm.gz

Simply remove that line to fix the issue, if you want to hide the menu again add a line which says

hiddenmenu

[duff]

The scrambled console [usually] means the path to the splashimage points to a nonexistant file. Did you use the .deb or did you configure it yourself? If you used the .deb it assumes that grub is installed in /boot/grub, which maybe different than your setup.

[kanem]

The scrambled console [usually] means the path to the splashimage points to a nonexistant file. Did you use the .deb or did you configure it yourself? If you used the .deb it assumes that grub is installed in /boot/grub, which maybe different than your setup.
I noticed that the default behaviour of the .deb I downloaded was to look for the image in /grub and not /boot/grub. Once I changed the line from splashimage=/grub/image.xpm.gz to splashimage=/boot/grub/image.xpm.gz
it was fine

[chuck_theobald]

Cool! This thread helped me out too. In my case, I tried using:
splashimage=(fd0,0)/grub/splash.xpm.gz
which works in other cases (using hd0 instead of fd0 and on a Gentoo machine), but was scrambling the screen as described above. I was beginning to doubt GRUB 0.94's ability to use my graphics card, but using:
splashimage=/boot/grub/image.xpm.gz
works fine.
Thank you!
Cheers,
Chuck

[brian g]

am i supposed to be using an = between splashimage and the path?

[chuck_theobald]

am i supposed to be using an = between splashimage and the path?

In my testing, the equal sign is not necessary, a space will do. At least under GRUB 0.94.

[brian g]

In my testing, the equal sign is not necessary, a space will do. At least under GRUB 0.94.
ok thanks.

i can't seem to get it to work.
does GRUB cache the image somewhere?
my first attempt i had an image of the wrong dimensions
after fixing it i still can not get it to work.
i tried with /boot and i got a tiny image in the top left corner
i tried without /boot and i got weird ASCII all over while it was going through the boot process

[chuck_theobald]

ok thanks.

i can't seem to get it to work.
does GRUB cache the image somewhere?
my first attempt i had an image of the wrong dimensions
after fixing it i still can not get it to work.
i tried with /boot and i got a tiny image in the top left corner
i tried without /boot and i got weird ASCII all over while it was going through the boot process
I am not that familiar with the workings of GRUB, though the weird ASCII or a garbled screen is related to a missing file (read, incorrect path) as mentioned by duff, above. When this happens, I am still able to sorta kinda make out words through the static.
If, using /boot, you got a tiny image, I would say that path is correct, but there is still an issue with GRUB and your file. What editor did you use to produce the file? I would like to produce custom splash screens, and GRUB I would think does not support common binary formats, but does support compressed xpm. So far, I have not found an editor for xpm files.

[chuck_theobald]

I am not that familiar with the workings of GRUB, though the weird ASCII or a garbled screen is related to a missing file (read, incorrect path) as mentioned by duff, above. When this happens, I am still able to sorta kinda make out words through the static.
If, using /boot, you got a tiny image, I would say that path is correct, but there is still an issue with GRUB and your file. What editor did you use to produce the file? I would like to produce custom splash screens, and GRUB I would think does not support common binary formats, but does support compressed xpm. So far, I have not found an editor for xpm files.

[chuck_theobald]

<doh!> sorry about the dup post.

But another thing: check out your file with a text editor. See what values you have for columns and rows. The xpm format is a simple ascii and looks somewhat like this:

/* XPM */
static char *magick[] = {
/* columns rows colors chars-per-pixel */
"640 480 16 1",
" c #45347b",
". c #4b3885",
"X c #523e92",
"o c #59439e",
"O c #3c2d6b",
"+ c #413174",
"@ c #382a63",
"# c #5f48aa",
"$ c #6c51c0",
"% c #7d5edf",
"& c #7357cd",
"* c #664db5",
"= c #8867f3",
"- c #fafafc",
"; c #9385bf",
": c #cdc7e2",
/* pixels */
" . . . . . ",
" . . . . ",
" . . . . . ",
" . . ",
" . . . ",
" . . . . . ",
" .
etc...

[brian g]

i used the GIMP to edit the image.. 640x480 and 14 indexed colors

/* XPM */
static char * tuxgrafsplash_xpm[] = {
"640 480 15 1",
" c None",
". c #BDC0D7",
"+ c #ACAFC5",
"@ c #BBA792",
"# c #605B54",
"$ c #565C6F",
"% c #8A8996",
"& c #283038",
"* c #14191E",
"= c #C3C4D1",
"- c #AFABB3",
"; c #CFD0DE",
"> c #E2E2EB",
", c #F4E2C8",
"' c #DED192",