From owner-freebsd-current@freebsd.org Sun Mar 25 09:55:42 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 46E72F5D4A1 for ; Sun, 25 Mar 2018 09:55:42 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (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 D0F0D7DD13; Sun, 25 Mar 2018 09:55:41 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 408CM86st4zDhKF; Sun, 25 Mar 2018 09:55:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1521971732; bh=dgGG2ptgp7C1WAOgc5hPLC5D qzNsVZmbOGKc/eNN7c0=; b=oI84QZjpnBEI5VIcCzEbhEiXdv6WkorhqAw5YP8K VnF61vjd23FawKZaPoFfhZ/XcU8P8CA7z58YIHZyPYkklPM04WRKDeFcu0kkgyAh Ytw9SlBrFTDjig5Aag0KL+E0siSaRvGz8t/smNYHNo9jNn0x+97Qe74SclfjDFSg I8A= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id GuG391MSJ2Kr; Sun, 25 Mar 2018 09:55:32 +0000 (UTC) Received: from celes.daemonic.se (celes.daemonic.se [IPv6:2001:470:dca9:2::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 408CM83b2NzDhK1; Sun, 25 Mar 2018 09:55:32 +0000 (UTC) Subject: Re: Call for Testing: UEFI Changes To: Kyle Evans , FreeBSD Current References: From: Niclas Zeising Message-ID: Date: Sun, 25 Mar 2018 11:54:38 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sun, 25 Mar 2018 09:55:42 -0000 On 03/22/18 01:45, Kyle Evans wrote: > Hello! > > A number of changes have gone in recently pertaining to UEFI booting > and UEFI runtime services. The changes with the most damaging > potential are: > > We now put UEFI runtime services into virtual address mode, fixing > runtime services with U-Boot/UEFI as well as the firmware > implementation in many Lenovos. The previously observed behavior was a > kernel panic upon invocation of efibootmgr/efivar, or a kernel panic > just loading efirt.ko or compiling EFIRT into the kernel. > > Graphics mode selection is now done differently to avoid regression > caused by r327058 while still achieving the same effect. The observed > regression was that the kernel would usually end up drawing > incorrectly at the old resolution on a subset of the screen, due to > incorrect framebuffer information. > > Explicit testing of these changes, the latest of which happened in > r331326, and any feedback from this testing would be greatly > appreciated. Testing should be done with either `options EFIRT` in > your kernel config or efirt.ko loaded along with updated bootloader > bits. > > I otherwise plan to MFC commits involved with the above-mentioned > changes by sometime in the first week of April, likely no earlier than > two (2) weeks from now on April 4th. > Hi! I've tested on two different computers, my ThinkPad x230 and my desktop with a Intel DQ77MK motherboard. I've only done light testing such as loading efirt.ko and running efibootmgr to check the boot settings, but it has worked fine. I also haven't seen any issues with console graphics on either machine. Both computers are running CURRENT from yesterday, the desktop is on r331481 and the laptop probably somewhere around that as well. Please let me know if you want me to test anything else! Regards -- Niclas