Date: Sun, 7 Feb 2021 06:01:37 +0100 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Matthew Grooms <mgrooms@shrew.net>, freebsd-arm@freebsd.org Subject: Re: rpi4 network boot Message-ID: <2D8B4921-CCEB-4203-B616-C0C86612C1E5@googlemail.com> In-Reply-To: <d02ac38c-ac8e-fc84-ba65-1c49e9b73bbf@shrew.net> References: <d385f2b3-87e0-1bd5-d0f8-76ba1eb99816@shrew.net> <3a1acba5-8662-55cb-c5c4-98ec7873f78f@shrew.net> <e324f942-43ac-d2ab-3e7f-47ca91e40bee@shrew.net> <082BC0B9-2538-43D5-9D5E-C18B4DEE9ECB@googlemail.com> <de86ca7c-dd8a-511a-6063-ada6eb451488@shrew.net> <C6845ECB-23BE-48DB-BD78-A56814FCB39C@googlemail.com> <d02ac38c-ac8e-fc84-ba65-1c49e9b73bbf@shrew.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 07.02.2021 um 05:00 schrieb Matthew Grooms <mgrooms@shrew.net>: >=20 >>> Am 07.02.2021 um 02:41 schrieb Matthew Grooms <mgrooms@shrew.net>: >>>=20 >>>=20 >>> /etc/exports: >>> /var/rpi4/netboot -ro -alldirs -maproot=3Droot >> why '-ro=E2=80=98 ?? >=20 > It's intended to be read only. That's also what the freebsd diskless = boot handbook article suggests to do ... >=20 > = https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-di= skless I like writing to the system I=E2=80=99ve booted on net0 and have no = problem with that :-) >=20 >=20 >> Am 05.01.2021 um 01:18 schrieb Matthew Grooms <mgrooms@shrew.net>: >>>>=20 >>=20 >> What=E2=80=99s your output of : >>=20 >> root@matthew:~# sockstat -l4 >>=20 >> and >>=20 >> root@matthew:~# cat /etc/fstab >=20 > I don't follow. For the boot server or the RPI4 host? I don't see how = the fstab of the boot server could be relevant. The RPI4 host doesn't = have a local filesystem. It's trying to boot from the nfs export =E2=80=A6= >=20 yes, for the boot server,=20 =E2=80=A6.look the link you=E2=80=99ve posted above : = https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-di= skless please read point/ 10. / Under "32.8.1. Setting Up the PXE = Environment=E2=80=9C. !!! that=E2=80=99s why I asked for =E2=80=99sockstat -l4` ( or `-l6` if you = use ipv6) there=E2=80=99s also a note in the link that `-ro` is only an option to = save machines from humans, if you trust yourself, you can remove the = `-ro` ;-) > Am 07.02.2021 um 05:00 schrieb Matthew Grooms <mgrooms@shrew.net>: >=20 >>>>=20 >> and why did you split the folders under ../netboot/..? >=20 > To serve the raspberry pi 4 what it wants during boot. A more complete = layout under my netboot directory looks like this ... >=20 > /var/rpi4/netboot/firmware > /var/rpi4/netboot/01-dc-a6-32-a8-54-13 -> /var/rpi4/netboot/firmware > /var/rpi4/netboot/freebsd > /var/rpi4/netboot/freebsd/boot/msdos -> /var/rpi4/netboot/firmware well, it would be simpler to=20 mount a bootable(downloaded) rpi.img with mdconfig to your = nfs-export-destination-directory or what I do and what is far more useful : we can `make buildworld buildkernel` directly=20 into the nfs-mount-directory on the boot-server. - my netboot was based on u-boot-tftp from the sd-card which=20 worked very well, and yes: with the right setup =E2=80=9Aloader.efi=E2=80= =98 is detected automatically=20 without copying it to the msdos-partition IIRC.=20 I didn=E2=80=99t try the eeprom-pxe yet but I assume(from what I=E2=80=99= ve read so far) your problem=20 is currently the missing `fstab-mount` . Best Regards Klaus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2D8B4921-CCEB-4203-B616-C0C86612C1E5>