From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] build 32-bit Linux loader as `linux', rename legacy loader to `linux16'
Date: Mon, 30 Mar 2009 16:35:52 +0200 [thread overview]
Message-ID: <49D0D8C8.4010801@gmail.com> (raw)
In-Reply-To: <1238419927.2868.6.camel@mj>
Pavel Roskin wrote:
> On Sat, 2009-03-28 at 13:53 +0100, Robert Millan wrote:
>
>>> Here's a patch to rename `linux' to `linux16' and build the 32-bit loader as
>>> simply `linux'.
>> Committed.
>
> Just for your information. With the old loader, booting an x86_64
> kernel in qemu emulating i386 would result in a kernel message:
>
> "This kernel requires an x86-64 CPU but only detected an i686 CPU
> Unable to boot - please use a kernel appropriate for your CPU"
>
> With the new loader, the kernel hands without showing any messages. It
> can be a kernel bug. Linux 2.6.29, current GRUB.
>
I confirm. I suppose that this check and message is bypassed with 32-bit
loading mode. IMO grub2 should provide an equivlent of this check. We
already have cpuid code. Does anyone know how to determine if kernel is
i386 or amd64?
--
Regards
Vladimir 'phcoder' Serbinenko
next prev parent reply other threads:[~2009-03-30 14:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 19:57 [PATCH] linux/gfxterm integration Robert Millan
2009-03-08 13:01 ` Robert Millan
2009-03-08 13:09 ` Robert Millan
2009-03-08 13:35 ` Vesa Jääskeläinen
2009-03-13 19:44 ` Robert Millan
2009-03-13 20:10 ` David Miller
2009-03-18 10:25 ` new Linux loader (Re: [PATCH] linux/gfxterm integration) Robert Millan
2009-03-18 13:09 ` phcoder
2009-03-21 17:50 ` Robert Millan
2009-03-22 16:00 ` [PATCH] build 32-bit Linux loader as `linux', rename legacy loader to `linux16' Robert Millan
2009-03-28 12:53 ` Robert Millan
2009-03-30 13:32 ` Pavel Roskin
2009-03-30 14:35 ` phcoder [this message]
2009-03-30 16:06 ` Yoshinori K. Okuji
2009-03-30 21:51 ` Pavel Roskin
2009-04-01 13:23 ` Robert Millan
2009-04-01 14:04 ` Pavel Roskin
2009-04-01 14:22 ` Robert Millan
2009-04-01 13:33 ` Robert Millan
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=49D0D8C8.4010801@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.