Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Mar 2018 13:56:11 -0300
From:      Renato Botelho <garga.bsd@gmail.com>
To:        Kyle Evans <kevans@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Call for Testing: UEFI Changes
Message-ID:  <02f4f83b-7cbc-feff-8858-87570c58640c@gmail.com>
In-Reply-To: <CACNAnaFmu2rFF1w4ar4xHUbN5vHitTLi0Ui6aCjL1MuTj3iJsQ@mail.gmail.com>
References:  <CACNAnaFmu2rFF1w4ar4xHUbN5vHitTLi0Ui6aCjL1MuTj3iJsQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 21/03/18 21: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.

Just FYI,

After upgrade to r331350 on a Thinkpad X230 using drm-next-kmod
trackpoint stopped working and touchpad worked but 3 buttons above it
didn't. Removing drm-next-kmod and start using i915kms.ko from
/boot/kernel fixed it.

-- 
Renato Botelho



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?02f4f83b-7cbc-feff-8858-87570c58640c>