From owner-freebsd-mobile Tue Dec 12 19:26:34 2000 From owner-freebsd-mobile@FreeBSD.ORG Tue Dec 12 19:26:32 2000 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from sodium.cips.nokia.com (Sodium.cips.nokia.com [199.46.17.134]) by hub.freebsd.org (Postfix) with ESMTP id 27B4E37B400 for ; Tue, 12 Dec 2000 19:26:32 -0800 (PST) Received: from sodium.cips.nokia.com (localhost.network-alchemy.com [127.0.0.1]) by sodium.cips.nokia.com (8.9.3/8.8.8) with ESMTP id TAA04527; Tue, 12 Dec 2000 19:26:30 -0800 (PST) (envelope-from key@sodium.cips.nokia.com) Message-Id: <200012130326.TAA04527@sodium.cips.nokia.com> To: freebsd-mobile@freebsd.org Cc: key@network-alchemy.com Subject: More IBM T20 BIOS booting weirdness. Date: Tue, 12 Dec 2000 19:26:30 -0800 From: Ken Key Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, we just had the T20 that was dual-booting Win98SE and FreeBSD (the BIOS v1.03 box) become a brick. The guy was moving over to a T21 (thanks to Bruce Mah's loaning me a major clue this weekend) using the change-the-partition-type-hack. He went to reinstall Win98SE from the IBM rescue CD, to wipe it before putting it back in the pool. After it downloaded some files and tried to reboot, it exhibited the same brick behaviors I was seeing on the later BIOS version T20's, T21's, and A21P's. Got it to boot again by putting the drive in my 600x and nuking the 165. At this point, I am highly confused! I have no solid idea why it would have changed like that. Regards, K^2 -- Ken Key (key@cips.nokia.com, key@network-alchemy.com) Nokia, Clustering IP Solutions, Santa Cruz, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message