From nobody Thu Dec 29 19:39:36 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Njdy86pN5z2l3yS for ; Thu, 29 Dec 2022 19:39:44 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail.karels.net (mail.karels.net [216.160.39.52]) by mx1.freebsd.org (Postfix) with ESMTP id 4Njdy84NT6z3M7h for ; Thu, 29 Dec 2022 19:39:44 +0000 (UTC) (envelope-from mike@karels.net) Authentication-Results: mx1.freebsd.org; none Received: from mail.karels.net (localhost [127.0.0.1]) by mail.karels.net (8.16.1/8.16.1) with ESMTP id 2BTJdbIo071983; Thu, 29 Dec 2022 13:39:38 -0600 (CST) (envelope-from mike@karels.net) Received: from [10.0.2.130] ([10.0.1.1]) by mail.karels.net with ESMTPSA id sHgjH/nsrWMtGQEA4+wvSQ (envelope-from ); Thu, 29 Dec 2022 13:39:37 -0600 From: Mike Karels To: "Bjoern A. Zeeb" Cc: freebsd-arm Subject: Re: rpi3b+ ue0 too late to be configured on boot? Date: Thu, 29 Dec 2022 13:39:36 -0600 X-Mailer: MailMate (1.14r5921) Message-ID: <52FD04A5-27B4-4C61-9C97-795D2D65135E@karels.net> In-Reply-To: <8srop579-r4sq-278-356p-nr7q81n31s4@mnoonqbm.arg> References: <8srop579-r4sq-278-356p-nr7q81n31s4@mnoonqbm.arg> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Njdy84NT6z3M7h X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:209, ipnet:216.160.36.0/22, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 28 Dec 2022, at 16:42, Bjoern A. Zeeb wrote: > 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)? I don=E2=80=99t see that problem. I tried the 12/24 snapshot of main on = an RPi3B+, and ue0 configured via DHCP on the initial boot, and on a reboot.= I did have problems with the HDMI console, some of which are new; I will follow up on that separately. Specifically, USB keyboard input didn=E2=80= =99t work to the loader, and I didn=E2=80=99t see console output from user-lev= el startup until I disabled boot_multicons and boot_serial. The second problem is relatively new. Mike > While during boot USB seems to need a wait-delay now, which it hadn't i= n > the last years for me? > > -----------------------------------------------------------------------= - > ... > Feeding entropy: . > ELF ldconfig path: /lib /usr/lib > ugen1.2: at usbus1 > uhub1 on uhub0 > uhub1: = on usbus1 > uhub1: MTT enabled > lo0: link state changed to UP > uhub1: 5 ports with 4 removable, self powered > ugen1.3: at usbus1 > smsc0 on uhub1 > smsc0: on usbus1 > smsc0: chip 0xec00, rev. 0002 > miibus0: on smsc0 > smscphy0: PHY 1 on miibus0 > smscphy0: OUI 0x00800f, model 0x000c, rev. 3 > smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ue0: on smsc0 > ue0: bpf attached > ue0: Ethernet address: xx:xx:xx:xx:xx:xx > Starting Network: lo0. > lo0: flags=3D8049 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=3D8843 metric 0 mtu = 1500 > ... > > > > Not that it should matter - this is with https://github.com/pftf/RPi3/r= eleases/tag/v1.38 > > /bz > > -- = > Bjoern A. Zeeb r15:= 7