All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Invalid symbol table on NetBSD boot
Date: Fri, 8 Jan 2010 22:35:37 +0100	[thread overview]
Message-ID: <20100108213537.GA22519@thorin> (raw)
In-Reply-To: <4B467FE9.3040200@labri.fr>

On Fri, Jan 08, 2010 at 01:44:25AM +0100, Grégoire Sutre wrote:
> Robert Millan wrote:
>
>> I suggest you test if GRUB Legacy's Multiboot loader supports this
>> properly, as the code I used derives from that.
>
> Yes, the problem disappears with GRUB Legacy's multiboot.  Moreover, I  
> noticed another issue: the command line is stripped (first word missing)  
> with GRUB 2's multiboot. Here are the logs.  After setting the root  
> variable appropriately, I get:
>
> --- With GRUB Legacy ---------------------------------------------------
> grub> kernel /netbsd.generic -z root=wd0a
> [...]
> --- With GRUB 2 -------------------------------------------------------
> grub> multiboot /netbsd.generic -z root=wd0a

There was an intentional backward-incompatible (but still compatible with
the specification) change.  The equivalent command on GRUB 2 would be:

grub> multiboot /netbsd.generic /netbsd.generic -z root=wd0a

First argument is the file being open;  in GRUB Legacy it's implicitly also
the first arg passed to payload, which is less flexible than letting user
specify it.  It doesn't have to be the filename at all, and usually the
payload doesn't need this information.

I'm not sure if this explains your missing word problem, but it sounds like
it could be related.

-- 
Robert Millan

  "Be the change you want to see in the world" -- Gandhi



  reply	other threads:[~2010-01-08 21:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 18:07 Invalid symbol table on NetBSD boot Grégoire Sutre
2010-01-07 21:36 ` Robert Millan
2010-01-08  0:44   ` Grégoire Sutre
2010-01-08 21:35     ` Robert Millan [this message]
2010-01-09 15:33       ` Grégoire Sutre

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=20100108213537.GA22519@thorin \
    --to=rmh@aybabtu.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.