From 7e62bd286bb7539e24e837f973c4e4db7da6dbbf Mon Sep 17 00:00:00 2001 From: GNU Hurd wiki engine Date: Fri, 21 Sep 2007 18:37:05 +0000 Subject: web commit by steevithak: fixed typos --- microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'microkernel') diff --git a/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn b/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn index cedccae6..27052bad 100644 --- a/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn +++ b/microkernel/mach/gnumach/hardwarecompatibilitylist.mdwn @@ -68,5 +68,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 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. +* 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. -- cgit v1.2.3