diff options
author | scottl <scottl@FreeBSD.org> | 2002-12-08 17:24:38 +0000 |
---|---|---|
committer | scottl <scottl@FreeBSD.org> | 2002-12-08 17:24:38 +0000 |
commit | 269e7fc862e919598a24b8bf01789b8c49d43e3c (patch) | |
tree | 6687b743d777b257dd51306f0939085155a22c14 /release | |
parent | a7482ae294664d142373a8b5ad6022c247d63528 (diff) | |
download | FreeBSD-src-269e7fc862e919598a24b8bf01789b8c49d43e3c.zip FreeBSD-src-269e7fc862e919598a24b8bf01789b8c49d43e3c.tar.gz |
Add FAQ entries on dealing with ACPI issues and enabling the ISA drivers
that were recently disabled.
There still are several references to the now-gone userconfig; these need to
be fixed before 5.0-RELEASE.
Approved by: re (rwatson)
Diffstat (limited to 'release')
-rw-r--r-- | release/doc/en_US.ISO8859-1/installation/common/trouble.sgml | 44 |
1 files changed, 44 insertions, 0 deletions
diff --git a/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml b/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml index 527cb8a..8862cf8 100644 --- a/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml +++ b/release/doc/en_US.ISO8859-1/installation/common/trouble.sgml @@ -34,6 +34,50 @@ <qandaset arch="i386"> <qandaentry> <question> + <para>My system hangs while probing hardware during boot, or it + behaves strangely during install.</para> + </question> + <answer> + <para>&os; 5.0 and above makes extensive use of the system ACPI + service on the i386 platform 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 unsetting the <quote>acpi_load</quote> + variable in the third stage boot loader:</para> + + <screen>unset acpi_loader</screen> + + <para>This is reset each time the system is booted, so it might be + necessary to set it permanently in the file + <filename>/boot/loader.conf</filename>. More inforation about the + boot loader can be found in the FreeBSD Handbook.</para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para>My legacy ISA device used to be recognized in previous versions + of &os;, but now it's not. What happened?</para> + </question> + <answer> + <para>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 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:</para> + + <screen>unset hint.foo.0.disabled</screen> + + <para>where <quote>foo</quote> is the name of the driver to re-enable. + This can be set permanently by editing the file + <filename>/boot/device.hints</filename> and removing the appropriate + <quote>disabled</quote> entry.</para> + </answer> + </qandaentry> + <qandaentry> + <question> <para>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:</para> |