Bug#512546: Same problem on Dell Optiplex 760 with Intel Corporation 82567LM-3 Gigabit Network Connection [8086:10de] (rev 02)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Perrier wrote:
> The only option could be adding something to an errata file.
That would very be nice.
While researching this problem a bit more, I found that support for the
Intel 82567LM-3 NIC was added in kernel 2.6.28:
commit f4187b56e1f8a05dd110875d5094b21b51ebd79b
Author: Bruce Allan <bruce.w.allan@intel.com>
Date: Tue Aug 26 18:36:50 2008 -0700
e1000e: add support for 82567LM-3 and 82567LF-3 (ICH10D) parts
Add support for new LOM devices on the latest generation ICHx
platforms.
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.28
This kernel is not even in unstable yet, so I think support for this
hardware will have to wait till Lenny 'N' Half at least?
In Ubuntu support for these ICH10 NICs was added to kernel 2.6.27-6.9:
[ Tim Gardner ]
* Add support in e1000e for a couple of ICH10 PCI IDs
* Enable CONFIG_INPUT_PCSPKR=m
- LP: #275453
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/275453/comments/3
Apparently they merged some changes from the e1000e driver from SourceForge:
+ /* Even those these are ICH10 devices, the ICH9 setup (which really
+ * uses ICH8) works fine. Just drop this patch when it collides with
+ * upstream. I ripped this from the SourceForge e1000e "0.4.1.7" driver.
+ */
+#define E1000_DEV_ID_ICH10_D_BM_LM 0x10DE
+#define E1000_DEV_ID_ICH10_D_BM_LF 0x10DF
+ { PCI_VDEVICE(INTEL, E1000_DEV_ID_ICH10_D_BM_LM), board_ich9lan },
+ { PCI_VDEVICE(INTEL, E1000_DEV_ID_ICH10_D_BM_LF), board_ich9lan },
+
http://launchpadlibrarian.net/18283516/linux_2.6.27-5.8_2.6.27-6.9.diff.gz
Using the Intel drivers from SourceForge may be an option for Lenny
users with recent Intel ICH10 NICs.
Good luck with the release this weekend!
Regards,
Bas
- --
GnuPG: 0x77A975AD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkmTQ/oACgkQRWRRA3epda1QIACfWf2zc1W3PInsZASRDPumX1Qk
mygAoJj/l34Yykl2peG2Gi3N+GyDP5mm
=JvwV
-----END PGP SIGNATURE-----
Reply to: