From owner-freebsd-stable@freebsd.org Wed Nov 6 20:12:33 2019 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3CB2E1BEFC3 for ; Wed, 6 Nov 2019 20:12:33 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 477d4H6N2Zz4ZhR for ; Wed, 6 Nov 2019 20:12:31 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id xA6KBsV0026517 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 6 Nov 2019 12:12:00 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: Chris Ross In-Reply-To: <20191106191711.GK1177@westeros.distal.com> From: Chris Reply-To: bsd-lists@BSDforge.com To: Subject: Re: UEFI ISO boot not working in 12.1 ? Date: Wed, 06 Nov 2019 12:12:00 -0800 Message-Id: <817c7580bb13a15bc8f5312d15306541@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 477d4H6N2Zz4ZhR X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of bsd-lists@BSDforge.com has no SPF policy when checking 24.113.41.81) smtp.mailfrom=bsd-lists@BSDforge.com X-Spamd-Result: default: False [0.74 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[bsd-lists@BSDforge.com]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.94)[-0.937,0]; IP_SCORE(-0.01)[country: US(-0.05)]; TAGGED_RCPT(0.00)[freebsd]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[BSDforge.com]; AUTH_NA(1.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; NEURAL_HAM_LONG(-0.22)[-0.222,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Nov 2019 20:12:33 -0000 On Wed, 6 Nov 2019 14:17:11 -0500 Chris Ross cross+freebsd@distal=2Ecom said > Hi there=2E I tried booting FreeBSD-12=2E1-RELEASE-amd64-disc1=2Eiso on a syst= em > here, which didn't work, and I found that > FreeBSD-12=2E0-RELEASE-amd64-disc1=2Eiso > did work on that same system=2E Another [older] system I had was working w= ith > FreeBSD-12=2E1-RELEASE-amd64-disc1=2Eiso, but after I had reason to change th= at > older system to UEFI boot mode, I found it also would not boot the 12=2E1= =20 > ISO any longer >=20 > A successul UEFI boot of 12=2E0-RELEASE-amd64-disc1 shows many lines of EFI > information to the console, and nearing the bottom: >=20 > BootOrder: 0001 0002 0003 0004[*] > BootInfo Path: > PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1) > BootInfo Path: VenHw(,) > Ignoring Boot0004: No Media Path > Trying ESP: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3= ) > Setting currdev to cd3: > - >=20 > And, that last line is a spinning cursor, after which becomes: >=20 > Loading /boot/defaults/loader=2Econf >=20 > And continues on from there=2E However, the attempt to boot 12=2E1-RELEASE > never loads the loader and allows it to boot=2E The console output > for 12=2E1-RELEASE is below=2E Can anyone help me figure out if it's somethi= ng > I need to do? How has 12=2E1 changed w=2Er=2Et=2E 12=2E0 for UEFI? >=20 > The 12=2E1-RELEASE shows the same as above until starting with "Trying ESP"= : >=20 > Trying ESP: > PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x1) > Setting currdev to cd4: > Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x1) > Setting currdev to cd0: > Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x2) > Setting currdev to cd1: > Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3) > Setting currdev to cd2: > Trying: > PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x3)/CDROM(0x0) > Setting currdev to cd3: > Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x4) > Setting currdev to cd5: > Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x5) > Setting currdev to cd6: > Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x6) > Setting currdev to cd7: > Trying: PciRoot(0x0)/Pci(0x14,0x0)/USB(0x5,0x0)/USB(0x2,0x0)/Unit(0x7) > Setting currdev to cd8: > Failed to bind bootable partition > press any key to interrupt reboot in 5 seconds >=20 > Let me know why 12=2E1-RELEASE is not behaving the same way on my systems=2E=2E= =2E >=20 > Thank you=2E >=20 > - Chris Not trying to hijack this thread, But on a similar note; Wile I'm able to boot/install from them=2E None of the October (12=2E1) install images will produce a bootable install=2E So I'm stuck on RELENG-12=2E This is on a Core 13 second gen=2E IOW my problem is the inverse of yours=2E --Chris