From owner-freebsd-current@freebsd.org Tue Jun 4 02:26:04 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B41DE15C5140 for ; Tue, 4 Jun 2019 02:26:04 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CAE738207C; Tue, 4 Jun 2019 02:25:53 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x542Pk6T045843; Mon, 3 Jun 2019 19:25:46 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x542Pjb5045842; Mon, 3 Jun 2019 19:25:45 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201906040225.x542Pjb5045842@gndrsh.dnsmgr.net> Subject: Re: UEFI boot broken in 13? In-Reply-To: <71a0c9f7-0b1f-3757-fc04-4c0d0a1e1085@FreeBSD.org> To: Johannes Lundberg Date: Mon, 3 Jun 2019 19:25:45 -0700 (PDT) CC: FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: CAE738207C X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [4.23 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.90)[0.902,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.40)[0.401,0]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[gndrsh.dnsmgr.net,gndrsh.dnsmgr.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.99)[0.991,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.04)[ip: (0.15), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.05), country: US(-0.06)] 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: Tue, 04 Jun 2019 02:26:04 -0000 > Hi > > I'm using poudriere-image to create usb memstick images. The images are > identical except OS version. They are tested on a laptop with 13-CURRENT > installed as only OS, having UEFI boot and root on zfs. > > 12-STABLE memstick boots fine with in UEFI mode. Does it actually boot via a UEFI, or did UEFI fall back to CSM and do a legacy boot? What does "sysctl machdep.bootmethod" say? machdep.bootmethod: BIOS > > With 13-CURRENT memstick it boots the installed FreeBSD from the SSD > instead (I choose USB UEFI OS in boot menu but it silently boots from > the SSD instead). If I switch to legacy boot, the memstick image boots fine. > > Any ideas? The .iso building was updated to create hybrid boot images some time back, these .iso images should be usable as boot .iso on a cd/dvd and as memstick images. I would encourage there use over the memstick images, as there is a plan to remove them once we get better experience with the hybrid .iso. It is also possible that something has munged the boot in head. Have you tried a downloaed ^/head snapshot from the last week, as it could also be your build system that is not producing a proper boot image? > /Johannes -- Rod Grimes rgrimes@freebsd.org