From nobody Sat Jan 13 16:24:13 2024 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 4TC3d861Gkz5669y; Sat, 13 Jan 2024 16:24:12 +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 4TC3d76gXKz4Zxx; Sat, 13 Jan 2024 16:24:11 +0000 (UTC) (envelope-from fbsd@www.zefox.net) 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 Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 40DGOE0h021021 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 13 Jan 2024 08:24:14 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 40DGOEL8021020; Sat, 13 Jan 2024 08:24:14 -0800 (PST) (envelope-from fbsd) Date: Sat, 13 Jan 2024 08:24:13 -0800 From: bob prohaska To: freebsd-current@freebsd.org Cc: freebsd-arm@freebsd.org Subject: Re: bsdinstall use on rpi4 Message-ID: References: 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: X-Spamd-Bar: - X-Spamd-Result: default: False [-1.10 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_WWW(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org,freebsd-arm@freebsd.org]; DMARC_NA(0.00)[zefox.net]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; R_SPF_NA(0.00)[no SPF record] X-Rspamd-Queue-Id: 4TC3d76gXKz4Zxx On Sat, Jan 13, 2024 at 03:26:19PM +0000, void wrote: > Hi, > > I'm trying to use bsdinstall on > FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240111-a61d2c7fbd3c-267507.img > to install to usb3-connected HD, using the 'expert mode' for UFS, > after having initially booted from mmcsd. > > The goal is to boot to usb3 with freebsd on UFS filesystem, and to have > that filesystem split into partitions, and the partitions having various > properties. IOW not to have it all on /. I'd like to use GPT instead of MBR. > > Is this (bsdinstall) method 'correct' or should I use some other method? > > I've tried this method but get errors after the fetching phase. > > 1. "manifest not found on local disk and will be fetched from an > unverified source..." http://void.f-m.fm.user.fm/error1.png > > 2. "error while extracting base.txz: can't create > /usr/share/untrusted/Sonera_Class_2_Root_CA.pem" > http://void.f-m.fm.user.fm/error2.png > > 3. "could not set root password. An installation step has been > aborted. Would you like to restart the installation or exit the > installer?" > http://void.f-m.fm.user.fm/error3.png > I tried this using 14-release on a Pi3 with a usb mechanical hard disk. I don't recall seeing the errors reported above, but found that the msdos partition wasn't populated. I copied files manually. The resulting host is finicky about booting, sometimes requiring intervention at the serial console to prod u-boot to find the usb disk. This particular Pi is booting without a microSD, it's possible the usb-sata adapter contributes to the problem. It might be worth trying the "bootcode.bin-only" method to see if that helps. Perhaps others can say more. Once FreeBSD is up there have been no obvious problems. Thanks for reading, hth bob prohaska