From nobody Tue Jul 02 08:43:29 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 4WCxJq6pRsz5PnnX for ; Tue, 02 Jul 2024 08:43:39 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Received: from nmtao202.oxsus-vadesecure.net (mta-232a.oxsus-vadesecure.net [15.204.3.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WCxJq0JSXz4R9Y for ; Tue, 2 Jul 2024 08:43:38 +0000 (UTC) (envelope-from fred@thegalacticzoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=webcom.xion.oxcs.net header.s=mail1 header.b=MudtevL2; dmarc=pass (policy=quarantine) header.from=thegalacticzoo.com; spf=pass (mx1.freebsd.org: domain of fred@thegalacticzoo.com designates 15.204.3.6 as permitted sender) smtp.mailfrom=fred@thegalacticzoo.com; arc=pass ("oxsus-vadesecure.net:s=arc-202309-rsa2048:i=1") ARC-Seal: i=1; a=rsa-sha256; d=oxsus-vadesecure.net; s=arc-202309-rsa2048; t=1719909813; cv=none; b=Sm8MRSRYv68wtongbNv+6yS5X3/YZ1hBzJ66oMoFcbltVsyZGRClCJ1QTI/BsLQhaddr2eMT9DDTSwrd7aEl/MI1NSS7g1mVfZ7fip3Uz8K7eZQGlaxVbJleGFmLOsP3/J8awZBjWsBbq+6AKnALp9xV3C2bTnUuRUuh1bvH2iQSiN8rBCzgjtHEtNr5moCMBI4AnkoLEmi32n9mtImCoSAY0fVxL3sNww9aEMDH47CGj6ByVPQ1svdfT3oN+ceaosWd2FYNoO/qw2Aq1PB/uCEzvWq2Xzj/tv730kqs58abY7rDSqSZ7Xt1wTKociz44t2XHrmiNs2CEmAIz18fyg== ARC-Message-Signature: i=1; a=rsa-sha256; d=oxsus-vadesecure.net; s=arc-202309-rsa2048; t=1719909813; c=relaxed/relaxed; h=from:reply-to:subject:date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to:references:list-id:list-help:list-unsubscribe:list-unsubscribe-post:list-subscribe:list-post:list-owner:list-archive; bh=Ohu32NWNswqPjyu4Pw4bEomMMIJDpZyZe+CywGSaIWk=; b=ksJOysbCxAX5OYohTO9eV1f+/LLucOLeOYGymicBe8ffQeFXVLIQjuvzGTKMFQc+nlJXu3T3kwpIbcmsypVRjT5kP5d4fY8cMMxIGBpf27BBNb+MnQr/ufWXqb6YJASlbZpWdhb3YgNLJ0KEanQNroiCdv97/gnbeAGUd835NCXTfJSPcCz1U2OmtR/gPJoJqx477ClbeqUOsLmForEvQ9AeCLvGotcLMMEEei6SfRdVAn+zzn+uJKeIlwyW/PROKY49Mh5v8tcYCupEuW4YvhgtAmX2MHATEqrQU6ovQ/4DziSzzfbdtWKmCk5bOz820FUK/fxN3I0tl9z7Hp2E9Q== ARC-Authentication-Results: i=1; DKIM-Signature: v=1; a=rsa-sha256; bh=Ohu32NWNswqPjyu4Pw4bEomMMIJDpZyZe+CywG SaIWk=; c=relaxed/relaxed; d=webcom.xion.oxcs.net; h=from:reply-to: subject:date:to:cc:resent-date:resent-from:resent-to:resent-cc: in-reply-to:references:list-id:list-help:list-unsubscribe: list-unsubscribe-post:list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=mail1; t=1719909813; x=1720514613; b=MudtevL2iwqPql946I2Qb QTtqDN/V1FBvWN3DW0Osbr4VF+FPfcDNpdkIknFxEWCj5Fs71wN6w1UOceqn1oEwJcR8Rl+ tTpmfy85G6fqSAxH98F94gGlL+xGaPj0lEs+VK2v7qxebIY6vXjfQ9Pr+AHRYYAQJ4XtftM dpRWL7dMR/lN8dHW2dsZMPVQe8L0AcI2IMuCcRBbwqaTmYfomu+qSx/cP3emQ+KtMUCynNr ASmnD7txV07e6pSag57VtB640nDzbh/azZKzcJHKg1O73gDcAYFg4wtkz0mx0w9fgAuwAic K/XaTQdTDAqdoe8ljYNs9mFrAF2QZf4TdIScA== Received: from proxy-18.proxy.cloudus.ewr.xion.oxcs.net ([172.56.200.211]) by oxsus2nmtao02p.internal.vadesecure.com with ngmta id 7788af3d-17de58dca76df6b4; Tue, 02 Jul 2024 08:43:33 +0000 From: "Fred L. Finster" Subject: Booting FreeBSD Arm64 from either a NVME disk or a USB SSD, Like Ugreen Case To: freebsd-arm@freebsd.org Cc: "fred@thegalacticzoo.com" Message-ID: <81e180ec-6aef-5e0c-5b0b-3c79b1a820fe@thegalacticzoo.com> Date: Tue, 2 Jul 2024 01:43:29 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 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; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.89 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; ARC_ALLOW(-1.00)[oxsus-vadesecure.net:s=arc-202309-rsa2048:i=1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.987]; DMARC_POLICY_ALLOW(-0.50)[thegalacticzoo.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:15.204.3.4/30]; R_DKIM_ALLOW(-0.20)[webcom.xion.oxcs.net:s=mail1]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:16276, ipnet:15.204.0.0/17, country:FR]; MIME_TRACE(0.00)[0:+]; TO_DN_EQ_ADDR_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[15.204.3.6:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[webcom.xion.oxcs.net:+] X-Rspamd-Queue-Id: 4WCxJq0JSXz4R9Y Hello Arjun and Klaus, So glad to see another Arm64 computer running FreeBSD 14.x in a little bit of time. May I provide some helpful information to your discussion of booting an Arm64 NeoVerse computer? I would like to help create booting FreeBSD kernel image in a disk medium. Others like Klaus have solid knowledge of the details. I have first hand experience from reading, studying, and building a bootable FreeBSD kernel image for the Raspberry Pi 4B Arm64 hardware. Okay, its just a baby computer compared to your 16 CPU CORE Neoverse machine, yet the kernel bootup method is still the same. Klaus your knowledge is helping this process of bringing up a new machine with FreeBSD ARM64 operating system. I recognize your FreeBSD experience is more solid and deeper than what I have learned over the past 6 years using GhostBSD as my daily driver. Now I do have experience running "make buildworld" for the tools and "make buildkernel" for the source code into a bootable file /boot/kernel/kernel I also have experience setting up Poudriere Package builder using Vermadens Poudriere setup web blog wordpress page. I was running Poudirere builder to night on the Raspberry Pi 4B building the RUST 1.78 compiler. There is a third option to use a USB SSD for booting your new ARM64 machine, create a USB SSD drive on a different FreeBSD or GhostBSD computer with either the UFS boot partition and file systems. One can also setup and use the OpenZFS Zettabyte File System. Move the created USB SSD over to the Arm64 machine and Plug in the USB SSD. Easy to modify, fix , or repair the disk structure on a USB SSD. I suppose the same can work with a single USB Flash Drive Stick. Use commands like 'gpart' and 'geom disklist' to verify the setup of the USB SSD disk partitions. Here are a couple FreeBSD commands to look at the drives being attached to the computer. gpart status gpart status /dev/ad0 or gpart status /dev/da0 gpart show -lp gpart show -lp /dev/ad0 or gpart show -lp /dev/da0 camcontrol devlist geom disk list gpart status da1 gpart show -lp da1 Here is my blog with directions for creating partitions on a USB SSD. https://ghostbsd-arm64.blogspot.com/ partition type numbers A501 A%03 A504 freebsd style partition numbers https://ghostbsd-arm64.blogspot.com/2023/11/arm64-boot-usb-flash-drive-hey-buddy.html https://ghostbsd-arm64.blogspot.com/2023/12/partition-type-numbers-for-freebsd-and.html#more https://ghostbsd-arm64.blogspot.com/2023/12/how-to-install-ghostbsd-arm64-into-usb.html Search on word 'SSD' or '500' Arjun, You are welcome to call me Fred Finster 971-718-9144 I will be happy to sign a NDA with human resources to meet with Intel's business procedures and methods. I can meet up with you Tuesday or Wednesday this week in Hillsboro Oregon. I have used Klara Systems article to build a bootable image of FreeBSD kernel for writing into a USB flash drive to boot up FreeBSD on a Raspberry Pi 4B Arm64 single board computer. https://ghostbsd-arm64.blogspot.com/2023/11/creating-ghost14-aarch64-arm64-boot.html https://ghostbsd-arm64.blogspot.com/2023/11/creating-ghost14-aarch64-arm64-boot.html The details are on my blog https://ghostbsd-arm64.blogspot.com https://ghostbsd-arm64.blogspot.com/2023/12/how-to-install-ghostbsd-arm64-into-usb.html https://ghostbsd-arm64.blogspot.com/2023/10/honey-i-broke-my-zfs-usb-sata-ssd-1-tb.html I can definitely help you get FreeBSD Arm64 booting on your Arm64 machine from my experience working with FreeBSD Arm64 over the past 9 months. I am happy to see you successfully boot FreeBSD image on your new Arm64 computer. What do you have for a JTAG and OpenOCD interface to debug booting up this Arm64 system? Jeff Probe from FLIRC is a good tool to use with GNU Debugger GDB or the LLDB debugger that comes with CLANG. I wish you success in making your NVME disk operational soon. If that is not working quite yet. Try a USB SSD device. They are fast and large to hold FreeBSD and compile FreeBSD kernel from sources. Fred Finster 971-718-9144 fredfinster58@gmail.com fred@thegalacticzoo.com Brooks Oregon Happy to help you first hand, Arjun. > From: Anantharam, Arjun > Date: Tue, 02 Jul 2024 00:38:39 UTC > > Unfortunately, PXE boot is still not an option on this platform yet. Will have to rely on FreeBSD iso/img installation from NVMe partition(RAMDisk method) untill we can get PXE to work with UEFI on this platform.. > > Thanks, > Arjun > > ________________________________ > From: owner-freebsd-arm@FreeBSD.org on behalf of Klaus Küchemann > Sent: Friday, June 28, 2024 7:35 AM > To: Andrew Turner ; Warner Losh ; Mark Millard ; freebsd-arm@freebsd.org ; Anantharam, Arjun ; kib@freebsd.org > Subject: Re: FreeBSD OS installation stuck after selecting Boot installer > > > >> Am 28.06.2024 um 12:09 schrieb Andrew Turner : > >> …..What device type is the installer on? e.g. NVMe, USB. I see what look like two NVMe devices on the pci bus, however the nvme driver only attaches to one…. >> >> > > what did I typically do at first in the past when hanging on -things debugging on arm64….. > The following seems to give a very nice option as it seems to indicate that the NIC-driver is working: > >> ………... >>> net devices: >>> net0: >>> net1: >>> net2: >>> net3: >>> > > You can compile fbsd-current into a folder at e.g. on net0 , > setup an PXE-environment(nice description in the handbook) and then : > > OK set currdev=net0 > > OK load boot/kernel/kernel > > OK boot > — > > If the uart problem is based on baudrate(not driver/attachment), there are tools like picocom > where you can change the baudrate on the fly , > That sometimes enlightens the situation.. > > Regards > > K. > -- Fred Finster GhostBSD-Arm64.blogspot.com t.me/ghostbsd Telegram Channel GhostBSD.org GhostBSD website ghostbsdarm64.hopto.org/packages