Hi Khanh, Emil has some suggestions, but in addition can you try booting the kernel with pci=bios, and then if that doesn't work use pci=biosirq
The other interesting boot option might be acpi=off, and acpismp=force I believe what you're basically seeing is a bios compatibility problem with the 2.4 kernel. > message log like "Unable to establish link!!!". Looking into the This message is always printed by the debug code as the device is coming up, because the init code is programmed to not wait for link. We expect that after doing ifconfig ethX up you would see more messages about link if interrupts were working. -----Original Message----- From: Nguyen, Khanh D (IS) [mailto:khanh.d.ngu...@ngc.com] Sent: Thursday, May 28, 2009 4:29 PM To: Tantilov, Emil S; e1000-de...@lists.sf.net Cc: Yu, Feng-Ger (IS); Stabile, John S (IS); DaCosta, Ted; Muller, Bill (IS); Pongmanopap, Tony (IS) Subject: Re: [E1000-devel] e1000e problem with Intel 82574L PCI-e controller Emil, Please see the attachments for your requested info. The interface name for Intel 82574L is eth1. FYI, we tested the same computer with the same BIOS on 2.6.9-78 and confirmed the chipset worked with e1000e driver. Thanks, Khanh -----Original Message----- From: Tantilov, Emil S [mailto:emil.s.tanti...@intel.com] Sent: Thursday, May 28, 2009 3:03 PM To: Nguyen, Khanh D (IS); e1000-de...@lists.sf.net Cc: Yu, Feng-Ger (IS); Stabile, John S (IS); DaCosta, Ted; Muller, Bill (IS); Pongmanopap, Tony (IS) Subject: RE: [E1000-devel] e1000e problem with Intel 82574L PCI-e controller Nguyen, Khanh D (IS) wrote: > Hi, > > I tried to use e1000e-0.5.18.3 driver (with the DEBUG on and no NAPI) > for my Intel PCI-e 82574L controller with 2.4.21-50 kernel. The > driver seemed to detect the controller, however it gave name "Intel > Corporation: Unknown device 10d3" to controller. This is normal when using new device. The driver will not update the bradning strings in pci.ids unless it is installed via rpm. > The interface seemed to be up with the e1000e driver, however, there > was no traffic in/out that interface. There was a error message in > message log like "Unable to establish link!!!". Looking into the > code, it indicated that call > e1000e_phy_has_link_generic() always failed. BTW, I also tried the > driver with 2.4.37-1 kernel and it did not seem to work as well. > Really appreciate if you could help to resolve the issue. I tested with 2.4.21-50 kernel and 82574L device and was not able to reproduce this issue. Link issues are generally caused by interrupt problems. Could you please provide the following information: 1. cat /proc/interrupts (after loading the driver and ifup) 2. dmesg 3. ethtool -t ethX 4. lspci -vvv Also - we usually recommend to check for BIOS updates for your system if possible. Thanks, Emil ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
