From owner-freebsd-mobile Wed Nov 29 11:50:49 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9121C37B402 for ; Wed, 29 Nov 2000 11:50:47 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eATJo4C29974; Wed, 29 Nov 2000 11:50:04 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <14885.15948.729037.110372@nomad.yogotech.com> Date: Wed, 29 Nov 2000 11:50:21 -0800 (PST) From: John Baldwin To: Nate Williams Subject: Re: Here is what IBM thinks about using FreeBSD on their newer T Cc: freebsd-mobile@FreeBSD.org, Ken Key Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29-Nov-00 Nate Williams wrote: >> I spent most of last week repeatedly converting an A21P and a T21 into >> wortless bricks and back, trying to find a way to get FreeBSD running on >> them. I distilled the death point to: >> >> - Do the install (I've used both boot0 and LILO, doesn't matter), it's >> a brick - won't even get into the BIOS menu. >> - Pull drive out and boot on my 600X. Fire up fdisk and change it from 165 >> to something else. Do not touch MBR or anything else. >> - Put drive back in (A21P and T21) and I can now get into the BIOS screens >> or actually boot via boot0 or LILO into Win2K. >> - Put drive back in 600x, change back to 165, back in *21 >> - It is a brick. >> >> So, while I don't know what IBM is doing with partition type 165, >> I am convinced it is a key to the boot lock-up problem for the >> T21 and A21P. Now boot0 has grown from 1 to 2 sectors in length, >> maybe that's what "the story inside IBM" is trying to talk about - >> I don't know. > > Didn't Robert shrink it back to 1 sector after 4.1 was released? It > would be interesting to know if the 'smaller' bootblock worked as well. Only in current, but for hte BIOS to hang, boot0 is not an issue, as boot0 isn't even being loaded or run. > (The box we're using is an A20, so it may be different from the A21 > problem..) > > > > Nate -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message