Date: Sun, 7 Feb 2021 19:24:57 -0600 From: Matthew Grooms <mgrooms@shrew.net> To: =?UTF-8?Q?Klaus_K=c3=bcchemann?= <maciphone2@googlemail.com>, Torfinn Ingolfsen <torfinn.ingolfsen@getmail.no>, Mike Karels <mike@karels.net>, freebsd-arm@freebsd.org Subject: Re: rpi4 network boot Message-ID: <cfd37d1a-3178-3ddf-b06b-ef13cdf15b86@shrew.net> In-Reply-To: <7DB4B9E5-2CA4-4AA3-B3EB-61A4807CFC9E@googlemail.com> 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> <2D8B4921-CCEB-4203-B616-C0C86612C1E5@googlemail.com> <24127be9-ff90-ad97-ada5-2c2175f34fd4@shrew.net> <20210207201956.f289206d5eb560c034fea7a4@getmail.no> <7DB4B9E5-2CA4-4AA3-B3EB-61A4807CFC9E@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/7/2021 2:00 PM, Klaus Küchemann wrote:
> Am 07.02.2021 um 20:19 schrieb Torfinn Ingolfsen
> <torfinn.ingolfsen@getmail.no>:
>> I believe he is asking you to verify that the fstab file for the _client_ (aka the diskless machine your'e trying to boot) is correct. That file exists as
>> ${NFSROOTDIR}/etc/fstab on the boot server.
>>
>> HTH
>> --
>> Torfinn Ingolfsen <torfinn.ingolfsen@getmail.no>
>> _______________________________________________
>> freebsd-arm@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org“
> Yes, the fstab-setup is important…... but then I realized Matthew`s boot environment :
> He has u-boot sitting on the pxe-Server, whereas the eeprom was flashed for completely diskless netboot
> as a requirement .
> With that setup in fact we will end up in n infinite loop of an 'genet0: gen_intr2‘ -console-output,
> regardless of fstab or whatever configuration elsewhere I tried.
Thanks for testing and re-producing that. Corroborating test results
were also posted by others in the FreeBSD forum thread I referenced earlier.
> I have now refreshed the eeprom to it’s default(where diskless pxe-boot is disabled )
> And again successfully net-booted (14_current in this case) :
>
> https://dmesgd.nycbug.org/index.cgi?do=view&id=5917
>
> Since netboot from u-boot on the uSD requiresdonly 1 command by hand (load net0:/boot/kernel/kernel
> )(+ command :’boot’) and there’s no problem with the genet-driver I guess that
> It’s an issue of the pxe-flashed eeprom where we don’t yet know exactly what happens.
I have a slightly different take: The network device appears to work
well initially when used by the eeprom and after the hand-off to u-boot.
The FreeBSD genet driver generally works well unless the device is first
used by eeprom/u-boot. I suspect that u-boot is performing some task
that leaves the device in a state that is incompatible what FreeBSD
expects and/or can work with. Perhaps there is a way to force some a
full device reset of genet either before u-boot hands things off to
FreeBSD or right after FreeBSD loads the genet driver? If so, maybe that
would be worth trying, even as a hacky test, to see if it's the network
device state that's wonky.
> So for now I guess netboot from uSD is a painless and well working setup,
> while to be honest:
> I don’t remember exactly at the moment how I figured to get it to work after trials&errors :-) Ha Ha
> But I’ll leave the uSD untouched or copy the folder to have a point for a tutorial or so if someone is interested in.
Can that be done without human intervention? Perhaps with some sort of
u-boot or EFI script that gets executed? If this method requires the
user to enter a command to boot from the network, it's not an
alternative to PXE.
Thanks,
-Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cfd37d1a-3178-3ddf-b06b-ef13cdf15b86>