1 files changed, 6 insertions, 1 deletions
diff --git a/microkernel/mach/gnumach/hardware_compatibility_list.mdwn b/microkernel/mach/gnumach/hardware_compatibility_list.mdwn
index 32e712c9..460c8aba 100644
--- a/microkernel/mach/gnumach/hardware_compatibility_list.mdwn
+++ b/microkernel/mach/gnumach/hardware_compatibility_list.mdwn
@@ -96,6 +96,11 @@ on the hardware devices they support.
 [[hurd/DDE]] provides more up-to-date network device drivers, based on Linux
 2.6.29 code, running as user-space processes.
 
+# BIOS32 Service Directory
+
+GNU Mach is not yet compatible with mmconfig, and PCI access requires the presence of the BIOS32 Service Directory.
+You can check for its presence by running a Linux 32 bits kernel with the kernel parameter "pci=bios" and checking if PCI devices work.
+
 # User Success Reports
 
 These boards are known to work. Gnumach/Hurd has been installed and run on these board successfully. 
@@ -115,7 +120,7 @@ These boards are known to work. Gnumach/Hurd has been installed and run on these
 
 Some people couldn't get these hardware combinations to work with Hurd.
 
-Note: The Debian GNU/Hurd installer actually runs on Linux, so it (almost) always works. The critical bit is booting after installation.
+The present Debian GNU/Hurd installer itself runs on Hurd, so failure on the installer may mean that the hardware is uncompatible with Hurd.
 
 * ASUS P5A motherboard and AMD K6-2 333MHz CPU - doesn't boot
 * ASUS P2B-LS motherboard with an Intel PII-MMX 400 MHz CPU - this board had a defective onboard NIC (that could not be disable in BIOS) and working 3COM Etherlink III NIC in a PCI bus slot. This combination worked with GNU/Linux. The 3COM NIC is known to work with the Hurd. However, while gnumach/Hurd will boot on this system, it is confused by the defective onboard NIC and unable to use the 3COM NIC. Attempting to start networking generates a continous stream of eth0 and eth1 reset messages on the console that renders the system unusable.