From e4c89aa6db30343aeabd8bbbf658626a901d1eca Mon Sep 17 00:00:00 2001 From: Eitan Adler Date: Tue, 30 Oct 2012 12:01:12 +0000 Subject: [PATCH] Ancient hardware is ancient Submitted by: mjg Approved by: bcr (mentor) --- en_US.ISO8859-1/books/faq/book.xml | 160 ----------------------------- 1 file changed, 160 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml index cfe647a842..cb4b275dc2 100644 --- a/en_US.ISO8859-1/books/faq/book.xml +++ b/en_US.ISO8859-1/books/faq/book.xml @@ -1382,166 +1382,6 @@ - - - My A, T, or X series IBM Thinkpad locks up when I first - booted up my &os; installation. How can I solve - this? - - - - 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. - - According to IBM - In an email from Keith Frechette - kfrechet@us.ibm.com., - the following model/BIOS release numbers incorporate the - fix. - - - - - - Model - - BIOS revision - - - - - - T20 - - IYET49WW or later - - - - T21 - - KZET22WW or later - - - - A20p - - IVET62WW or later - - - - A20m - - IWET54WW or later - - - - A21p - - KYET27WW or later - - - - A21m - - KXET24WW or later - - - - A21e - - KUET30WW - - - - - - It has been reported that later IBM BIOS revisions may - have reintroduced the bug. This message - 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. - - 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. - - 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. - - With the machine functional again, you can use the - workaround procedure described here to get a working &os; - installation. - - - - Download boot1 and - boot2 from . - Put these files somewhere you will be able to retrieve - them later. - - - - Install &os; as normal on to the ThinkPad. - Do not use Dangerously - Dedicated mode. Do not - reboot when the install has finished. - - - - Either switch to the Emergency Holographic - Shell (AltF4) - or start a fixit shell. - - - - Use &man.fdisk.8; to change the &os; partition ID - from 165 to 166 - (this is the type used by OpenBSD). - - - - Bring the boot1 and - boot2 files to the local file - system. - - - - Use &man.disklabel.8; to write - boot1 and boot2 - to your &os; slice. - - &prompt.root; disklabel -B -b boot1 -s boot2 ad0sn - - n is the number of the - slice where you installed &os;. - - - - Reboot. At the boot prompt you will be given the - option of booting OpenBSD. This will - actually boot &os;. - - - - 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. - - - Can I install on a disk with bad blocks?