From owner-freebsd-stable@freebsd.org Sun Jun 28 03:24:08 2020 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 13D9533DD9D for ; Sun, 28 Jun 2020 03:24:08 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (gate.utahime.jp [183.180.29.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49vbZG0Jvbz3Ynd for ; Sun, 28 Jun 2020 03:24:05 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by gate.utahime.jp (Postfix) with ESMTPS id 568F79D7E for ; Sun, 28 Jun 2020 12:24:02 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=utahime.org; s=maybe2019112701; t=1593314642; bh=c8X704HIlGXSdS7E5sdCKz3cyJz5N/BRjPwz5mS71bc=; h=Date:To:Subject:From:In-Reply-To:References; b=lBqysAeiZ+5DZ3xQWQD6QCPksaFxgwg/OlgZJzrjl+WCT0Quu+MjD+CvOzP+Ybdsr uYtrIeNrg1GuX5xIIFcXErpI4v1Dhwsj8EaigBOhs5V6nItBD3b6WJKKSieTdB65nG 8eOC+vUCdWfL29nwKkj5NmN6vAuXc2hoIhG3WIhZW18GyIcWKLcbxleHHXwcyEqPDs n9VTHqOFIblu2SgoHSM5LG8D1tB8WMp+X+lWttTQuRSWzgbInRM2P5NsS6zk1kxqhm ZOcEMRupv5RPbccANuN4oLV0SLPIFZFTvPcZW7hixQ8nNSUKgO0LvpmY3arfO+49Xs /4d0AzPPx1SOg== Received: from localhost (rolling.home.utahime.org [192.168.174.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 492225B4B1; Sun, 28 Jun 2020 12:24:00 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.3 at eastasia.home.utahime.org Date: Sun, 28 Jun 2020 12:23:46 +0900 (JST) Message-Id: <20200628.122346.912505386040690060.yasu@utahime.org> To: freebsd-stable@freebsd.org Subject: Re: `efivar -l` fails on UEFI booted 11.4-RELEASE From: Yasuhiro KIMURA In-Reply-To: References: <20200628.100353.961960407054898629.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49vbZG0Jvbz3Ynd X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=utahime.org header.s=maybe2019112701 header.b=lBqysAei; dmarc=none; spf=pass (mx1.freebsd.org: domain of yasu@utahime.org designates 183.180.29.210 as permitted sender) smtp.mailfrom=yasu@utahime.org X-Spamd-Result: default: False [-1.03 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[utahime.org:s=maybe2019112701]; NEURAL_HAM_MEDIUM(-1.01)[-1.006]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.97)[-0.970]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[utahime.org]; R_SPF_ALLOW(-0.20)[+a:spf-authorized.utahime.org]; DKIM_TRACE(0.00)[utahime.org:+]; NEURAL_HAM_SHORT(-0.05)[-0.054]; MID_CONTAINS_FROM(1.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2519, ipnet:183.180.0.0/16, country:JP]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2020 03:24:08 -0000 From: Kyle Evans Subject: Re: `efivar -l` fails on UEFI booted 11.4-RELEASE Date: Sat, 27 Jun 2020 21:21:10 -0500 > This should be an easy fix. :-) EFI Runtime Services on FreeBSD > ("EFIRT") wasn't necessarily globally stable until right around 12.0. > For 11.x, you'll need to `kldload efirt` or add `options EFIRT` to > your kernel config before efivar/efibootmgr become usable. Thank you for reply. After loading efirt.ko `efivar -l` succesfully lists UEFI environment variables. --- Yasuhiro KIMURA