Mike Leone on Thu, 8 Nov 2001 22:00:22 +0100 |
Wondering if anyone has seen this, or can help out .. I have an Intel EtherExpress Pro 100 NIC. I downloaded the sources for kernel 2.4.13; configured the eepro as a module, like always; compiled; installed. All worked fine. The NIC works fine in kernel 2.4.10 and below. However, when I booted into my new 2.4.13 kernel, it wouldn't initialize. I manually did an "ifdown eth0". Then did a "ifup eth0", figuring that I'll bring the interface up by hand. Here's the log snippet: Nov 8 00:46:40 minas-aran network: Setting network parameters: succeeded Nov 8 00:46:40 minas-aran ifup: Cannot send dump request: Connection refused Nov 8 00:46:40 minas-aran network: Bringing up interface lo: succeeded Nov 8 00:46:40 minas-aran ifup: Cannot send dump request: Connection refused Nov 8 00:46:42 minas-aran ifup: Cannot send dump request: Connection refused Nov 8 00:46:42 minas-aran ifup: Error adding address 192.168.100.40 for eth0. Nov 8 00:46:42 minas-aran ifup: Cannot send dump request: Connection refused Nov 8 00:46:42 minas-aran ifup: bind: Cannot assign requested address Nov 8 00:46:42 minas-aran ifup: Cannot send dump request: Connection refused Nov 8 00:46:42 minas-aran ifup: Cannot talk to rtnetlink: Connection refused Nov 8 00:46:43 minas-aran network: Bringing up interface eth0: succeeded Have no idea what "dump request" it's talking about, nor why it couldn't bind that address to my NIC. Anybody? The kernel does know that the NIC is there, because I saw this earlier in the boot sequence: kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savoch kernel: PCI: Found IRQ 3 for device 00:0a.0 kernel: eth0: Intel Corporation 82557 [Ethernet Pro 100], 00:90:27:BA:6F:DA, kernel: Board assembly 721383-007, Physical connectors present: RJ45 kernel: Primary interface chip i82555 PHY #1. kernel: General self-test: passed. kernel: Serial sub-system self-test: passed. kernel: Internal registers self-test: passed. kernel: ROM checksum self-test: passed (0x04f4518b). I did try compiling the eepro directly into the kernel (i.e., not as a module); same results. Had to boot back into 2.4.10. Thoughts, anyone? -- Goodbye youth, goodbye dreams, The good times and the friends I used to know. Goodbye freedom, hello fear, A brave new world has suddenly appeared. "Salvation Road", The Kinks ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|