Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Feb 2012 11:33:05 -0500
From:      Rick Miller <vmiller@hostileadmin.com>
To:        =?ISO-8859-1?Q?Erik_N=F8rgaard?= <norgaard@locolomo.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: pxeboot.bs and vlan tagging
Message-ID:  <CAHzLAVGYbbhyeCQCf6_KE=P_EuSFni2zOZb76XwFwYYC8-MpPw@mail.gmail.com>
In-Reply-To: <CAHzLAVHxpWyvcb-ioaEXOLkentujUbT6Fd7eEois4SHQa-MVAQ@mail.gmail.com>
References:  <CAHzLAVEKavBHqz4atdqys6KDJXqGpinCcEPg7--Nqn9ZZCTH4Q@mail.gmail.com> <4F2FF7D3.2030707@locolomo.org> <CAHzLAVHxpWyvcb-ioaEXOLkentujUbT6Fd7eEois4SHQa-MVAQ@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
>> 2) do you fetch the kernel successfully?
>>
>> When using tftp, The kernel and kernel modules are fetched before the me=
mory
>> file system, so do pxeboot fetch the kernel but not the mfsroot?
>>
>> The reason for these questions is that your problem may be with the kern=
el
>> and kernel modules and not pxeboot. Just to be sure.
>
> I see what you are saying. =A0We will have to look at the packet
> captures to make that determination.

The target system loads pxeboot.bs and consequently requests the
following files:

/boot/boot.4th (which it does not find)
/boot/loader.rc
/boot/loader.4th
/boot/support.4th
/boot/defaults/loader.conf
/boot/device.hints
/boot/loader.conf

It is at this point where the failure occurs.  The contents of loader.conf =
are:

mfsroot_load=3D"YES"
mfsroot_type=3D"mfs_root"
mfsroot_name=3D"/boot/mfsroot"

Does this seem consistent with what you were theorizing that it's the
kernel that has the problem with vlan tagging and not pxeboot.bs?


--=20
Take care
Rick Miller



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CAHzLAVGYbbhyeCQCf6_KE=P_EuSFni2zOZb76XwFwYYC8-MpPw>