From owner-freebsd-current@freebsd.org Mon Jul 13 23:18:19 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 D7D3C9959AE for ; Mon, 13 Jul 2015 23:18:19 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99B171D50; Mon, 13 Jul 2015 23:18:19 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by oihq81 with SMTP id q81so51258571oih.2; Mon, 13 Jul 2015 16:18:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=TnREVNH4kGGaP5e/pW69ctwF2i2eKUAaaGYqdsqmFok=; b=hkGTtxFtfo/NJuUvcVHXQtj37ZxzBYWTw1Qog3s5xAKcNdrKA1kKURffwsvvK67Qgl xsVvyHVDqhtVW8S8Mp197VrqgZtHO4PGNh4LRlnGRo3EHOPO0t/yvbroh7tAF3DZ4tzi wcsGNYUV1tq3gaeF4hNBOBN2GtWXsX3aJXw0Zf7zJhtUBiPvDj03Hbp7U5Pylx92uBhM RQ6Z15u3sq65NwxjWsfLIsas+Upyt09hZW8Z1LKFEwXU0d6pQUpcj70c+kkd++V3+Y4O gFr/2qTVoD/JWBuI45xYBb19RkvtRycN4nMimliAtyHkNMl03WwTgghAntNik9Xnpxrs RtDg== MIME-Version: 1.0 X-Received: by 10.182.250.137 with SMTP id zc9mr3095491obc.79.1436829499044; Mon, 13 Jul 2015 16:18:19 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.221.69 with HTTP; Mon, 13 Jul 2015 16:18:18 -0700 (PDT) In-Reply-To: <55A416EC.2020306@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> <55A3DF26.5020602@freebsd.org> <55A41036.2070602@freebsd.org> <55A416EC.2020306@freebsd.org> Date: Mon, 13 Jul 2015 16:18:18 -0700 X-Google-Sender-Auth: ctyCeuYnzUtLSmshdhRMZYp2L44 Message-ID: Subject: Re: Lenovo BIOS boot fix From: Kevin Oberman To: Allan Jude Cc: Warren Block , Hans Ottevanger , "Andrey V. Elsukov" , FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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 23:18:19 -0000 On Mon, Jul 13, 2015 at 12:52 PM, Allan Jude wrote: > 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 This is possibly orthogonal and possibly not of use on X2nn systems, but I boot my T520 with a GPT formatted disk as the secondary drive by having the MBR disk0 configured with booteasy and telling it to boot disk1. While this is of no use on single spindle systems like the X220, I have been told that a MBR USB drive can be used to do the same thing. I have not tried this and can't confirm, though. Clearly a kludge work-around, but better than nothing and works well for me as I have always left Windows on the main drive and put FreeBSD on the removable one. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683