From nobody Mon Jun 07 18:40:16 2021 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 94A4AE59E65 for ; Mon, 7 Jun 2021 18:40:23 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FzMck3hSSz3qTD for ; Mon, 7 Jun 2021 18:40:22 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 157IeGtF011284 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 7 Jun 2021 11:40:17 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 157IeGIM011283; Mon, 7 Jun 2021 11:40:16 -0700 (PDT) (envelope-from fbsd) Date: Mon, 7 Jun 2021 11:40:16 -0700 From: bob prohaska To: marklmi@yahoo.com Cc: freebsd-arm@freebsd.org Subject: Re: Strange u-boot behavior Message-ID: <20210607184016.GA11184@www.zefox.net> References: <20210606043152.GA94545@www.zefox.net> <27786296-8C55-4CEC-A587-14BF4465A4F8@yahoo.com> <20210606160040.GA97697@www.zefox.net> <407FDEDF-8595-4F20-91B9-B475CCE95B39@yahoo.com> 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=us-ascii Content-Disposition: inline In-Reply-To: <407FDEDF-8595-4F20-91B9-B475CCE95B39@yahoo.com> X-Rspamd-Queue-Id: 4FzMck3hSSz3qTD X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-1.10 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.1.20.27:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[50.1.20.27:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm]; MID_RHS_WWW(0.50)[] X-ThisMailContainsUnwantedMimeParts: N On Sun, Jun 06, 2021 at 10:34:26AM -0700, Mark Millard via freebsd-arm wrote: > > > On 2021-Jun-6, at 09:00, bob prohaska wrote: > > > > > It's a dual-boot system, with a complete FreeBSD-current install > > on both USB and microSD storage. > > How do you control which device provides kernel+world > if both have a kernel_world? > If the machine is powered up and not touched, it boots from the microSD card. If boot is interrupted at the u-boot prompt it's (was) possible to issue a usb reset command, at which point the external USB hard drive was discovered. At that point issuing a run bootcmd_usb0 command would boot kernel and mount world from the USB device. > I suggest trying the same vintage that is on 13.0-RELEASE's I've written the 13.0-release image to a microSD card and tried that. It reports a version of U-Boot 2020.10 (Apr 09 2021 - 03:55:54 +0000) Stopped at the u-boot prompt and given the usb reset command, zero storage devices are found. However, usb tree still reports USB device tree: 1 Hub (480 Mb/s, 0mA) | U-Boot Root Hub | +-2 Hub (480 Mb/s, 2mA) | +-3 Vendor specific (12 Mb/s, 90mA) | FTDI FT232R USB UART AM00FGTR | +-4 Vendor specific (480 Mb/s, 2mA) | +-5 Mass Storage (480 Mb/s, 0mA) ASMT ASM105x 12345678D558 The mismatch between what usb reset and usb tree report strikes me as extremely puzzling. As an experiment, I tried booting with no microSD card installed at all. This got confusing; u-boot still came up, apparently from the USB hard drive. The USB disk is still not found by usb scan, but it is recognized by usb tree. As a final test I tried connecting a monitor that had been used with this Pi previously. The monitor's presence made no difference, the display looked normal. A hands-off boot to single user is successful from the microSD card. It's possible to see and access the USB hard drive. At this point I'm beginning to suspect some obscure mischief with the USB-SATA adapter, based only on earlier intermittent problems detecting the USB hard drive. In those cases a few repeats of usb scan found the disk and allowed booting from it. Thanks for following this goose chase! bob prohaska