Date: Wed, 29 Nov 2000 10:35:08 -0700 (MST) From: Nate Williams <nate@yogotech.com> To: Ken Key <key@network-alchemy.com> Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Here is what IBM thinks about using FreeBSD on their newer Thinkpads Message-ID: <14885.15948.729037.110372@nomad.yogotech.com> In-Reply-To: <200011291710.JAA88193@sodium.cips.nokia.com> References: <200011290551.eAT5pJF28047@mass.osd.bsdi.com> <200011291710.JAA88193@sodium.cips.nokia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. (The box we're using is an A20, so it may be different from the A21 problem..) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14885.15948.729037.110372>