From owner-freebsd-current@freebsd.org Mon Jul 13 19:52:15 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E950099C09B for ; Mon, 13 Jul 2015 19:52:15 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id C67E2150C for ; Mon, 13 Jul 2015 19:52:15 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [192.168.1.10] (unknown [192.168.1.10]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id CADD099B7; Mon, 13 Jul 2015 19:52:14 +0000 (UTC) Message-ID: <55A416EC.2020306@freebsd.org> Date: Mon, 13 Jul 2015 15:52:12 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Warren Block CC: Hans Ottevanger , "Andrey V. Elsukov" , freebsd-current@freebsd.org Subject: Re: Lenovo BIOS boot fix 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> <55A3DF26.5020602@freebsd.org> <55A41036.2070602@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Mon, 13 Jul 2015 19:52:16 -0000 On 2015-07-13 15:45, Warren Block wrote: > On Mon, 13 Jul 2015, Allan Jude wrote: > >> On 2015-07-13 14:08, Warren Block wrote: >>> 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". >> >> I tried the latest bios update for the X220, from 2015-05-27 >> >> It does not resolve the issue. >> >> Also, it required some hoop jumping, as they only provide a bootable >> cd (x220s do not have CD drives) and a windows program. >> >> However, if others are interested, this handy perl script: >> http://userpages.uni-koblenz.de/~krienke/ftp/noarch/geteltorito/ >> >> can be used to extract the el torito image from that .iso to a file, >> that can then be dd'd to a USB stick and update the bios. > > Sorry, I did not mean to imply that the latest X220 BIOS fixed the > problem, just that they were continuing to release BIOS updates for it > and could not disown responsibility by saying the system was no longer > supported. Right. I was not aware they were still publishing BIOSs, so I was hopeful it was fixed, and was disappointed after jumping through the hoops to get the update without installing windows on my machine, or somehow connecting a CD drive to it. Anyway, yes, hopefully Lenovo will fix this someday. -- Allan Jude