Hi, On 16/09/11 at 15:44 +0000, Ronciak, John wrote: > Frederik, Lucas, > > Are both of you using Debian as the base OS install? I know you are > changing kernels but I'm wondering what the base install OS is. I > agree that the D# state is most likely what the cause of the device > not being seen by the system but what's causing the system to have the > NIC in the D3 state.
Indeed, it seems that we are both running Debian (and Debian-provided kernels). > Also, both of you have the exact same Dell laptop right? No, I have a E4300, while Frederik has an E6400 (according to https://lkml.org/lkml/2011/9/9/212). Same generation, different models. Another data point: I've got a friend using E4300 (same laptop as mine), running Debian with 3.0.0-1-amd64 kernel. His network works fine. One difference is that he is running with i386 userland (but amd64 kernel), while I am running plain amd64. > Is there a BIOS setting in about how the NIC is suspended or put to > sleep? The newer kernels may be doing something with the setting > where the older kernels didn't care. Can you guys please check? I already went through BIOS options looking for likely suspects, but did not find anything obvious related to NIC or power management. Lucas ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
