Date: Fri, 22 Dec 2000 12:18:05 -0800 From: "Bruce A. Mah" <bmah@FreeBSD.ORG> To: Nik Clayton <nik@FreeBSD.ORG> Cc: "Bruce A. Mah" <bmah@FreeBSD.ORG>, John Van Sickle <johnandsamson@home.com>, freebsd-mobile@FreeBSD.ORG Subject: Re: Thinkpad Partition Problem Solved? Message-ID: <200012222018.eBMKI5E45367@bmah-freebsd-0.cisco.com> In-Reply-To: <20001222112445.A84939@canyon.nothing-going-on.org> References: <002001c06b69$278a7f60$d84c0f18@evansv1.in.home.com> <200012211849.eBLIngE35110@bmah-freebsd-0.cisco.com> <20001222112445.A84939@canyon.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_969930484P Content-Type: text/plain; charset=us-ascii If memory serves me right, Nik Clayton wrote: > Attached is a FAQ patch. Comments? Cool! Wish I'd thought of this idea; the "F" has certainly been true for me the last couple of weeks. :-) Comments on the text in-line... [snip] > Index: book.sgml > =================================================================== > RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/faq/book.sgml,v > retrieving revision 1.129 > diff -u -r1.129 book.sgml > --- book.sgml 2000/12/05 13:18:16 1.129 > +++ book.sgml 2000/12/22 11:24:17 > @@ -2399,6 +2399,75 @@ > </qandaentry> In my addled mental state, I read this as <quandry>. :-p > <qandaentry> > + <question id="boot-on-thinkpad"> > + <para>I have an IBM Thinkpad A20p that FreeBSD installs on, but then > + the machine locks up on next boot. How can I solve this?</para> > + </question> I'd start with "I have an IBM ThinkPad in the A, T, or X series...". My wonderful (actually it *is*, now that this problem's solved) T20 crapped out to start this off. There's two problems to be solved here. The first is to get the machine past its self-test screen. The second is to get FreeBSD installed in a way that can boot. The text I wrote gets the reader through the second problem, but there's still the first part to deal with. OK, how about something like this: > + > + <answer> > + <para>It seems as though IBM decided to use partition ID 165 for > + their suspend-to-disk partition. This is the same ID FreeBSD > + uses, and after installing FreeBSD the BIOS refuses to boot. </para> <para>First, you'll need to to restore the machine to a state where it can get through its self-test screen. Doing this requires powering up the machine up without letting it find a FreeBSD partition on its primary disk. One way is to remove the hard disk and temporarily move it to an older ThinkPad (such as a ThinkPad 600) or a desktop PC with an appropriate conversion cable. Once it's there, you can delete the FreeBSD partition and move the hard disk back. The ThinkPad should now be in a bootable state again.</para> <para>With the machine functional again, you can use the workaround procedure described here to get a working FreeBSD installation. Essentially, you will perform an install of FreeBSD, change the partition ID that FreeBSD uses, and install new blocks that can handle the different partition ID.</para> > + <procedure> > + <step> > + <para>Download <filename>boot1</filename> and > + <filename>boot2</filename> from <ulink > + url="http://people.freebsd.org/~bmah/ThinkPad/">http://peo > ple.freebsd.org/~bmah/ThinkPad/</ulink>. > + Put these files somewhere you will be able to retrieve them > + later.</para> > + </step> > + > + <step> > + <para>Install FreeBSD as normal on to the ThinkPad. > + <emphasis>Do not</emphasis> use <literal>Dangerously > + Dedicated</literal> mode. <emphasis>Do not</emphasis> > + reboot when the install has finished.</para> > + </step> > + > + <step> > + <para>Either switch to the <quote>Emergency Holographic > + Shell</quote> (<keycombo><keycap>ALT</keycap> > + <keycap>F4</keycap></keycombo>) or start a > + <quote>fixit</quote> shell.</para> > + </step> > + > + <step> > + <para>Use &man.fdisk.8; to change the FreeBSD partition ID from > + <literal>165</literal> to <literal>166</literal> (this is the > + type used by OpenBSD).</para> > + </step> > + > + <step> > + <para>Bring the <filename>boot1</filename> and > + <filename>boot2</filename> files to the local > + filesystem.</para> > + </step> > + > + <step> > + <para>Use &man.disklabel.8; to write <filename>boot1</filename> > + and <filename>boot2</filename> to your FreeBSD slice.</para> > + > + <screen>&prompt.root; <userinput>disklabel -B -b boot1 -s boot2 a > d0</userinput></screen> > + </step> One correction. First, we don't write to the disk itself, we need to write to the slice. Second, we unfortunately don't know what exact slice the user needs to use (since we can't clairvoyantly see their partition table. So: <step> <para>Use &man.disklabel.8; to write <filename>boot1</filename> and <filename>boot2</filename> to your FreeBSD slice.</para> <screen>&prompt.root; <userinput>disklabel -B -b boot1 -s boot2 ad0s<replaceable>n</replaceable></userinput></screen> <para><replaceable>n</replaceable> is the number of the slice where you installed FreeBSD.</para> </step> > + > + <step> > + <para>Reboot. At the boot prompt you will be given the option > + of booting <literal>OpenBSD</literal>. This will actually > + boot FreeBSD.</para> > + </step> > + </procedure> > + > + <para>Getting this to work in the case where you want to dual boot > + OpenBSD and FreeBSD on the same laptop is left as an exercise for > + the reader.</para> > + </answer> > + </qandaentry> > + > + <qandaentry> > <question id="jaz-zip-removable-support"> > <para>Does FreeBSD support JAZ, EZ and other removable > drives?</para> Nice job of mark-up BTW. I think I learned a couple of things reading this. Thanks! Bruce. --==_Exmh_969930484P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6Q7b82MoxcVugUsMRAtChAJ9NvCnQvbPQQicYW9CRWqvhwWFK0gCfa8RL wV2pXEM86/IW+wkw4JMHrnI= =wS6K -----END PGP SIGNATURE----- --==_Exmh_969930484P-- 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?200012222018.eBMKI5E45367>