From owner-freebsd-mobile  Fri Nov  9  3:49: 9 2001
Delivered-To: freebsd-mobile@freebsd.org
Received: from web14807.mail.yahoo.com (web14807.mail.yahoo.com [216.136.224.223])
	by hub.freebsd.org (Postfix) with SMTP id 5D49937B420
	for <freebsd-mobile@freebsd.org>; Fri,  9 Nov 2001 03:49:06 -0800 (PST)
Message-ID: <20011109114904.58079.qmail@web14807.mail.yahoo.com>
Received: from [202.163.243.212] by web14807.mail.yahoo.com via HTTP; Fri, 09 Nov 2001 03:49:03 PST
Date: Fri, 9 Nov 2001 03:49:03 -0800 (PST)
From: Pratibha <ibpratibha@yahoo.com>
Subject: IBM ThinkPad T20 BIOS 1.16-IYET56WW
To: freebsd-mobile@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-mobile@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-mobile.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-mobile>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-mobile>
X-Loop: FreeBSD.org

Can anyone please confirm that this particular
BIOS version is indeed NOT plagued by the dreaded
cannot-boot-after-installing-FreeBSD problem?
I have just upgraded my IBM ThinkPad T20 from BIOS
version 1.07-IYET43WW to this 1.16-IYET56WW version.  

I have seen the past tales of woe about ThinkPads not
being able to boot after installation of FreeBSD.

I know that there was an official-looking e-mail
dated 15-Feb-2001 from Keith Frechette of IBM
<kfrechet@us.ibm.com> saying that for the T20,
BIOS version "IYET49WW or later" has fixed the
problem:
http://www.clave.gr.jp/ml/bsd-nomads/200102/msg00050.html
This information is also reflected in the FAQ:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#BOOT-ON-THINKPAD

HOWEVER, I HESITATE, because that same FAQ, section
2.10, says ominously and cryptically:  "It has been
reported that later IBM BIOS revisions may have
reintroduced the bug."

So can someone please confirm that the BIOS
version that I have, 1.16-IYET56WW, has not
reintroduced the bug?  In general, is it known or
documented somewhere which BIOS revisions have,
or may have, reintroduced the bug?

I don't want to "just try it out and see what
happens", because in my present circumstances
[travelling,
away from home base], it would be very hard to
recover from a disaster (nonbootable condition)
on my laptop.

Thanks,
IBPratibha

__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message