Hi, On Wed, Sep 19, 2007 at 02:32:01PM -0500, R. Steven Rainwater wrote:
> The second box was an ASUS P2B-LS motherboard with an Intel PII-MMX > 400 MHz CPU. The Hurd installed and even booted but TCP/IP refused to > work. The problem was a defective built-in ethernet port on the P2B-LS > board. While Linux is okay using a secondary nic and ignoring the > broken built-in nic, the Hurd can't do it. It insisted on confusing > eth0 and eth1, generating endless error messages on the console, and > rendering both useless. I saw that in the IRC backlog, but didn't have a chance to reply... The secondary NIC should work just fine, if you disable the onboard one in the BIOS setup. I actually tested such a setup quite recently. Regarding the eth0/eth1 issue: On my system (Intel i815 chipset with onbard Intel NIC), I *always* get eth0 and eth1. (That's totally unrelated to a secondary NIC being present; it's some bug with the driver itself.) But it works nevertheless, if I use eth0 and ignore eth1. (Touching eth1 makes bad things happen...) -antrik- _______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
