From owner-freebsd-current@freebsd.org Thu Nov 7 08:38:29 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 0F6881AC750 for ; Thu, 7 Nov 2019 08:38:29 +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 477xcz6Lsjz4JZ4 for ; Thu, 7 Nov 2019 08:38:27 +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 xA78cNXT038834 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 7 Nov 2019 00:38:29 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: In-Reply-To: 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:38:29 -0800 Message-Id: <6968bf2dc24e9c5ca0156225024b1581@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 477xcz6Lsjz4JZ4 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.85 / 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.71)[-0.713,0]; IP_SCORE(0.49)[asn: 11404(2.53), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[BSDforge.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.16)[0.155,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]; FREEMAIL_CC(0.00)[me.com]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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:38:29 -0000 On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tsoome@me=2Ecom said > > On 7=2E Nov 2019, at 10:05, Chris wrote: > >=20 > > On Thu, 7 Nov 2019 08:31:14 +0100 gljennjohn@gmail=2Ecom said > >=20 > >> On Wed, 06 Nov 2019 17:23:08 -0800 > >> Chris wrote: > >> > 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? > >> > > Thank you for all your time, and consideration=2E > >> >=20 > >=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 In fa= ct, > > when I added the / partition the installer automatically > >> created and populated the EFI boot partition for me=2E > >=20 > > Same here=2E But in spite of it=2E The reboot proved to be unsuccessful=2E :( > >> I used UEFI because that was already set in the BIOS and the > >> computer doesn't belong to me=2E > >> LEGACY mode should still work as long as the BIOS offers that=2E My main > > FreeBSD 13 box uses LEGACY booting=2E > >=20 > > My BIOS offers both=2E Yet neither option proved fruitful=2E :( > >> --=20 > >> Gary Jennejohn > >=20 > > Thanks again, Gary! :) > >=20 >=20 > Do you have more detailed information? any error messages, screenshots? Thanks for the reply, toomas=2E It's just the standard BIOS report about non-bootable device, please inset bootable medium=2E=2E=2E IOW it doesn't recognize the freshly installed 13-CURRENT on the hard drive as being a bootable OS=2E I'm wondering what happened between RELENG-12, and 13 that made the change? Thanks again! --Chris >=20 > rgds, > toomas