diff --git a/release/sysinstall/help/en_US.ISO8859-1/hardware.hlp b/release/sysinstall/help/en_US.ISO8859-1/hardware.hlp index 5119894eaf6f..5c3f3d06edcc 100644 --- a/release/sysinstall/help/en_US.ISO8859-1/hardware.hlp +++ b/release/sysinstall/help/en_US.ISO8859-1/hardware.hlp @@ -1,4 +1,4 @@ -Hardware Documentation Guide: $Id: hardware.hlp,v 1.8 1995/06/06 00:55:25 jkh Exp $ +Hardware Documentation Guide: $Id: hardware.hlp,v 1.9 1995/06/07 05:51:11 jkh Exp $ Table of Contents ----------------- @@ -371,4 +371,14 @@ A: This problem may occur in a system with a 3com 3c509 ethernet adaptor. at address 0x300 except the ep0 driver. On exit, your machine should successfully boot FreeBSD. + +Q: My system hangs during boot, right after the "fd0: [my floppy drive]" + line. + +A: This is not actually a hang, simply a very LONG "wcd0" probe that + often takes a long time to complete on certain systems (where there + usually _isn't_ a WD controller). Be patient, your system will boot! + To eliminate the problem, boot with the -c flag and eliminate the wdc0 + device, or compile a custom kernel. + [ Please add more hardware tips to this Q&A section! ] diff --git a/release/sysinstall/help/en_US.ISO_8859-1/hardware.hlp b/release/sysinstall/help/en_US.ISO_8859-1/hardware.hlp index 5119894eaf6f..5c3f3d06edcc 100644 --- a/release/sysinstall/help/en_US.ISO_8859-1/hardware.hlp +++ b/release/sysinstall/help/en_US.ISO_8859-1/hardware.hlp @@ -1,4 +1,4 @@ -Hardware Documentation Guide: $Id: hardware.hlp,v 1.8 1995/06/06 00:55:25 jkh Exp $ +Hardware Documentation Guide: $Id: hardware.hlp,v 1.9 1995/06/07 05:51:11 jkh Exp $ Table of Contents ----------------- @@ -371,4 +371,14 @@ A: This problem may occur in a system with a 3com 3c509 ethernet adaptor. at address 0x300 except the ep0 driver. On exit, your machine should successfully boot FreeBSD. + +Q: My system hangs during boot, right after the "fd0: [my floppy drive]" + line. + +A: This is not actually a hang, simply a very LONG "wcd0" probe that + often takes a long time to complete on certain systems (where there + usually _isn't_ a WD controller). Be patient, your system will boot! + To eliminate the problem, boot with the -c flag and eliminate the wdc0 + device, or compile a custom kernel. + [ Please add more hardware tips to this Q&A section! ]