On 6/19/07, Wayne Topa <[EMAIL PROTECTED]> wrote:
Yuwen Dai([EMAIL PROTECTED]) is reported to have said: > Dear all, > > I have a Intel pro100 network card in my PC. The system loads kernel module > `e100' automatically when booting. But ifconfig eth0 up failed. If I > manually load `eepro100', ifconfig also failed. This is some output: > > # modprobe eepro100 > PCI: Enabling device 0000:02:02.0 (0110 -> 0113) > ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 185 > eth0: 0000:02:02.0, 00:0E:0C:5E:4B:06, IRQ 185. > Board assembly 741462-017, Physical connectors present: RJ45 > Primary interface chip i82555 PHY #1. > General self-test: passed. > Serial sub-system self-test: passed. > Internal registers self-test: passed. > ROM checksum self-test: passed (0x04f4518b). > If you try 'ifup eth1' or 2,3,4 and it comes up then
Hi Wayne, Yes. `ifconfig eth1' brings up the network. Take a look at
/etc/udev/rules.d/z25_persistent-net.rules: I had this occur on a laptop. My net_rules file had a bunch of eth lines and my eth1 cane up when I did 'ifup eth6". Removed all of the eth rules except eth0 and all was well again.
There's another rule with a different MAC address in this file. This reminds me that I once used another 3com NIC in the PC. So udev remembers this. Thank you very much! Best regards, Yuwen :-) HTH, YMMV, HAND :-)
Wayne -- | LINUX - Because a PC is a terrible thing to waste..on WinDoze |
