From owner-freebsd-current@freebsd.org Thu Nov 7 08:05:25 2019 Return-Path: Delivered-To: freebsd-current@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 1F2C41ABAEE for ; Thu, 7 Nov 2019 08:05:25 +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 477wtq6rrWz4Gw8 for ; Thu, 7 Nov 2019 08:05:23 +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 xA785JNH038355 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 7 Nov 2019 00:05:25 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 In-Reply-To: <20191107083114.1d9cc7de@ernst.home> From: Chris Reply-To: bsd-lists@BSDforge.com To: freebsd-current Subject: Re: CURRENT October images do not create a bootable install Date: Thu, 07 Nov 2019 00:05:25 -0800 Message-Id: <4ac97a981f9fa6728a552fe1802aeb9e@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 477wtq6rrWz4Gw8 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 [1.70 / 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_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(0.53)[asn: 11404(2.70), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[BSDforge.com]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_LONG(0.63)[0.628,0]; NEURAL_HAM_MEDIUM(-0.36)[-0.363,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2019 08:05:25 -0000 On Thu, 7 Nov 2019 08:31:14 +0100 gljennjohn@gmail=2Ecom said > On Wed, 06 Nov 2019 17:23:08 -0800 > Chris wrote: >=20 > > I put a box together to test 13 about a mos ago=2E > > It's a second gen core i3=2E But whether choosing automatic > > disk layout, or choosing manual=2E When the install finishes, and > > boots to the drive=2E The BIOS reports no bootable media=2E > > I finally gave up, and grabbed the most recent RELENG-12=2E Which > > worked as expected=2E > > While I have no troubles booting (U)EFI=2E Isn't the so-called > > LEGACY boot option still supported? > >=20 > > Thank you for all your time, and consideration=2E > >=20 Thanks for taking the time to respond, Gary=2E >=20 > I installed the latest FreeBSD 13 memstick image (UEFI) yesterday > and had no problem booting it=2E I used manual disk partitioning=2E=20 > In fact, when I added the / partition the installer automatically > created and populated the EFI boot partition for me=2E Same here=2E But in spite of it=2E The reboot proved to be unsuccessful=2E :( >=20 > I used UEFI because that was already set in the BIOS and the > computer doesn't belong to me=2E >=20 > LEGACY mode should still work as long as the BIOS offers that=2E=20 > My main FreeBSD 13 box uses LEGACY booting=2E My BIOS offers both=2E Yet neither option proved fruitful=2E :( >=20 > --=20 > Gary Jennejohn Thanks again, Gary! :)