From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Booting EFI (or work-arounds to install 9front on GPT partition)?
Date: Sat, 6 Dec 2014 12:19:04 +0100 [thread overview]
Message-ID: <a11e3f6f8c8ef1c20820e282b0526ed8@felloff.net> (raw)
In-Reply-To: <5454299.WklWF47Z7a@krypton>
we currently have no gpt support in fdisk. but mischief is working
on it.
from the description, it seems the efi loader has some problems.
i assume the "some sort of shell" refers to the boot console (see
9boot(8)). in one case, it seemed to be unable to locate the kernel
file from the boot media.
the bootloader; as a last action; prints "boot" before jumping to the
kernel. if that just hangs, it means the kernel fails *before* it is
able to attach to the GOP framebuffer.
possible causes (speculation):
- bad memory map (see *e820= boot parameter)
- efi doesnt provide GOP (see *bootscreen= boot parameter)
- maybe kernel image got corrupted (in memory?) due to wrong assumtptions
- you might have tried to load an older kernel that has no *bootscreen= support
- acpi?
what we can do to get some evidence:
hit any key on boot to get to the bootloader console (until you see the
">" prompt).
then read what boot parameters where established by the loader:
*e820=, *bootscreen=, and *acpi=
you can use the "show" command to print the boot parameter environment.
you can try serial console by specifying console=0 before booting the
kernel. that way, we might see more early output of the kernel.
if thats not an option, then all we can do commenting out code before
bootscreeninit() in the kenrel to figure out where it fails.
the efi loader has pxe boot support. so you might be able todo the
debugging this way without having to copy stuff to usb or burn cdroms.
keep in mind that the efi stuff is very fresh and has only been tested
with thinkpads and qemu/vmware and vbox so far. it would be good to
know what kind of machine this is.
--
cinap
next prev parent reply other threads:[~2014-12-06 11:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 16:58 Jens Staal
2014-12-06 0:47 ` [9front] " mischief
2014-12-06 11:19 ` cinap_lenrek [this message]
2014-12-07 5:55 ` Jens Staal
2014-12-07 13:53 ` cinap_lenrek
2014-12-07 5:42 Jens Staal
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=a11e3f6f8c8ef1c20820e282b0526ed8@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).