From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Beeblebrox <zaphod@berentweb.com>
Cc: grub-devel <grub-devel@gnu.org>
Subject: Re: Grub kfreebsd with pxe & nfs
Date: Sat, 1 Nov 2014 17:30:13 +0300 [thread overview]
Message-ID: <20141101173013.0b9a3405@opensuse.site> (raw)
In-Reply-To: <20141026211938.4a709655@rsbsd.rsb>
В Sun, 26 Oct 2014 21:19:38 +0200
Beeblebrox <zaphod@berentweb.com> пишет:
>
> > > * First is, code snippet to get mount_root to use NFS V3 instead of
> > > V2. grub.cfg code should be as below, but does not work
>
> > This should be kFreeBSD....
> Still does not work with
> {set kFreeBSD.boot.nfsroot.options="nfsv3"}
> mount_root this time does not hang, but resulting mounted root is still V2
>
> * grub.cfg does not accept kFreeBSD for all parameters, and needs mixed syntax. Example:
> menuentry 'FreeBSD 11_amd64' {
> kfreebsd kernel/kernel
> # NOT kFreeBSD kernel/kernel
kfreebsd is not parameter, it is command. kFreeBSD. is variable name
prefix.
> set FreeBSD.acpi_load=YES
> kfreebsd_loadenv device.hints
> # NOT kFreeBSD_loadenv device.hints
> kfreebsd_module kernel/if_sis.ko
> # NOT kFreeBSD_module kernel/if_sis.ko
>
> * I disabled these 3 params:
> # set kFreeBSD.vfs.root.mountfrom="nfs:192.168.2.1:/data/amd64"
> # set kFreeBSD.vfs.root.mountfrom.options="ro"
> # set kFreeBSD.boot.nfsroot.options="nfsv3"
> And saw that FreeBSD boots normally through grub. This means that the {set kFreeBSD.*} settings are very likely being ignored as boot settings.
It is possible to verify that those variables are actually passed from
grub to kernel?
> The mount_root is successful because FreeBSD executes what is passed
from dhcp.
>
> Regards.
prev parent reply other threads:[~2014-11-01 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 18:03 Grub kfreebsd with pxe & nfs Beeblebrox
2014-10-26 18:24 ` Andrei Borzenkov
2014-10-26 19:19 ` Beeblebrox
2014-11-01 14:30 ` Andrei Borzenkov [this message]
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=20141101173013.0b9a3405@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=zaphod@berentweb.com \
/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).