From nobody Tue Feb 08 11:33:50 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 D85C219A60D0 for ; Tue, 8 Feb 2022 11:34:01 +0000 (UTC) (envelope-from wb7odyfred@yahoo.com) Received: from sonic304-9.consmr.mail.bf2.yahoo.com (sonic304-9.consmr.mail.bf2.yahoo.com [74.6.128.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4JtLWD731Rz3j6f for ; Tue, 8 Feb 2022 11:34:00 +0000 (UTC) (envelope-from wb7odyfred@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1644320034; bh=yySC1lsf2Z6Zf4a8P5umXGg5Vu5HlAygdsfeT1On414=; h=Date:From:To:Subject:Cc:References:From:Subject:Reply-To; b=D9LsIjuNOFMNsQRM30MOUgC9sQUnqO/pPW2E92IU88SENn/vtWcEDnQpfB88t+GhOFe0+Mw7Vp94kyHREWBeRJay+JIDUDpafwyuE4hhKg6tKIaJ1+f3lNrY51kKvN4t3N9/p6rwyHmQUHvMohe/26LIMtmXWLVyE34TkTlOSudrEIwkOjjw3Bb6SFP6C80/AeejLj34ghhSaylzeoO1PEMP+SrpV81tuPXwgYlH5q+SNPw65RfWRH/7e8Ge3EP2/Eym1/hBOxAvlwILWqUeXOyCOqzkmuK2ss8pyLRov5FDzHSv6hmX4BRRQc8OgJ14T6f7vEFU3QDbcWoVEqh6dA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1644320034; bh=mskJUb/IxqXWJqpgP2dPHb1xyGNFZj4dzzOZhrvC2ku=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=SLIRJcwzeUoNr1hlWDG4OqPoRT6ibgkzn46W45Wwyvante6mDuFFL/jwcJGQS3BQTMBfn/gan8pFSzgzJpC0RjAzg0trbX35q/rgAmPApqHrm8G9ZntDBvdr3D7yTDUBdKQNKptSd/tzzNq8k+xjYJ7wVVpDV0Ye/BByKLAoaScS3SGkKCeD/s66KzezFgooBxUXoCkh2ZN498mGqb0axOBbAbh9WBiz+XyWYyFQGjA9D4oQYCbNtgR6rBQqJJcQfd+zXTXLOBWhfvNfGBCO0938072Iwgsni4vqH5dcMbDelNLQc5Nf3Qa8Mx4DxJS5TaS0bkKbXFDqCNlkmpPPsw== X-YMail-OSG: M2DDV7oVM1ldiFLEzytKv48K9iFIBDzdHE7w6OjMrWKd0V5EjmF_0W5XjMetN9k gXjwCk5.WKruFCOWGPQ2ByI6ITaZZziWtpqjLlQmYxuLbRPeGKiVQurAoVtxMjNfvYOBw.OTolK8 c7fATYtvJtfUdsBtVPuuox6X4PLmr2T_UgXSVBLLyeT3kNx.R74vlJxtG0Huod3TP1VtFA2_S96g F69utuyX9X7aH9ppQm7OIET3WpJ4ND9UGVt7QNAnHTDKjqCFujHJWOiMLa3sbs47uI3Z3r4cFjuU gDwgH7EjNuufOufTlgl2g2l2HJrrIDU2pRoRXmLGXf9QV3KYOYkH8DtJUUYGWRF8tnNxKsR7IjTE lyi.BkP9uJsGiijWbbQyty3vs9s5pDuLFvQ_5alN0mPgcvqcDjyLsORHMgNAqE7B6ky6isCWcKHG 5Dby_tfPwvmdLzdstlo61idv93AiTTm0LGSLJ9gvnGn4ArGRQ1xssub.xI.JYdklcO.Wg5ACQH1J vqbsEVZYONmddc7pB0YqwKFFfhpBMPyLBvCbyc6BK2N14vTSzvcyWPpC1KjZMLJO80K5a.Qahpd. MuDzdCzogL1l.UXBlOLz4uUz7GzAG7MLXjmyDuUZFpgVmVchKste6p027_A1eUiADOMkM9d.dlLv DpjlVlFOd7wXyw0gByUGIqsnRfTcp_etlPuseA2fmLw70e.FGVSP6Yq3FfEONnkANuN9SnTZ12lX zzFfad5mhIO_KFlqVZ6nZhCIZZbs98WB7uP.f7ThQjnJ0oauNIeQPQp2rNAxWygwRGtyGm70Ss6f JC35G0Q90Ny_8CsoTY9m2uXkS665cMvqgmgwOaF1oDyHMuJECfgjU_7ErhCQX6GkKX8Sg90RvmKX dFuOFn.I.1RMazExtn9uiXlFQ6gjDgar_QNZMeffwqgUvxsbPztFUnazURgznvDS_YGftd04zEAg R.u7vcR6hFmnj2ji7Zw6jiMXoYlvBVfRPOIaiBHEepd8x2NQCk12tEK1T5Uob.NnFKDXT2RiNkKz JxVE1USESlOOt1mLaLpAPKNJSvgqmbt5ld3STwkU3GEOJ8XU14IYiJM2uNggXcTfTQsv.qC2k96G j.jEcOWQzE_7W1dVR5DWnQ1YouSBUU_2DGlZD_5WtXztC9Gnaz_2AuuLod.C74ie2gGvKawW8IGL MMuSXK7kxbBwqSqTMf77K.JMF15Ujeq.2I0O31lhrtmcxdMQ7WOuBUqv5ddihbaSFzTGpVvF83OJ yLddOZ_TdCXEMs68igUaWKb.J0Jc1wJCzfxY5KSUlBIIyfCCwfvFPpSXfA0qYp1KnKMwkf7SAydW aGcNfOF2q_.5kthYDNpwN5qO00DjnDiJzjFwyPrvoJ9lzPL10DPv5JE2hHBbIMw33GJqnDwoQPI5 2ylqI1xhCnV6wmczshp.du2IND1KZgw7hNbiCuHYDdeVvsTlXDzPCsDLlCCQ.7fbnkeRic.4Ci0L sPd9Ez3J3ZNqLE9lVz.ITOa5NUV3Cn3xHt4gaZe1PLGaaxsG82IHSi4xg.QYWkbj_dGz2ajdMhU8 FXlpi5sl5oG3R3j_LTg6s0Xeo_ncNp6BO5XQRsqeRlFpkIXHi.W6s0OnDyKKzS9zPsdFpqK7zUQL KkU2Zkc8wSW3mTpIZjKz7xCkhW.aHF5U4r5AJCz93K_UMHzJ64uGg_jFVU_oq8JE_KViNFz4LbBI huMYwwN7AdLEXnFX7YYvnnqunSHFhSOAKNHCDPnJfEB9Cg9fOVwYwBLz5BIR2FJpRSL_vKRNGe7v jteMCcnngjAmXumeAE_q9PD_q2E5raOKSRt.o.vetmcqpYm3fNjZNsMOxfb9DQdjhH3AFuXdEaC2 yPlzO2UfOTCDNqCPRDEV.taw4PoAb_aiY.cxpt14eiEQ_uOzF_yCED3c.E2Fie0fOcDxiqNKHn2p UwxcHszu3bXxC.xELChKnhjdVcOKsW.lOutm8.wmmDgPO72o_f4.C9Z1_5i6PVXY6DVOqBrCQwbY P48eCVj_JHATamu5o7.bRRfXbbafnQC8ICQ3641Bj1cU7qKT8IzpnDcxuz7UtexOjh2w6vXFOHof DdMg.uZwtaI3b2y2wOx7gT2b3GJU5LVeumbMErJ1_NUegofLjVnK78vtB3N7ZcVVXcByKn2W0yLb aSne_9KcESL4tWPV4XawCe_PogdLBFa.16Awq0YRRIn0ZFOXwIl8LYeoJUApL6BYSTzKuEVjXpJx F5h3qgZepFNI_27SAtGFCdVRS6JvB.uO7RPEyD1xcoLkC7R3sHTJpOegtq8ozJYo3hhz2ETc- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.bf2.yahoo.com with HTTP; Tue, 8 Feb 2022 11:33:54 +0000 Received: by kubenode539.mail-prod1.omega.gq1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID 138e249b9a94d24b12e40c6f28cb1c28; Tue, 08 Feb 2022 11:33:52 +0000 (UTC) Content-Type: multipart/alternative; boundary="------------8CJO0Pe5ymtCU0v0PyR8HtR5" Message-ID: <17693697-ba5d-7b09-4bcb-c7e5e43a6f01@yahoo.com> Date: Tue, 8 Feb 2022 03:33:50 -0800 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Content-Language: en-US From: Fred Finster Organization: Kliktel To: freebsd-arm@freebsd.org Subject: SSD 500GB, has several slices, FreeBSD-ARM64 Snapshot 14, installed to a slice. Cc: fbsd@www.zefox.net, Fred.Suyimazu@theGalacticZoo.com References: <17693697-ba5d-7b09-4bcb-c7e5e43a6f01.ref@yahoo.com> X-Mailer: WebService/1.1.19711 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.yahoo X-Rspamd-Queue-Id: 4JtLWD731Rz3j6f X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=D9LsIjuN; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of wb7odyfred@yahoo.com designates 74.6.128.32 as permitted sender) smtp.mailfrom=wb7odyfred@yahoo.com X-Spamd-Result: default: False [-3.00 / 15.00]; FREEMAIL_FROM(0.00)[yahoo.com]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; TO_DN_NONE(0.00)[]; URI_COUNT_ODD(1.00)[5]; HAS_ORG_HEADER(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:26101, ipnet:74.6.128.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[74.6.128.32:from]; MLMMJ_DEST(0.00)[freebsd-arm]; RWL_MAILSPIKE_POSSIBLE(0.00)[74.6.128.32:from]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------8CJO0Pe5ymtCU0v0PyR8HtR5 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit I will post details and pictures to https://ghostbsd-arm64.blogpost.com to better explain my confusion I want to thank  Bob Prohaska for his little notes on setting up Raspberry Pi 4B at http://www.zefox.net/~fbsd/u-boot_cheatsheet for booting from a USB SSD disk. http://www.zefox.net/~fbsd/ Check his other notes on booting Raspberry Pi 3+ and 4B SBCs. I am searching and looking for using EFIBOOTMGR to setup the SSD to boot from a slice.  There is an error about NO BootOrder setup and missing ubootefi.var value. So I can boot from a USB 2.0 Flash drive with the FreeBSD 14.0 RPI3 snapshot installed.  I did  install same image to a slice on the 500GB SATA SSD , but did not make any other changes or settings.  Still looking for the Instructions, Dance Steps, what ever it takes to make the SSD boot for a self contained system. I document here the steps, so others can follow. Install FreeBSD 14.0 Snapshot RPI3 to USB Flash Drive: download from freebsd.org/where https://download.freebsd.org/snapshots/arm64/aarch64/ISO-IMAGES/14.0/FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20220127-2c449a4c5a3-252673.img.xz 2022 01 27 date snapshot Note:  unxz FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20220127-2c449a4c5a3-252673.img.xz dd if=./FreeBSD-ARM64-RPI3.img of=/dev/da1  bs=1m conv=notrunc status=progress Install FreeBSD 14.0 Snapshot RPI3 to USB 3.0 500GB SSD in an external HornetTek metal case Drive enclosure: dd if=./FreeBSD-ARM64-RPI3.img of=/dev/da1p4  bs=1m conv=notrunc status=progress Look at the location difference between  a single USB Flash drive stick  /dev/da1   and the SDD /dev/da1p4  into a slice (linux primary partition ) versus if  I used /dev/da1 for the whole disk.  So does the U-Boot have logic to do both to boot from a SSD (1.) boot whole drive and then 2.0 boot a single Slice that has 2 partitions 1.) MSDOS FAT32 2.) BSD with a label. ) So I am missing  efibootmrg on  aarch64 FreeBSD 14.0 snapshot to set the "boot order".  Missing ubootefi.var  variables? So  look at more details here at https://ghostbsd-arm64.blogspot.com {not like a web page with text files, yet I can display pictures I took with a camera here }.AR  I have not made the post "Booting 500 GB SSD on FreeBSD-ARM64-14.0 January 27, 2022  snapshot". yet. Simply,  I am asking:  1.)  Can U-BOOT and UEFI handle booting from an image installed to a  slice or does it have to be an image installed to a full disk?  How do you point the UEFI loader to select this one slice? Which tools accomplish that?  Are those tools already loaded inside the snapshot image downloaded from FreeBSD.org/where ??  I don't have ethernet access here and the internal wifi device does not have a working device driver for the Broadcom wifi.  2.)  Is there a method, to boot Rod Smiths rEFInd aaarch64 boot manager to allow FreeBSD 14 ARM64, POP!_OS ARM64, Manjaro Linux ARM64, Raspup 8.2.1 (ARM32) from the same disk?   Is there a UEFI work around using EFIBOOTMGR, EFI commands: printenv , setenv, run bootcmd  ?? URLS to read are good resource, that I would read. pss. Hard when you are starting out, to now what commands to issue in which sequence for the desired effect, unless you follow a pattern worked out by someone else. If I run eifbootmgr on my FreeBSD developer machine with the SSD plugged in. It sees the other devices and proceeds to setup the boot order for the development machine, not the SSD disk that has be plugged in termporarily. The answer is something simple, that I have not read about using before. Or so obvious a child could do it. -- Fred Finster email:Fred.Suyimazu@theGalacticZoo.com 971-718-9144 ghostbsd-arm64.blogspot.com --------------8CJO0Pe5ymtCU0v0PyR8HtR5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

I will post details and pictures to  https://ghostbsd-arm64.blogpost.com to better explain my confusion

I want to thank  Bob Prohaska for his little notes on setting up Raspberry Pi 4B at http://www.zefox.net/~fbsd/u-boot_cheatsheet for booting from a USB SSD disk.  http://www.zefox.net/~fbsd/  Check his other notes on booting Raspberry Pi 3+ and 4B SBCs.

I am searching and looking for using EFIBOOTMGR to setup the SSD to boot from a slice.  There is an error about NO BootOrder setup and missing ubootefi.var value.

So I can boot from a USB 2.0 Flash drive with the FreeBSD 14.0 RPI3 snapshot installed.  I did  install same image to a slice on the 500GB SATA SSD , but did not make any other changes or settings.  Still looking for the Instructions, Dance Steps, what ever it takes to make the SSD boot for a self contained system.

I document here the steps, so others can follow. 

Install FreeBSD 14.0 Snapshot RPI3 to USB Flash Drive:

download from  freebsd.org/where   https://download.freebsd.org/snapshots/arm64/aarch64/ISO-IMAGES/14.0/FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20220127-2c449a4c5a3-252673.img.xz  2022 01 27 date snapshot  

Note:  unxz  FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20220127-2c449a4c5a3-252673.img.xz

dd if=./FreeBSD-ARM64-RPI3.img of=/dev/da1  bs=1m conv=notrunc  status=progress

Install FreeBSD 14.0 Snapshot RPI3 to USB 3.0 500GB SSD in an external HornetTek metal case Drive enclosure:

dd if=./FreeBSD-ARM64-RPI3.img of=/dev/da1p4  bs=1m conv=notrunc  status=progress

Look at the location difference between  a single USB Flash drive stick  /dev/da1   and the SDD /dev/da1p4  into a slice (linux primary partition ) versus if  I used /dev/da1 for the whole disk.  So does the U-Boot have logic to do both to boot from a SSD (1.) boot whole drive and then 2.0 boot a single Slice that has 2 partitions 1.) MSDOS FAT32 2.) BSD with a label. )

So I am missing  efibootmrg on  aarch64 FreeBSD 14.0 snapshot to set the "boot order".  Missing ubootefi.var  variables?

So  look at more details here at https://ghostbsd-arm64.blogspot.com {not like a web page with text files, yet I can display pictures I took with a camera here }.AR  I have not made the post "Booting 500 GB SSD on FreeBSD-ARM64-14.0 January 27, 2022  snapshot".  yet.

Simply,  I am asking:

 1.)  Can U-BOOT and UEFI handle booting from an image installed to a  slice or does it have to be an image installed to a full disk?  How do you point the UEFI loader to select this one slice?  Which tools accomplish that?  Are those tools already loaded inside the snapshot image downloaded from FreeBSD.org/where ??  I don't have ethernet access here and the internal wifi device does not have a working device driver for the Broadcom wifi.

 2.)  Is there a method, to boot Rod Smiths rEFInd aaarch64 boot manager to allow FreeBSD 14 ARM64, POP!_OS ARM64, Manjaro Linux ARM64, Raspup 8.2.1 (ARM32) from the same disk?   Is there a UEFI work around using EFIBOOTMGR, EFI commands: printenv , setenv, run bootcmd  ??

URLS to read are good resource, that I would read.

pss.  Hard when you are starting out, to now what commands to issue in which sequence for the desired effect, unless you follow a pattern worked out by someone else.  
If I run eifbootmgr on my FreeBSD developer machine with the SSD plugged in.  It sees the other devices and proceeds to setup the boot order for the development machine, 
not the SSD disk that has be plugged in termporarily.   The answer is something simple, that I have not read about using before.  Or so obvious a child could do it.

-- 
Fred Finster 
email:  Fred.Suyimazu@theGalacticZoo.com
971-718-9144
ghostbsd-arm64.blogspot.com
--------------8CJO0Pe5ymtCU0v0PyR8HtR5--