Date: Sat, 6 Feb 2021 14:27:10 -0600 From: Matthew Grooms <mgrooms@shrew.net> To: =?UTF-8?Q?Klaus_K=c3=bcchemann?= <maciphone2@googlemail.com>, freebsd-arm@freebsd.org Subject: Re: rpi4 network boot Message-ID: <de86ca7c-dd8a-511a-6063-ada6eb451488@shrew.net> In-Reply-To: <082BC0B9-2538-43D5-9D5E-C18B4DEE9ECB@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/6/2021 9:43 PM, Klaus Küchemann wrote: > At the moment I can say that there is NO problem with the genet-driver related to netboot : > > see my successful netboot incl. fully working genet : > > https://dmesgd.nycbug.org/index.cgi?do=view&id=5864 > > Also it doesn’t seem to be a firmware problem . > It’s more a configuration-thing. > So: I also experienced the hang on genet between my first netboot-trials , > But after changing some configurations that problem went away. > > Since this was a quite complex and fiddly setup on both server and uSD-client > I don’t remember at the moment which conf-setting exactly it was that solved it :-) > > for further help we would need your configs: fstab, ifconfig and so on... Hi Klaus, Sorry for the late reply. Does your example qualify as a network boot? From your console output, it looks like you loaded bootaa64.efi from mmc and there was human interaction with the efi boot console at least once. I need to netboot without the help of local storage or human intervention. I'll gather more info from my setup and post back to this thread. Thanks, -Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?de86ca7c-dd8a-511a-6063-ada6eb451488>