Ancient hardware is ancient
Submitted by: mjg Approved by: bcr (mentor)
This commit is contained in:
Eitan Adler
parent
0e384fff4f
commit
e4c89aa6db
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=39851
1 changed files with 0 additions and 160 deletions
|
|
@ -1382,166 +1382,6 @@
|
|||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="boot-on-thinkpad">
|
||||
<para>My A, T, or X series IBM Thinkpad locks up when I first
|
||||
booted up my &os; installation. How can I solve
|
||||
this?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>A bug in early revisions of IBM's BIOS on these machines
|
||||
mistakenly identifies the &os; partition as a potential FAT
|
||||
suspend-to-disk partition. When the BIOS tries to parse the
|
||||
&os; partition it hangs.</para>
|
||||
|
||||
<para>According to IBM<footnote>
|
||||
<para>In an email from Keith Frechette
|
||||
<email>kfrechet@us.ibm.com</email>.</para></footnote>,
|
||||
the following model/BIOS release numbers incorporate the
|
||||
fix.</para>
|
||||
|
||||
<informaltable frame="none" pgwide="1">
|
||||
<tgroup cols="2">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>Model</entry>
|
||||
|
||||
<entry>BIOS revision</entry>
|
||||
</row>
|
||||
</thead>
|
||||
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>T20</entry>
|
||||
|
||||
<entry>IYET49WW or later</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>T21</entry>
|
||||
|
||||
<entry>KZET22WW or later</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>A20p</entry>
|
||||
|
||||
<entry>IVET62WW or later</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>A20m</entry>
|
||||
|
||||
<entry>IWET54WW or later</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>A21p</entry>
|
||||
|
||||
<entry>KYET27WW or later</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>A21m</entry>
|
||||
|
||||
<entry>KXET24WW or later</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>A21e</entry>
|
||||
|
||||
<entry>KUET30WW</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
|
||||
<para>It has been reported that later IBM BIOS revisions may
|
||||
have reintroduced the bug. <ulink
|
||||
url="http://docs.FreeBSD.org/cgi/mid.cgi?20010427133759.A71732">This message</ulink>
|
||||
from &a.nectar; to the &a.mobile; describes a procedure
|
||||
which may work if your newer IBM laptop does not boot &os;
|
||||
properly, and you can upgrade or downgrade the BIOS.</para>
|
||||
|
||||
<para>If you have an earlier BIOS, and upgrading is not an
|
||||
option, a workaround is to install &os;, change the partition
|
||||
ID &os; uses, and install new boot blocks that can handle
|
||||
the different partition ID.</para>
|
||||
|
||||
<para>First, you will need 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
|
||||
&os; 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 is there, you can delete the &os;
|
||||
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 &os;
|
||||
installation.</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Download <filename>boot1</filename> and
|
||||
<filename>boot2</filename> from <ulink
|
||||
url="http://people.FreeBSD.org/~bmah/ThinkPad/"></ulink>.
|
||||
Put these files somewhere you will be able to retrieve
|
||||
them later.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Install &os; 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
|
||||
action="simul"><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 &os; 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 file
|
||||
system.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Use &man.disklabel.8; to write
|
||||
<filename>boot1</filename> and <filename>boot2</filename>
|
||||
to your &os; 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 &os;.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Reboot. At the boot prompt you will be given the
|
||||
option of booting <literal>OpenBSD</literal>. This will
|
||||
actually boot &os;.</para>
|
||||
</step>
|
||||
</procedure>
|
||||
|
||||
<para>Getting this to work in the case where you want to dual
|
||||
boot OpenBSD and &os; 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