From: Stephen Kou <stephen@hyarros.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: UEFI Boot with Grub-Experimental
Date: Wed, 07 Jul 2010 18:39:55 -0700 [thread overview]
Message-ID: <4C352C6B.3080600@hyarros.com> (raw)
In-Reply-To: <4C351796.4080700@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1869 bytes --]
Given that grub itself works as 64-bit, I assume that the EFI firmware
is also 64-bit. And the grub itself loads a 64-bit kernel, so I'm
pretty sure everything is 64-bit in the pipeline.
Would 64-bit grub-efi work on a 32-bit efi firmware?
On 7/7/2010 5:11 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 07/08/2010 01:49 AM, stephen@hyarros.com wrote:
>> I've gotten UEFI booting working on some platforms, while other
>> platforms are not working. Specifically, booting on Intel's own
>> motherobards using Intel's own BIOS software (Specifically, the SOX5810J
>> motherboard) does not seem to work. I get the blank screen before the
>> kernel is about to come alive and after grub hands off execution to the
>> kernel. It boots fine with the noefi flag, but without noefi it doesn't
>> work.
>>
>>
> Check that they bit size of Linux and EFI match. If they don't Linux crashes
>> I've tried all sorts of kernel flags to try to get some sort of output:
>> earlyprintk, debug=all, loglevel=7, vga=771, etc. However, nothing
>> works -- the system is hung (numlock doesn't cause the LED to turn
>> on/off).
>>
>> Although I suspect this to be a kernel bug, could it be that grub is
>> setting up the video improperly or something? The AMIBIOS boards have
>> some special video mode that uses the gnu unicode font. The intel
>> boards only use the default system font.
>>
>> Any ideas on how to get some sort of output or kernel panic would be
>> appreciated.
>>
>> Thanks,
>> Stephen
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> http://lists.gnu.org/mailman/listinfo/grub-devel
>>
>>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
[-- Attachment #2: Type: text/html, Size: 2914 bytes --]
next prev parent reply other threads:[~2010-07-08 1:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 8:54 UEFI Boot with Grub-Experimental stephen
2010-06-30 9:40 ` Colin Watson
2010-06-30 17:10 ` stephen
2010-07-01 6:16 ` Reynald Lercier
2010-07-01 17:49 ` stephen
2010-07-01 17:54 ` stephen
2010-07-01 18:33 ` Seth Goldberg
2010-07-01 18:43 ` stephen
2010-07-02 14:14 ` Reynald Lercier
2010-07-02 17:16 ` stephen
2010-07-02 18:46 ` Reynald Lercier
2010-07-02 22:30 ` Stephen Kou
2010-07-07 23:49 ` stephen
2010-07-08 0:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-07-08 1:39 ` Stephen Kou [this message]
2010-07-01 19:09 ` Piscium
2010-09-05 20:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-04 1:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4C352C6B.3080600@hyarros.com \
--to=stephen@hyarros.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.