From owner-freebsd-questions@freebsd.org Tue Jan 12 15:53:38 2021 Return-Path: Delivered-To: freebsd-questions@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 32ACD4DCF29 for ; Tue, 12 Jan 2021 15:53:38 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from cp160176.hpdns.net (cp160176.hpdns.net [91.238.160.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DFZqh67bTz3jTk for ; Tue, 12 Jan 2021 15:53:36 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=milibyte.co.uk; s=default; h=Content-Type:Content-Transfer-Encoding: MIME-Version:Message-ID:Date:Subject:To:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=bqVQLJAgn4Q/qnh+csryVLzrIysQCyEdKHWyHRhaX3s=; b=dG3sWJ/1kyHa0fcN2v7E4th2V4 vd8eZrORRfNysKFvLEKll8wZvCGvUcr+/iNyiOUSZpHq70sJt06++IV8KQqiRw67NWaLyjNxt38BE X5zZ3g8ypj9zRDX4Q2kZdqcK42FxuBCCzRZF7c5msxHXWRptg8ZP9+JLQxz4U2ev0Kz/uczrKbEE6 QSPLnNSoL4awBDfVpf32Q20uAVT1CJooSvxUbj6BgEDGoahrHzUsPpuV3PcsgddA50BnH/iwHaEVE MvpKaR9VbDDnNyy/5rVQh00rlgrSLbXU57qYLIl42R5EqaU/B6DcFApRHUSPL1UBUMIVQJ1SKqq9C DgBlLZ+w==; Received: from 82-71-56-121.dsl.in-addr.zen.co.uk ([82.71.56.121]:29319 helo=curlew.milibyte.co.uk) by cp160176.hpdns.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1kzLyw-000483-EG for freebsd-questions@freebsd.org; Tue, 12 Jan 2021 15:53:18 +0000 Received: from [127.0.0.1] (helo=curlew.localnet) by curlew.milibyte.co.uk with esmtp (Exim 4.94) (envelope-from ) id 1kzLyw-0000o5-HL for freebsd-questions@freebsd.org; Tue, 12 Jan 2021 15:53:18 +0000 From: Mike Clarke To: FreeBSD questions Subject: Several 'Not supported' messages with UEFI boot Date: Tue, 12 Jan 2021 15:53:17 +0000 Message-ID: <9050372.RH3biPoPvx@curlew> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-SA-Exim-Scanned: No (on curlew.milibyte.co.uk); SAEximRunCond expanded to false X-YourOrg-MailScanner-Information: Please contact the ISP for more information X-YourOrg-MailScanner-ID: 1kzLyw-000483-EG X-YourOrg-MailScanner: Found to be clean X-YourOrg-MailScanner-SpamCheck: X-YourOrg-MailScanner-From: jmc-freebsd2@milibyte.co.uk X-Spam-Status: No X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp160176.hpdns.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - milibyte.co.uk X-Get-Message-Sender-Via: cp160176.hpdns.net: authenticated_id: mailpool@milibyte.co.uk X-Authenticated-Sender: cp160176.hpdns.net: mailpool@milibyte.co.uk X-Source: X-Source-Args: X-Source-Dir: X-Rspamd-Queue-Id: 4DFZqh67bTz3jTk X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=milibyte.co.uk header.s=default header.b=dG3sWJ/1; dmarc=none; spf=pass (mx1.freebsd.org: domain of jmc-freebsd2@milibyte.co.uk designates 91.238.160.176 as permitted sender) smtp.mailfrom=jmc-freebsd2@milibyte.co.uk X-Spamd-Result: default: False [-2.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; HAS_X_SOURCE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[milibyte.co.uk:+]; NEURAL_HAM_SHORT(-1.00)[-0.999]; HAS_X_ANTIABUSE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[91.238.160.176:from]; CTE_CASE(0.50)[]; ASN(0.00)[asn:12703, ipnet:91.238.160.0/22, country:GB]; HAS_X_AS(0.00)[mailpool@milibyte.co.uk]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[milibyte.co.uk:s=default]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[milibyte.co.uk]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[91.238.160.176:from:127.0.2.255]; HAS_X_GMSV(0.00)[mailpool@milibyte.co.uk]; MID_RHS_NOT_FQDN(0.50)[]; MAILMAN_DEST(0.00)[freebsd-questions] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2021 15:53:38 -0000 As an experiment I've switched from legacy boot to UEFI. It seems to be working OK except that I see several 'Not supported' messages at the start of the boot process. I've manually typed the following boot messages from a video shot of the start up so there may be a few typos. >> FreeBSD EFI boot block Loader path /boot/loader.efi Initializing modules: ZFS UFS Load Path: \EFI\BOOT\BOOTX64,EFI Load Device: PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x0,0x0)/HD(2,GPT, 62ea9e00-529a-11eb-94b8-408d5c843d74,0x428,0xbd8) BootCurrent: 002e BootOrder: 002e[*] 002d 0028 002a 0026 0017 0018 0016 0019 0029 002b Probing 18 block devices...not supported not supported not supported not supported not supported not supported not supported not supported not supported not supported not supported better not supported not supported not supported good good not supported done ZFS found the following pools: ssd home UFS found no partitions Consoles: EFI console Things then scrolled too fast to capture a sharp video until the FreeBSD loader menu appeared and everything went normally. So should I worry about the 'Not supported' messages, just ignore them or revert to legacy boot? -- Mike Clarke