From owner-freebsd-current@freebsd.org Mon Jul 13 19:45:56 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 A756C99CF29 for ; Mon, 13 Jul 2015 19:45:56 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 345E6E8C; Mon, 13 Jul 2015 19:45:55 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id t6DJjlua022978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 13 Jul 2015 13:45:47 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id t6DJjks3022975; Mon, 13 Jul 2015 13:45:46 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 13 Jul 2015 13:45:46 -0600 (MDT) From: Warren Block To: Allan Jude cc: Hans Ottevanger , "Andrey V. Elsukov" , freebsd-current@freebsd.org Subject: Re: Lenovo BIOS boot fix In-Reply-To: <55A41036.2070602@freebsd.org> Message-ID: 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> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 13 Jul 2015 13:45:47 -0600 (MDT) 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:45:56 -0000 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.