From 3d8da60ac53b17688f60aa6cd41a8ccfdaf50089 Mon Sep 17 00:00:00 2001 From: "Bruce A. Mah" Date: Mon, 6 Aug 2007 20:25:31 +0000 Subject: [PATCH] Copy the "Common Installation Problems" section from the installation notes to the installation chapter of the handbook. This is basically a verbatim copy except for changes that were necessary to make the new text build (consisted of removing a few entities and arch= attributes). Subsequent commits will remove questions that (in my opinion) are no longer relevant or recent and adjust whitespace to match the rest of this file. --- .../books/handbook/install/chapter.sgml | 331 ++++++++++++++++++ 1 file changed, 331 insertions(+) diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml index 3c10bc566b..e52c57c5e0 100644 --- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml @@ -4035,6 +4035,337 @@ Please press any key to reboot. NTFS partitions can also be mounted in a similar manner using the &man.mount.ntfs.8; command. + + + Troubleshooting Questions and Answers + + + + + My system hangs while probing hardware during boot, or it + behaves strangely during install, or the floppy drive isn't + probed. + + + &os; 5.0 and above makes extensive use of the system ACPI + service on the i386, amd64 and ia64 platforms to aid in system + configuration if it's detected during boot. Unfortunately, + some bugs still exist in both the ACPI driver and within system + motherboards and BIOS. The use of ACPI can be disabled by setting + the hint.acpi.0.disabled hint in the third stage + boot loader: + + set hint.acpi.0.disabled="1" + + This is reset each time the system is booted, so it is + necessary to add hint.acpi.0.disabled="1" + to the file + /boot/loader.conf. More information about the + boot loader can be found in the &os; Handbook. + + + + + My legacy ISA device used to be recognized in previous versions + of &os;, but now it's not. What happened? + + + Some device drivers, like matcd, were removed over time due to + lack of maintainership or other reasons. Others still exist but + are disabled because of their intrusive hardware probe routines. + The following ISA device drivers fall into this category and can + re-enabled from the third stage boot loader: aha, ahv, aic, bt, ed, + cs, sn, ie, fe, le, and lnc. To do this, stop the loader during + it's 10 second countdown and enter the following at the + prompt: + + unset hint.foo.0.disabled + + where foo is the name of the driver + to re-enable. This can be set permanently by editing the file + /boot/device.hints and removing the appropriate + disabled entry. + + + + + I go to boot from the hard disk for the first time + after installing &os;, the kernel loads and probes my + hardware, but stops with messages like: + + changing root device to ad1s1a panic: cannot mount root + What is wrong? What can I do? + + What is this + bios_drive:interface(unit,partition)kernel_name + thing that is displayed with the boot help? + + + There is a longstanding problem in the case where the + boot disk is not the first disk in the system. The BIOS + uses a different numbering scheme to &os;, and working + out which numbers correspond to which is difficult to get + right. + + In the case where the boot disk is not the first disk + in the system, &os; can need some help finding it. There + are two common situations here, and in both of these cases, + you need to tell &os; where the root filesystem is. You + do this by specifying the BIOS disk number, the disk type + and the &os; disk number for that type. + + The first situation is where you have two IDE disks, + each configured as the master on their respective IDE + busses, and wish to boot &os; from the second disk. The + BIOS sees these as disk 0 and disk 1, while &os; sees + them as ad0 and + ad2. + + &os; is on BIOS disk 1, of type + ad and the &os; disk number is 2, so + you would say: + + 1:ad(2,a)kernel + + Note that if you have a slave on the primary bus, the + above is not necessary (and is effectively wrong). + + The second situation involves booting from a SCSI disk + when you have one or more IDE disks in the system. In this + case, the &os; disk number is lower than the BIOS disk + number. If you have two IDE disks as well as the SCSI disk, + the SCSI disk is BIOS disk 2, type da and + &os; disk number 0, so you would say: + + 2:da(0,a)kernel + + To tell &os; that you want to boot from BIOS disk + 2, which is the first SCSI disk in the system. If you only + had one IDE disk, you would use '1:' instead. + + Once you have determined the correct values to use, + you can put the command exactly as you would have typed it + in the /boot.config file using a + standard text editor. Unless instructed otherwise, &os; + will use the contents of this file as the default response + to the boot: prompt. + + + + + I go to boot from the hard disk for the first time + after installing &os;, but the Boot Manager prompt just + prints F? at the boot menu each time but + the boot won't go any further. + + + The hard disk geometry was set incorrectly in the + Partition editor when you installed &os;. Go back into + the partition editor and specify the actual geometry of your + hard disk. You must reinstall &os; again from the + beginning with the correct geometry. + + If you are failing entirely in figuring out the + correct geometry for your machine, here's a tip: Install a + small DOS partition at the beginning of the disk and install + &os; after that. The install program will see the DOS + partition and try to infer the correct geometry from it, + which usually works. + + The following tip is no longer recommended, but is left here + for reference: + +
+ If you are setting up a truly dedicated &os; + server or workstation where you don't care for (future) + compatibility with DOS, Linux or another operating system, + you've also got the option to use the entire disk (`A' in + the partition editor), selecting the non-standard option + where &os; occupies the entire disk from the very first + to the very last sector. This will leave all geometry + considerations aside, but is somewhat limiting unless + you're never going to run anything other than &os; on a + disk. +
+ + + + + The &man.mcd.4; driver keeps thinking that it has + found a device and this stops my Intel EtherExpress card + from working. + + + Set the hints + hint.mcd.0.disabled="1" and + hint.mcd.1.disabled="1" + in the third stage boot loader to disable the probing + of the mcd0 and + mcd1 devices. Generally speaking, + you should only leave the devices that you will be using + enabled in your kernel. + + + + + The system finds my &man.ed.4; network card, but I + keep getting device timeout errors. + + + Your card is probably on a different IRQ from what is + specified in the /boot/device.hints file. The ed driver does + not use the `soft' configuration by default (values entered + using EZSETUP in DOS), but it will use the software + configuration if you specify -1 in the hints + for the interface. + + Either move the jumper on the card to a hard + configuration setting (altering the kernel settings if + necessary), or specify the IRQ as -1 + by setting the hint hint.ed.0.irq="-1" + This will tell the kernel to + use the soft configuration. + + Another possibility is that your card is at IRQ 9, + which is shared by IRQ 2 and frequently a cause of problems + (especially when you have a VGA card using IRQ 2!). You + should not use IRQ 2 or 9 if at all possible. + + + + + I booted the install floppy on my IBM ThinkPad (tm) + laptop, and the keyboard is all messed up. + + + Older IBM laptops use a non-standard keyboard + controller, so you must tell the keyboard driver (atkbd0) to + go into a special mode which works on the ThinkPads. Set the + hint hint.atkbd.0.flags="4" and it should work + fine. + + + + + My system can not find my Intel EtherExpress 16 card. + + + You must set your Intel EtherExpress 16 card to be + memory mapped at address 0xD0000, and set the amount of + mapped memory to 32K using the Intel supplied + softset.exe program. + + + + + When installing on an EISA HP Netserver, my on-board + AIC-7xxx SCSI controller isn't detected. + + + This is a known problem, and will hopefully be fixed + in the future. In order to get your system installed at + all, set the hint hw.eisa_slots="12" in the + third stage loader. + + + + + I have a Panasonic AL-N1 or Rios Chandler Pentium + machine and I find that the system hangs before ever getting + into the installation now. + + + Your machine doesn't like the new + i586_copyout and + i586_copyin code for some reason. To + disable this, set the hint hint.npx.0.flags="1" + + + + + I have this CMD640 IDE controller that is said to be + broken. + + + &os; does not support this controller. + + + + + On a Compaq Aero notebook, I get the message No + floppy devices found! Please check ... when trying to + install from floppy. + + + With Compaq being always a little different from other + systems, they do not announce their floppy drive in the CMOS + RAM of an Aero notebook. Therefore, the floppy disk driver + assumes there is no drive configured. Set the hint + hint.fdc.0.flags="1" + This pretends the existence of the first floppy drive (as a + 1.44 MB drive) to the driver without asking the CMOS at + all. + + + + + When installing on a Dell Poweredge XE, Dell + proprietary RAID controller DSA (Dell SCSI Array) isn't + recognized. + + + Configure the DSA to use AHA-1540 emulation using EISA + configuration utility. After that &os; detects the DSA + as an Adaptec AHA-1540 SCSI controller, with irq 11 and port + 340. Under emulation mode system will use DSA RAID disks, + but you cannot use DSA-specific features such as watching + RAID health. + + + + + I have an IBM EtherJet PCI card, it is detected by the + &man.fxp.4; driver correctly, but the lights on the card don't + come on and it doesn't connect to the network. + + + We don't understand why this happens. Neither do IBM + (we asked them). The card is a standard Intel EtherExpress + Pro/100 with an IBM label on it, and these cards normally + work just fine. You may see these symptoms only in some IBM + Netfinity servers. The only solution is to install a + different Ethernet adapter. + + + + + When I configure the network during installation on an + IBM Netfinity 3500, the system freezes. + + + There is a problem with the onboard Ethernet in the + Netfinity 3500 which we have not been able to identify at + this time. It may be related to the SMP features of the + system being misconfigured. You will have to install + another Ethernet adapter and avoid attempting to configure + the onboard adapter at any time. + + + + + When I install onto a drive managed by a Mylex PCI + RAID controller, the system fails to boot (eg. with a + read error message). + + + There is a bug in the Mylex driver which results in it + ignoring the 8GB geometry mode setting in the + BIOS. Use the 2GB mode instead. + + + + +