From: Constantine Kousoulos <wuwei@freemail.gr>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: multiboot header error
Date: Tue, 29 May 2007 21:48:14 +0300 [thread overview]
Message-ID: <465C756E.8000506@freemail.gr> (raw)
After successfully installing GRUB2 from cvs (thanks Jerone!), i
decided to further test it on my amd64 machine.
At first, i built the sample kernel from
http://www.gnu.org/software/grub/manual/multiboot/multiboot.html#Example-OS-code
using the '-m32' gcc flag and by marking boot.S with the '.code32'
directive. All these effectively created an elf32 image on my
amd64 machine which built and booted without any trouble. :)
Then i proceeded to check if i can make GRUB2 boot the same kernel
as a native elf64 image. So, i removed the above mentioned flag
and directive, renamed any 'pushl' instruction to 'pushq', renamed
registers 'eax' to 'rex' and 'ebx' to 'rbx', modified the magic
number (0xe85250d6) and alingned it to 64-bits. When i tried to
boot it i got: "error: No multiboot header found". :(
Is there something i did or didn't do correctly? I would greatly
appreciate any feedback!
Thanks,
Constantine
next reply other threads:[~2007-05-29 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 18:48 Constantine Kousoulos [this message]
2007-05-30 15:51 ` multiboot header error Constantine Kousoulos
2007-05-31 18:51 ` Constantine Kousoulos
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=465C756E.8000506@freemail.gr \
--to=wuwei@freemail.gr \
--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.