![]() | ||||||||||
Messages in this thread |
>> When trying to update the kernel from 2.4.25 to 2.6.3 I run >> into a probelm: >> While the driver for the onboard Intel E1000 network adapter >> loads OK, it >> doesn't seem to find an interrupt for the interface - ifconfig shows: >> eth0 Link encap:Ethernet HWaddr 00:0E:A6:2D:7A:64 >> BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> Base address:0x9000 Memory:fc000000-fc020000 >> Board is an Asus PC-DL, Intel 875P Chipset, one Xeon 2.8Ghz >> CPU, Onboard >> e1000 Network interface. Any idea how I can get the onboard >> NIC to work? >full output of /var/log/dmesg || dmesg after bootup might help. Some more information: * Update to 2.6.4-rc1 doesn't help, same situation as before. * 2.4.25 finds/uses int 18 * Binary search shows that the problem first appears with 2.6.2-bk1; 2.6.2 works OK. Further search shows that it's the e1000 driver update from 5.2.20 to 5.2.30.1 that breaks things for me. copying the older driver into a newer kernel works. Hmm, changelog states what looks like a possible candidate: * o Use pdev->irq rather than netdev->irq in preparation for MSI support. Final information: Backing out the pdev->irq <-> netdev->irq changes gives me ifconfig output with the correct interrupt listed; unfortunately, ifconfig eth0 up still locks the machine, so that doesn't seem to be the only problem. Bye, Martin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 13:01 [from the cache] ©2003-2008 | ||||||||||