Date: Thu, 7 Jan 2021 04:43:02 +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: <082BC0B9-2538-43D5-9D5E-C18B4DEE9ECB@googlemail.com> In-Reply-To: <e324f942-43ac-d2ab-3e7f-47ca91e40bee@shrew.net> References: <d385f2b3-87e0-1bd5-d0f8-76ba1eb99816@shrew.net> <3a1acba5-8662-55cb-c5c4-98ec7873f78f@shrew.net> <e324f942-43ac-d2ab-3e7f-47ca91e40bee@shrew.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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=3Dview&id=3D5864 Also it doesn=E2=80=99t seem to be a firmware problem . It=E2=80=99s 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=20 I don=E2=80=99t 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... Best Regards Klaus =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?082BC0B9-2538-43D5-9D5E-C18B4DEE9ECB>