Hi bhawver,
OK- i've got my model up and running and this driver does actually load on our E6410. The kernel versions for DS6.9SP3 and DS6.9SP4 are the same, so you shouldn't have an issue.
I've been asking around here the best way to troubleshoot, and the consensus here is to load up your Linux automation environment and do the following,
modprobe -l e1000e
This should list all the modules found with the name e1000e in the /lib/modules structure. There should be two drivers, one loaded in with bootdisk creator, and the native one included in the automation environment. You should therefore see following output,
/lib/modules/2.6.27.7/kernel/opt/bdc/e1000e.ko
/lib/modules/2.6.27.7/kernel/drivers/net/e1000e/e1000e.ko
If you don't see the bdc variant here, something is wrong. Try the process of adding the driver again. Next, to see what driver was actually loaded at boot time type,
dmseg | grep "e1000e"
and this should give you the output as follows,
e1000e : Intel(R) PRO/1000 Network Driver - 1.1.19 -NAPI
e1000e: Copyright 1999 - 2010 Intel Coorporation
e1000e: 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
e1000e: 0000:00:19.0: Setting latency timer to 64
e1000e: eth0 NIC link is up 100Mbps Full Duplex, Flow Control: None
e1000e: eth0 NIC link is up 100Mbps Full Duplex, Flow Control: None
Here you should explicitly see that the 1.1.19 driver has been loaded.
What do you get at your end? If you see nothing at all, i.e. no Intel drivers loaded as determined by lsmod, what do you get if you try to explicitly load the module using insmod e1000e?
Kind Regards,
Ian./