diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml index e52c57c5e0..34a401e5b6 100644 --- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml @@ -4064,29 +4064,6 @@ Please press any key to reboot. 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 @@ -4189,23 +4166,6 @@ Please press any key to reboot. - - - 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 @@ -4232,137 +4192,6 @@ Please press any key to reboot. 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. - -