From nobody Sat Mar 16 05:45:51 2024 X-Original-To: freebsd-stable@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 4TxVTq62K7z5Dp80 for ; Sat, 16 Mar 2024 05:46:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TxVTp3NJTz49FL for ; Sat, 16 Mar 2024 05:46:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-x133.google.com with SMTP id 2adb3069b0e04-513ccc70a6dso4725526e87.1 for ; Fri, 15 Mar 2024 22:46:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1710567962; x=1711172762; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=f2wNgQ2e2iEWXu1M/nzBz6v9x6KGBoQYNj318iqs9U8=; b=ZBfc0pDK529ca2lDFNmjtuOkkuPlXvgn25HzX4UotFv8esN+QVdAfr82/F7KDid6v8 vpd7lbe6icoi0MOXsmVsEzGlSAf6MJMgrl0bWowojqY6JWGZws8WNkr/ITxKeuz0m5sY 5ZKyd1c7ZpoqVp07A7H3qBnf83OOvHx46D0c9nsr0xk+LFd3T7oFKe6xJLyG4H0TfiMn C6Iif5bfWVIXuZ8l2Ikzv/VHa5UMwM4k0IhT7yMl4cwu2wXERXFrsE9mvL3GhMjQmGrn VqCOtxoOD3rpPVoH9k87CwKcIgLad6XKUPoeUWbBXRCBgkWVsZmW8MOWA9YUQju/jDcH s8MQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710567962; x=1711172762; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=f2wNgQ2e2iEWXu1M/nzBz6v9x6KGBoQYNj318iqs9U8=; b=nKij2KKTCZ1LbJHykdFrr+8DMCcN37tQ04L5XquQEngJQ2U6QT+ENGXHtapwKO4Uv2 wFC/0hDmYK83eRejfpWY68olVU7m5lwnfoV1YSkpHXRxJOR/YLcfCi5aXLhC+QEjlxhs G0AG6AC1xLp+F4T83tY8IWk9mbw0euj2A9F9epq/3GG9MQoM2z6HHUHF9+JTmorJake7 9Udchx95YV4/dzEj1U+sECQEhAFlstwpFaujGcsiw050DsdZZuMGJ5ZfUeu95IX11UgK i53vGa7Y+eN/Hy6OgumP5wD/1Y8/62zo7U8GmO/XTPS4yhlQnsEqBX3pOqI3SpJNKj2E +WVw== X-Gm-Message-State: AOJu0YwdESxtH+5jNcom1u+N0ygaW6DdF66M1S+818BDH4W+O8aIkw0j bsfYQKJvaeU0p9NGkVVqKTXEKlAIphJhSvmg2TcruJoHTWii0NlgIiISqdPMEzb0/2RuKaYv1eF PXPL+Cst3Pu804c0+qsyVRlJo47BqZ1nCi/HWrmr7rpkteRYycC4= X-Google-Smtp-Source: AGHT+IGkccot8g0VURb3UfKraMNryZRGu0yppde138Z6qPuZXLSPrhcVFIdRNvHET3M0kcdnbl7euWO9gqC4NOyBmI0= X-Received: by 2002:ac2:4acc:0:b0:513:a7e1:73ff with SMTP id m12-20020ac24acc000000b00513a7e173ffmr630717lfp.66.1710567962370; Fri, 15 Mar 2024 22:46:02 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Fri, 15 Mar 2024 23:45:51 -0600 Message-ID: Subject: Re: Where to get clue about UEFI and zfs boot clue? To: George Michaelson Cc: FreeBSD Stable Content-Type: multipart/alternative; boundary="000000000000c30d860613c0a313" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4TxVTp3NJTz49FL --000000000000c30d860613c0a313 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Mar 15, 2024, 10:21=E2=80=AFPM George Michaelson = wrote: > how "generic" is the initial boot selector? If I have one already > which points to debian on the same MMC, is there any point installing > the FreeBSD one? the generic one I have chain loads what looks like > grub. I want to minimise damage to the MMC and so don't want to > destroy this state if I can, but in the final analysis I can, if the > best path is to recreate an EFI partition of known quality. > > the one I have (zimablade) is able to boot the SSD with a FreeBSD > install if I break to F11 so there obviously is a bootable media > reference visible at EFI time but I cannot work out how to make it the > autoboot target. That in itself might be the reason to install the > FreeBSD one. Do I e.g. have to put something into the MMC backed EFI > msdos partition, and boot to that? Is that a loader, or a kernel? How > does it find the (ZFS) FreeBSD partition I want to be the live boot? > (ie is the FreeBSD /boot partition going to have to live on the MMC > itself) > > thats about it for now. FreeBSD on the zimablade (quad core, 16GB > DDR3L, fanless, small box with a PCIx2 breakout connector and 2xSATA > on the main board) works fine. I'm booting into TrueNAS core so its > FreeBSD 13.1 and working fine. Every mainboard device seems to be > recognized and the 4 port SATA card I am running on the PCI connector > works fine. zimablade wants you to run some debian hosted suite, I > prefer to be in BSD. That said, it does have VMs and docker. > When you boot FreeBSD, what does efibootmgr -v say? Warner -G > > > On Sat, Mar 16, 2024 at 1:59=E2=80=AFPM Warner Losh wrot= e: > > > > > > > > On Fri, Mar 15, 2024, 3:47=E2=80=AFPM George Michaelson > wrote: > >> > >> I feel in a bit of a corner case window regarding UEFI boot > configuration, multiple disks, and zfs. Ignorance is not bliss. > >> > >> Probably it's UEFI clue more than FreeBSD clue I lack, but the target > OS is a zfs backed FreeBSD. > >> > >> Which ML is the best place to ask? Here? > > > > > > Here. What's your question? > > > > Warner > > > >> G > --000000000000c30d860613c0a313 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Mar 15, 2024, 10:21=E2=80=AFPM George Michaels= on <ggm@algebras.org> wrote:<= br>
how "generic" is the init= ial boot selector? If I have one already
which points to debian on the same MMC, is there any point installing
the FreeBSD one? the generic one I have chain loads what looks like
grub. I want to minimise damage to the MMC and so don't want to
destroy this state if I can, but in the final analysis I can, if the
best path is to recreate an EFI partition of known quality.

the one I have (zimablade) is able to boot the SSD with a FreeBSD
install if I break to F11 so there obviously is a bootable media
reference visible at EFI time but I cannot work out how to make it the
autoboot target. That in itself might be the reason to install the
FreeBSD one.=C2=A0 Do I e.g. have to put something into the MMC backed EFI<= br> msdos partition, and boot to that? Is that a loader, or a kernel? How
does it find the (ZFS) FreeBSD partition I want to be the live boot?
(ie is the FreeBSD /boot partition going to have to live on the MMC
itself)

thats about it for now. FreeBSD on the zimablade (quad core, 16GB
DDR3L, fanless, small box with a PCIx2 breakout connector and 2xSATA
on the main board) works fine. I'm booting into TrueNAS core so its
FreeBSD 13.1 and working fine. Every mainboard device seems to be
recognized and the 4 port SATA card I am running on the PCI connector
works fine. zimablade wants you to run some debian hosted suite, I
prefer to be in BSD. That said, it does have VMs and docker.


When you boot FreeBSD,=C2=A0 what does efibootmgr -v say?

Warner

-G


On Sat, Mar 16, 2024 at 1:59=E2=80=AFPM Warner Losh <imp@bsdimp.com> = wrote:
>
>
>
> On Fri, Mar 15, 2024, 3:47=E2=80=AFPM George Michaelson <ggm@algebras= .org> wrote:
>>
>> I feel in a bit of a corner case window regarding UEFI boot config= uration, multiple disks, and zfs. Ignorance is not bliss.
>>
>> Probably it's UEFI clue more than FreeBSD clue I lack, but the= target OS is a zfs backed FreeBSD.
>>
>> Which ML is the best place to ask? Here?
>
>
> Here. What's your question?
>
> Warner
>
>> G
--000000000000c30d860613c0a313--