Date: Wed, 28 Dec 2022 22:42:33 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: rpi3b+ ue0 too late to be configured on boot? Message-ID: <8srop579-r4sq-278-356p-nr7q81n31s4@mnoonqbm.arg>
next in thread | raw e-mail | index | archive | help
Hi, does anyone else have the problem on latest main that the ue0 on an rpi3b+ doesn't show up in time for the rc netif to configure it (or at least it looks like)? While during boot USB seems to need a wait-delay now, which it hadn't in the last years for me? ------------------------------------------------------------------------ ... Feeding entropy: . ELF ldconfig path: /lib /usr/lib ugen1.2: <vendor 0x0424 product 0x9514> at usbus1 uhub1 on uhub0 uhub1: <vendor 0x0424 product 0x9514, class 9/0, rev 2.00/2.00, addr 2> on usbus1 uhub1: MTT enabled lo0: link state changed to UP uhub1: 5 ports with 4 removable, self powered ugen1.3: <vendor 0x0424 product 0xec00> at usbus1 smsc0 on uhub1 smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus1 smsc0: chip 0xec00, rev. 0002 miibus0: <MII bus> on smsc0 smscphy0: <SMC LAN8700 10/100 interface> PHY 1 on miibus0 smscphy0: OUI 0x00800f, model 0x000c, rev. 3 smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ue0: <USB Ethernet> on smsc0 ue0: bpf attached ue0: Ethernet address: xx:xx:xx:xx:xx:xx Starting Network: lo0. lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 ... ------------------------------------------------------------------------ If running manually after boot (again) it all works fine? # sh /etc/rc.d/netif start ue0 smsc0: chip 0xec00, rev. 0002 Starting Network: ue0. ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ... Not that it should matter - this is with https://github.com/pftf/RPi3/releases/tag/v1.38 /bz -- Bjoern A. Zeeb r15:7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8srop579-r4sq-278-356p-nr7q81n31s4>