summaryrefslogtreecommitdiff
path: root/microkernel/mach
diff options
context:
space:
mode:
authorGNU Hurd wiki engine <web-hurd@gnu.org>2007-09-20 16:23:21 +0000
committerGNU Hurd wiki engine <web-hurd@gnu.org>2007-09-20 16:23:21 +0000
commita10cd6d3d0446b84e0f306ffa47550387d217ef8 (patch)
treee741df5e6e14507d6df469b2e0a90e0c2d090c51 /microkernel/mach
parent121c11701c5fffccd3d020635375e1084b4c64c1 (diff)
web commit by steevithak
Diffstat (limited to 'microkernel/mach')
-rw-r--r--microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn b/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn
index f5f9fda5..b043b233 100644
--- a/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn
+++ b/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn
@@ -77,5 +77,5 @@ These boards are known to work. Gnumach/Hurd has been installed and run on these
These boards or hardware combination are known to fail with gnumach/Hurd.
* ASUS P5A motherboard and AMD K6-2 333MHz CPU - Debian GNU/Hurd will install but not boot on this board
-* ASUS P2B-LS motherboard with an Intel PII-MMX 400 MHz CPU - this board had a defective onboard NIC and working 3COM Etherlink III nic in a PCI bus slot. This combination worked with GNU/Linux. The 3COM NIC is know to work with the Hurd. However, while gnumach/Hurd will boot on this system, it is unable to ignore the defective onboard NIC and unable to use the 3COM NIC. Attempting to start networking generates continous streams of eth0 and eth1 reset messages on the console that render the system unusable.
+* ASUS P2B-LS motherboard with an Intel PII-MMX 400 MHz CPU - this board had a defective onboard NIC 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 streams of eth0 and eth1 reset messages on the console that renders the system unusable.