Quoting Jesse Brandeburg <[email protected]>:
On Fri, Oct 22, 2010 at 6:17 PM, <[email protected]> wrote:
Quoting "Brandeburg, Jesse" <[email protected]>:
On Thu, 21 Oct 2010, [email protected] wrote:
I am still having this issue but it seems to only be on x86_64. I used
a Knoppix disk to boot with and the card worked with no issues using a
32bit kernel. I downloaded the latest kernel from kernel.org and
compiled it and the issue returns using a 64bit kernel.
huh, that is pretty interesting. Does your machine have >=
4GB ram? Did
you ever try enabling the APIC with apic=force kernel boot option?
Yes it has 6GB of RAM. I have never tried apic=force as a boot option
I will try that. I thought the default was for apic to be enabled so I
have tried it with apic=no.
I have tried ignore_64bit_dma=1 and still get the same issue. I am
using modprobe ignore_64bit_dma=1 e1000, that is the correct way to
load it with that option? I have also tried TXDescriptorStep=4 along
I think the syntax is modprobe ./e1000.ko ignore_64bit_dma=1
of course only after make install
The dot slash in front results in a module not found. Is there a way
to see if the module was loaded with the option enabled? I looked at
modinfo e1000 and it doesn't show if a particular option is loaded.
I am right now trying to figure out how to get the dmesg.log from
knoppix whch seems to truncate it. Tushar has asked me for this so I
have been waiting to post back until I got it when I noticed your reply.
you might be able to boot the knoppix kernel with a kernel option to
increase the dmesg log buffer size (think its called log_buf_size ?).
Impossible, I can only use their options. The option I was looking for
turned out to be log_buf_len=262144 but I couldn't put that on the
boot line. I will burn a FC11 i386 cd and use that from now on.
While I'm trying to figure out the dmesg problem what else if anything
would you need, cat /proc/interrupts or any thing else?
cat /proc interrupts on the 32 bit kernel and the full dmesg (i know
you're working on it) you maybe just want to do dmesg > file.txt
I had to just do dmesg > file.txt as you suggested because of the
knoppic issue. It is not a full dmesg but it does show the e1000
module being loaded, I hope it's enough. If not, let me know and I
will burn a fc11 disk and try again.
The 64bit dma fix is precisely for the problem you're describing, also
the descriptor step workaround has been known to help in amd systems.
I was really hopeful. :)
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
