grub emerge make boot screen and others unreadable
At Wed, 09 Jul 2008 13:20:43 -0700 Joshua D Doll <joshua.doll@gmail.com> wrote:
> Neil Bothwick wrote:
>> On Wed, 09 Jul 2008 12:25:30 -0700, Joshua D Doll wrote:
>>
>>
>>> splashimage has nothing to with the kernel. The kernel isn't even
>>> loaded at this point. It's very likely that the splashimage line is
>>> pointing to a nonexistent file.
>>>
>>
>> Grub hangs if that's the case.
>>
>>
>>
> I've had exactly the same thing happen to me when I've had the path
> wrong for the splashimage. You get a highly unreadable screen, but it
> still "works".
I agree with joshua. That is what happened to me.
allan
--
gentoo-user@lists.gentoo.org mailing list
07-09-2008, 08:57 PM
Allan Gottlieb
grub emerge make boot screen and others unreadable
At Wed, 09 Jul 2008 21:15:16 +0100 Neil Bothwick <neil@digimed.co.uk> wrote:
> On Wed, 09 Jul 2008 14:02:59 -0400, Allan Gottlieb wrote:
>
>> The latest stable emerge of grub decided to add
>>
>> splashimage=(hd0,2)/boot/grub/splash.xpm.gz
>>
>> to my grub.conf
>>
>> Since I do not have support for this in my kernel the screen was
>> unreadable. Should I file this as a bug?
>
> The fact that the ebuild modifies grub.conf in any way should be
> considered a bug IMO.
That was my error. The file grub.conf was not modified.
Instead a file pointed to by grub.conf (the splash) was moved.
sorry,
allan
--
gentoo-user@lists.gentoo.org mailing list
07-09-2008, 09:30 PM
Denis
grub emerge make boot screen and others unreadable
Thanks for this thread. I had a bunch of gibberish on the screen,
too, after the most recent emerge and figured it was grub but didn't
know why. Strangely, the splash image was missing from /boot/grub -
is it not supposed to be in /boot or was this an ebuild error??
I found the splash image (splash.xpm.gz) under /usr/share/grub, and
moving it to /boot/grub fixed this issue for me.
Denis
--
gentoo-user@lists.gentoo.org mailing list
07-09-2008, 10:59 PM
Allan Gottlieb
grub emerge make boot screen and others unreadable
At Wed, 09 Jul 2008 17:30:12 -0400 Denis <denis.che@gmail.com> wrote:
> Thanks for this thread. I had a bunch of gibberish on the screen,
> too, after the most recent emerge and figured it was grub but didn't
> know why. Strangely, the splash image was missing from /boot/grub -
> is it not supposed to be in /boot or was this an ebuild error??
>
> I found the splash image (splash.xpm.gz) under /usr/share/grub, and
> moving it to /boot/grub fixed this issue for me.
Indeed this is one thing in the bug
http://bugs.gentoo.org/show_bug.cgi?id=231039
Apparently the ebuild recommendation about
"emerge --config grub" was supposed to get the file
copied over (and presumably it would).
However the actual recommendation was for those who
wish to
install grub files to another device (like a usb stick)
Since many like me had no desire to do this, we didn't
run the configure and the moved splash file bit us.
allan
--
gentoo-user@lists.gentoo.org mailing list
07-09-2008, 11:03 PM
Neil Bothwick
grub emerge make boot screen and others unreadable
On Wed, 09 Jul 2008 13:20:43 -0700, Joshua D Doll wrote:
> > Grub hangs if that's the case.
> I've had exactly the same thing happen to me when I've had the path
> wrong for the splashimage. You get a highly unreadable screen, but it
> still "works".
Did the wrong path point to something? When I got it wrong, grub refused
to load the menu.lst file at all. Mind you, that was a couple of years
ago. Maybe handles things differently now, I haven't dared find out!
--
Neil Bothwick
Disinformation is not as good as datinformation.
07-09-2008, 11:07 PM
Joshua D Doll
grub emerge make boot screen and others unreadable
Neil Bothwick wrote:
On Wed, 09 Jul 2008 13:20:43 -0700, Joshua D Doll wrote:
Grub hangs if that's the case.
I've had exactly the same thing happen to me when I've had the path
wrong for the splashimage. You get a highly unreadable screen, but it
still "works".
Did the wrong path point to something? When I got it wrong, grub refused
to load the menu.lst file at all. Mind you, that was a couple of years
ago. Maybe handles things differently now, I haven't dared find out!
It pointed to nothing. I actually had the wrong drive and/or partition
in the line. I say it worked but really the screen was so jacked it was
useless.
--Joshua Doll
--
gentoo-user@lists.gentoo.org mailing list
07-10-2008, 12:31 AM
Allan Gottlieb
grub emerge make boot screen and others unreadable
At Thu, 10 Jul 2008 00:03:01 +0100 Neil Bothwick <neil@digimed.co.uk> wrote:
> On Wed, 09 Jul 2008 13:20:43 -0700, Joshua D Doll wrote:
>
>> > Grub hangs if that's the case.
>
>> I've had exactly the same thing happen to me when I've had the path
>> wrong for the splashimage. You get a highly unreadable screen, but it
>> still "works".
>
> Did the wrong path point to something?
No. In grub.conf I had and still have
splashimage=(hd0,2)/boot/grub/splash.xpm.gz
There used to be such a file. But the recent emerge removed it
and put the file in /usr/share/grub. So the splashimage target didn't
exist.
> When I got it wrong, grub refused to load the menu.lst file at
> all. Mind you, that was a couple of years ago. Maybe handles things
> differently now, I haven't dared find out!
Grub did load and if left alone would successfully load the default
target. However,
1. The menu grub normally displays (i.e. the grub.conf entries) was
absent or at least the screen was dark.
2. When the kernel starting booting, the screen was nearly unreadable
until the kernel set the console font, at which point ...
... poof--all was well.