Jesse/Emil, Just wonder if you have any news regarding to e1000e driver on our platform. BTW, we just test the driver e1000e with the same kernel 2.4.37-1 on laptop Compaq 8510p with Intel 82566MM chip and encounter similar problem. You mention that "Unknown device 10d3" problem is common because the driver will not update the branding strings in pci.ids unless it is installed via rpm. However we use the same method (just copy and load .o or .ko files and no rpms) to load module in 2.4 and 2.6, but on 2.6 kernel, the driver actually recognizes the name as "Intel 10/1000" where as on 2.4, it just says "Unknown device 10d3"? Any ideas?
Thanks, Khanh -----Original Message----- From: Nguyen, Khanh D (IS) Sent: Friday, May 29, 2009 3:06 PM To: 'Brandeburg, Jesse' Cc: Yu, Feng-Ger (IS); Stabile, John S (IS); DaCosta, Ted; Muller, Bill (IS); Pongmanopap, Tony (IS); Tantilov, Emil S; [email protected] Subject: RE: [E1000-devel] e1000e problem with Intel 82574L PCI-e controller Jesse, Please see attachment for the requested info. Really appreciate for your help. Khanh -----Original Message----- From: Brandeburg, Jesse [mailto:[email protected]] Sent: Friday, May 29, 2009 2:41 PM To: Nguyen, Khanh D (IS); Tantilov, Emil S; [email protected] 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 I was hoping you could try without noapic Once noapic didn't work I wouldn't have expected it to work with any other options either, sorry I wasn't more clear. As for the IRQ routing conflict, it is probably related to why your machine doesn't work in the first place. Can you send a full dmesg (dmesg.txt.gz) please, and output of ethtool -e ethX (ethtool.txt), as well? -----Original Message----- From: Nguyen, Khanh D (IS) [mailto:[email protected]] Sent: Friday, May 29, 2009 2:17 PM To: Brandeburg, Jesse; Tantilov, Emil S; [email protected] 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 Jesse and Emil, I tried your suggestions, unfortunately they all did not work. Just want to list out combinations that I tried. 1. noapic => did not work 2. noapic pci=bios => did not work, also caused the keyboard not detected 3. noapic pci=biosirq => did not work 3. noapic pci=biosirq apci=off => did not work 4. noapic pci=biosirq apci=off apcismp=off => did not work Looking into dmesg, I also found another error msg when loading module is " "IRQ routing conflict for 05:00.0, have irq 5, want irq 7" Any ideas how to fix this? Thanks, Khanh -----Original Message----- From: Brandeburg, Jesse [mailto:[email protected]] Sent: Friday, May 29, 2009 11:32 AM To: Nguyen, Khanh D (IS); Tantilov, Emil S; [email protected] 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 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:[email protected]] Sent: Thursday, May 28, 2009 4:29 PM To: Tantilov, Emil S; [email protected] 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:[email protected]] Sent: Thursday, May 28, 2009 3:03 PM To: Nguyen, Khanh D (IS); [email protected] 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 ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel
