From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Cannot see Grub menu
Date: Sun, 12 Aug 2012 18:14:11 -0500 [thread overview]
Message-ID: <502838C3.904@gmail.com> (raw)
In-Reply-To: <20120812225232.GA7202@eisen.lan>
Frank Steinmetzger wrote:
> On Sun, Aug 12, 2012 at 02:31:07PM +0100, Mick wrote:
>
>>>>> So after the recent thread here about 32bit/64bit and some arguments
>>>>> from a friend, I made the switch from 32 bit to 64 bit (with a clean
>>>>> install from scratch of course). There’s one big problem I’m
>>>>> having: I cannot see the Grub (legacy) boot menu. It still
>>>>> functions alright, but I don’t see it.
>>>> […]
>>>> Do you use a splashimage in your grub.conf? Maybe without you will
>>>> get a working text mode Grub. Not that this should matter, but anyway.
> Yes, I used to use a self-made spash image; it shows a Windows-Logo-like
> stickers saying "Windows Vista incapable" with a Tux in it. :)
>
> Anyways, the file was missing, so I commented out the line, but to no avail.
> I tried a temporary grub.conf with the bare essentials (just one entry), and
> it didn't help either.
>
> Booting the same disk in qemu yields the same thing. So I gather it must be
> some borkage in grub itself. Perhaps I could try an older version, there are
> so many available right now.
>
>>> When grub is running and showing it's menu, the only thing active
> ---------------------------------------^
> *cough* *wink wink*
>
>> I have always used GRUB splashimage without genkernel and without anything
>> special to get it going other than the correct path in /boot/grub/grub.conf;
>> e.g.
>>
>> default 0
>> timeout 30
>> splashimage=(hd0,9)/boot/grub/splash.xpm.gz
> That's the way I used to too also. Very strange this all...
Just a thought. Could it be that the text and the background is the
same color? If you put white text on a white background, all you see is
white which looks blank, empty or whatever you want to call it.
Otherwise, I'm clueless. It's OK. I'm used to being clueless. lol
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
next prev parent reply other threads:[~2012-08-12 23:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 0:09 [gentoo-user] Cannot see Grub menu Frank Steinmetzger
2012-08-12 1:33 ` Mark Knecht
2012-08-12 1:41 ` Frank Steinmetzger
2012-08-12 2:28 ` Mark Knecht
2012-08-12 3:10 ` Dale
2012-08-13 9:18 ` Hinnerk van Bruinehsen
2012-08-13 11:21 ` Michael Hampicke
2012-08-12 9:47 ` Alex Schuster
2012-08-12 10:01 ` Alan McKinnon
2012-08-12 13:31 ` Mick
2012-08-12 22:52 ` Frank Steinmetzger
2012-08-12 23:08 ` Alan McKinnon
2012-08-13 1:43 ` Peter Humphrey
2012-08-13 8:03 ` Neil Bothwick
2012-08-13 17:43 ` Frank Steinmetzger
2012-08-14 0:16 ` [OT] " Peter Humphrey
2012-08-14 7:32 ` Neil Bothwick
2012-08-12 23:14 ` Dale [this message]
2012-08-13 17:46 ` Frank Steinmetzger
2012-08-13 21:31 ` Mick
2012-08-12 18:52 ` Michael Mol
2012-08-12 19:34 ` Mick
2012-08-12 20:06 ` Michael Mol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=502838C3.904@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox