diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index f118306968..a6527e1e98 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -9,13 +9,9 @@ Frequently Asked Questions for FreeBSD 2.X, 3.X and 4.X - - - The FreeBSD Documentation Project - - + The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.136 2001/01/08 18:36:28 ben Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.137 2001/01/11 00:16:46 brian Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. @@ -1422,10 +1418,96 @@ File: +DESC (ignored) SCSI disk), etc. - + + + 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? + + + + 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. + + 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. + + With the machine functional again, you can use the workaround + procedure described here to get a working FreeBSD + installation. + + + + Download boot1 and + boot2 from http://people.freebsd.org/~bmah/ThinkPad/. + Put these files somewhere you will be able to retrieve them + later. + + + + Install FreeBSD 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 (ALT + F4) or start a + fixit shell. + + + + Use &man.fdisk.8; to change the FreeBSD partition ID from + 165 to 166 (this is the + type used by OpenBSD). + + + + Bring the boot1 and + boot2 files to the local + filesystem. + + + + Use &man.disklabel.8; to write boot1 + and boot2 to your FreeBSD slice. + + &prompt.root; disklabel -B -b boot1 -s boot2 ad0sn + + n is the number of the slice + where you installed FreeBSD. + + + + Reboot. At the boot prompt you will be given the option + of booting OpenBSD. This will actually + boot FreeBSD. + + + + 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. + + + Can I install on a disk with bad blocks? diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index f118306968..a6527e1e98 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -9,13 +9,9 @@ Frequently Asked Questions for FreeBSD 2.X, 3.X and 4.X - - - The FreeBSD Documentation Project - - + The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.136 2001/01/08 18:36:28 ben Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.137 2001/01/11 00:16:46 brian Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. @@ -1422,10 +1418,96 @@ File: +DESC (ignored) SCSI disk), etc. - + + + 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? + + + + 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. + + 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. + + With the machine functional again, you can use the workaround + procedure described here to get a working FreeBSD + installation. + + + + Download boot1 and + boot2 from http://people.freebsd.org/~bmah/ThinkPad/. + Put these files somewhere you will be able to retrieve them + later. + + + + Install FreeBSD 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 (ALT + F4) or start a + fixit shell. + + + + Use &man.fdisk.8; to change the FreeBSD partition ID from + 165 to 166 (this is the + type used by OpenBSD). + + + + Bring the boot1 and + boot2 files to the local + filesystem. + + + + Use &man.disklabel.8; to write boot1 + and boot2 to your FreeBSD slice. + + &prompt.root; disklabel -B -b boot1 -s boot2 ad0sn + + n is the number of the slice + where you installed FreeBSD. + + + + Reboot. At the boot prompt you will be given the option + of booting OpenBSD. This will actually + boot FreeBSD. + + + + 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. + + + Can I install on a disk with bad blocks?