Add a question explaining how to get FreeBSD working on one of those
newfangled IBM Thinkpads with a broken BIOS. A joint effort between myself and Bruce (bmah). While I'm here, change <author> in the header to <corpauthor>, which is more DocBook'ly correct.
This commit is contained in:
Nik Clayton
parent
ffc90df9b4
commit
1a2cb783d0
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=8692
2 changed files with 178 additions and 14 deletions
|
|
@ -9,13 +9,9 @@
|
|||
<bookinfo>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X, 3.X and 4.X</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<surname>The FreeBSD Documentation Project</surname>
|
||||
</author>
|
||||
</authorgroup>
|
||||
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.136 2001/01/08 18:36:28 ben Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.137 2001/01/11 00:16:46 brian Exp $</pubdate>
|
||||
|
||||
<abstract>
|
||||
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
|
||||
|
|
@ -1422,10 +1418,96 @@ File: +DESC (ignored)</screen>
|
|||
SCSI disk), etc.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="boot-on-thinkpad">
|
||||
<para>I have an IBM Thinkpad in the A, T, or X series that FreeBSD
|
||||
installs on, but then the machine locks up on next boot. How can I
|
||||
solve this?</para>
|
||||
</question>
|
||||
|
||||
<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. A
|
||||
workaround is to install FreeBSD, change the partition ID FreeBSD
|
||||
uses, and install new boot blocks that can handle the different
|
||||
partition ID.</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 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.</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Download <filename>boot1</filename> and
|
||||
<filename>boot2</filename> from <ulink
|
||||
url="http://people.freebsd.org/~bmah/ThinkPad/">http://people.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 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="install-bad-blocks">
|
||||
<para>Can I install on a disk with bad blocks?</para>
|
||||
|
|
|
|||
|
|
@ -9,13 +9,9 @@
|
|||
<bookinfo>
|
||||
<title>Frequently Asked Questions for FreeBSD 2.X, 3.X and 4.X</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<surname>The FreeBSD Documentation Project</surname>
|
||||
</author>
|
||||
</authorgroup>
|
||||
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.136 2001/01/08 18:36:28 ben Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.137 2001/01/11 00:16:46 brian Exp $</pubdate>
|
||||
|
||||
<abstract>
|
||||
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
|
||||
|
|
@ -1422,10 +1418,96 @@ File: +DESC (ignored)</screen>
|
|||
SCSI disk), etc.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="boot-on-thinkpad">
|
||||
<para>I have an IBM Thinkpad in the A, T, or X series that FreeBSD
|
||||
installs on, but then the machine locks up on next boot. How can I
|
||||
solve this?</para>
|
||||
</question>
|
||||
|
||||
<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. A
|
||||
workaround is to install FreeBSD, change the partition ID FreeBSD
|
||||
uses, and install new boot blocks that can handle the different
|
||||
partition ID.</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 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.</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Download <filename>boot1</filename> and
|
||||
<filename>boot2</filename> from <ulink
|
||||
url="http://people.freebsd.org/~bmah/ThinkPad/">http://people.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 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="install-bad-blocks">
|
||||
<para>Can I install on a disk with bad blocks?</para>
|
||||
|
|
|
|||
Loading…
Reference in a new issue