Date: Sun, 7 Feb 2021 17:02:26 +0100 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Mike Karels <mike@karels.net>, Matthew Grooms <mgrooms@shrew.net>, freebsd-arm@freebsd.org Subject: Re: rpi4 network boot Message-ID: <6C01F20A-7104-440A-ABE4-A9AB789CF51E@googlemail.com> In-Reply-To: <202102071539.117FdTiG086550@mail.karels.net> References: <202102071539.117FdTiG086550@mail.karels.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 07.02.2021 um 16:39 schrieb Mike Karels <mike@karels.net>: >=20 > fwiw, the fdt indicates that the genet has two interrupts, but I have = no > idea what the second one is for. This is the first time I've heard of = it > happening. The interrupt routine for the second interrupt just prints > this message and returns, so we'd know that it was happening at least. >=20 > Mike > _______________________________________________ > 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=E2=80=9C yes, I have now tested the exact or similar same boot-environment as = Matthew: Having u-boot as the payload sitting on the pxe-server instead of = SD-card, As a complete diskless boot by configuring the eeprom as pxe-bootable. It=E2=80=99s an issue in old friend bcm2711-rpi-4-b.dtb : using newer versions of it fail to boot(stopping at net0: cannot set rx. = filters (status=3D3) /) while older versions ends up in the=20 Interrupt-loop(genet0: gen_intr2). I could successfully netboot from SD-card some weeks ago, so this seems = not necessarily=20 an issue with your driver. It only loops when u-boot is placed on the = pxe-server. IIRC any netboot seemed to depend on the right combination of = firmware/msdos-partition=20 and the corresponding fbsd-version . =20 Regards K.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6C01F20A-7104-440A-ABE4-A9AB789CF51E>