Date: Mon, 13 Jul 2015 12:08:24 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Allan Jude <allanjude@freebsd.org> Cc: Hans Ottevanger <hans@beastielabs.net>, "Andrey V. Elsukov" <bu7cher@yandex.ru>, freebsd-current@freebsd.org Subject: Re: Lenovo BIOS boot fix Message-ID: <alpine.BSF.2.20.1507131156570.88315@wonkity.com> In-Reply-To: <55A3DF26.5020602@freebsd.org> References: <55A1FFD5.7080008@freebsd.org> <55A2030B.7010405@freebsd.org> <55A2835F.1030004@yandex.ru> <55A2ACDD.408@freebsd.org> <55A36FBE.1020206@beastielabs.net> <55A3D01E.40102@freebsd.org> <alpine.BSF.2.20.1507130915250.56039@wonkity.com> <55A3DF26.5020602@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 Jul 2015, Allan Jude wrote: > On 2015-07-13 11:19, Warren Block wrote: >>> >>> Needing the active flag set is indeed a different problem. I am working >>> on a patch for bsdinstall that will allow the user to request the active >>> bit be set as well. >> >> For GPT, that should be the default, because it matches the standard. >> >> I would like to see an effort to get Lenovo to fix their broken >> UEFI/BIOS. Adding non-standard PMBR configurations should be short-term >> hack. > > Lenovo has fixed the issue in newer models, x230, t530, t540 etc work fine. > > Just the x220, t420, and t520 etc series do not. The latest BIOS update for the x220 was less than two months ago, so it is still supported. That they've fixed the problem in other models shows they understand the issue. So owners of those models should be bugging Lenovo, so to speak. Long-term, it seems like they as a company would be concerned that special bug fixes naming their specific models are needed. Short-term, we probably can't avoid this. It would be nice to be able to remove a Lenovo-specific hack from gpart in the future with a commit that says "Fixed by Lenovo BIOS update #123, no longer needed".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1507131156570.88315>