From owner-freebsd-current@freebsd.org Fri Jul 27 18:20:29 2018 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 C095E1052BE6 for ; Fri, 27 Jul 2018 18:20:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 528E680DB5 for ; Fri, 27 Jul 2018 18:20:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x231.google.com with SMTP id e14-v6so8832624itf.1 for ; Fri, 27 Jul 2018 11:20:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=n3TFmLq5ZM+yVDyphpERbgpI8QYz3hyjzlAJaSYpU/Q=; b=hCPeQHPXY8EhaPguNGszpRrezq3xABPjm/5y4AqMzCOiW7wxuoJHX4ct7FPlT+Y7o0 LUUYiAN5mPSM2mQGM/DUg8BZnHpMgmBdFiAR6ruRTBkAlbDDXDC/N8OzeLfZXpTrvtRh 8IzUNhavsmfBo1SeY48yawW1J1A+/3fXWaXCgdatPZRS/cYpYLZXgRgykM29mXGd0SKo SBZSq1i6zOEQ8Y4f0CKRs0s/sDchQat/rR9UauQr2HE/S1U2NIFMDT34FU+92U4akfo3 EwUXykKQMxG0mlxqt8Ie6eA4PKtaVBuWigVvVnxlH7J69t8fMISxOjFIv8TFrcGce72U 7F5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=n3TFmLq5ZM+yVDyphpERbgpI8QYz3hyjzlAJaSYpU/Q=; b=jVvrcZbKvTbejldvbjdBtWnPfjpFNpBQxhA6qoHn2WIdTF44dM3IF+qbewZtE2m3Cr XrL57RAzgPCl7vYIO5QVXdd4rH9NyZUdan6JYTZwitVK0fgOrrTngk50hxlM2jFbSWqH ypyCHSfozlJt+uFn2XlbBNR/LmdMzu1g1iYlOGiQXMfNelAm4/MWiiU7BSfubSeJJwyt 0a5v7lDgVHNdjpSsVY08+jAZWi+qQMZddoKumNQVMImCJPY4V6Hv0QLdX4w3jVnUYTrw VfMbb9YAT8EIhR2ZLuEkmBlNAcAgSk5Q2kMUMdXQSTv9TeIL6i5zmayRsTA2vKPyjmrt ezXA== X-Gm-Message-State: AOUpUlHPzzhlXfoQ4R74duWrS3USDGxK4KXgh0VJzwvG7vV2CAWusZwa YLJfx57xKUwsW7kqzyhmVI+fHb6unK2SDM8kUB//WPApyifXaw== X-Google-Smtp-Source: AAOMgpdyZP0cVFK/Xw+/LjPRUqFk4prkxw5RkCeNWjl4qMLCSpPm30oz7GYzjZTnm0Lb4ggHhq1s6xyXPu6TXI17EVE= X-Received: by 2002:a24:b211:: with SMTP id u17-v6mr6317667ite.1.1532715627663; Fri, 27 Jul 2018 11:20:27 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:4485:0:0:0:0:0 with HTTP; Fri, 27 Jul 2018 11:20:26 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <1E6058D2-5804-480B-B6AF-66AA02CDD7AD@me.com> <201807251430.w6PEUWPn041286@pdx.rh.CN85.dnsmgr.net> <20180726155821.6f9906e9@freyja.zeit4.iv.bundesimmobilien.de> <7FA45CAF-6869-4DF6-AA93-5F96F83EF958@me.com> <20180727074558.75b2d730@freyja.zeit4.iv.bundesimmobilien.de> <6C5D21D2-59C6-42DB-AC75-79D98BA5E62B@me.com> <20180727120232.270e1d9f@freyja.zeit4.iv.bundesimmobilien.de> <2A5E5E42-8595-44E9-A51E-504C9C2C7FA7@me.com> <20180727190555.55439fb3@thor.intern.walstatt.dynvpn.de> From: Warner Losh Date: Fri, 27 Jul 2018 12:20:26 -0600 X-Google-Sender-Auth: pSKlm6X-R1XazrmZmZb8gqVzULg Message-ID: Subject: Re: [UEFI] Boot issues on some UEFI implementations To: "O. Hartmann" Cc: Toomas Soome , "Rodney W. Grimes" , freebsd-current , Allan Jude Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 27 Jul 2018 18:20:29 -0000 [[ context trimmed ]] On Fri, Jul 27, 2018 at 12:03 PM, Warner Losh wrote: > > > On Fri, Jul 27, 2018 at 11:05 AM, O. Hartmann > wrote: > >> >> Just to add another success on ASRock Z77-Pro4 (800k ESP, FAT12) and >> ASRock Z77-Pro4M >> (300mb ESP, FAT32). >> >> On this firmware, I did not have to define/copy the bootloader >> within /efi/freebd/BOOTx64.efi. It was sufficient to add an EFI variable >> as described in >> the manpage efibootmgr(8). >> >> The only pitfall on this firmware (very old, last functional update 2013, >> Spectre/Meltodown mitigation only May 2018) was that I wasn't able to >> activate variable >> "0000"! Creating >> >> efibootmgr -c -l /mnt/efi/boot/BOOTx64.efi -L FreeBSD-12 >> >> which results in "Boot0000" >> >> and followed by >> >> efibootmgr -a 0000 >> >> or >> >> efibootmgr -n 0000 >> >> resulted in "No such variable" or similar. >> > > Yes. that's a bogus sanity check in the code. I've removed it and will > commit in a moment. > that should be fixed as of r336768. > I had to perform the very same task again to gain variable 0001 and then I >> was able to >> "activate" variable 0000. This might be due to the fact the only variable >> defined at all >> was Boot0005 pointing to the most recent USB flash device with 12-CURRENT >> from 2018-07-26 >> I just prepared. >> > That part is weird.... > Now, also those boxes boot via UEFI (one, 800k ESP with the /efi/boot >> folder, the other, >> 300mb ESP, with a copy /efi/freebsd as I had to do on the Fujitsu ESPRIMO >> Q956 firmware). > > > OK. > Cool!... Warner