Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#512546: Same problem on Dell Optiplex 760 with Intel Corporation 82567LM-3 Gigabit Network Connection [8086:10de] (rev 02)

282 views
Skip to first unread message

Sebastiaan Couwenberg

unread,
Feb 11, 2009, 6:50:10 AM2/11/09
to
Today I encountered this issue on a Dell Optiplex 760 while trying to
setup my new workstation at work.

Both the Etch and Etch 'N' Half D-I, which I initially tried, fail to
detect the network card. The Lenny D-I RC2 and the daily build of
2009-02-09 also fail to detect the network card. Manually selecting the
e1000e driver also fails. On Ubuntu 8.10 the NIC is detected correctly.

lspci -kvv output:

lspci -kvv: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset
DRAM Controller [8086:2e10] (rev 03)
lspci -kvv: Kernel driver in use: agpgart-intel
lspci -kvv: Kernel modules: intel-agp
lspci -kvv: 00:01.0 PCI bridge [0604]: Intel Corporation 4 Series Chipset
PCI Express Root Port [8086:2e11] (rev 03)
lspci -kvv: Kernel driver in use: pcieport-driver
lspci -kvv: Kernel modules: shpchp
lspci -kvv: 00:02.0 VGA compatible controller [0300]: Intel Corporation 4
Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03)
lspci -kvv: 00:02.1 Display controller [0380]: Intel Corporation 4 Series
Chipset Integrated Graphics Controller [8086:2e13] (rev 03)
lspci -kvv: 00:03.0 Communication controller [0780]: Intel Corporation 4
Series Chipset HECI Controller [8086:2e14] (rev 03)
lspci -kvv: 00:03.2 IDE interface [0101]: Intel Corporation 4 Series
Chipset PT IDER Controller [8086:2e16] (rev 03)
lspci -kvv: 00:03.3 Serial controller [0700]: Intel Corporation 4 Series
Chipset Serial KT Controller [8086:2e17] (rev 03)
lspci -kvv: Kernel driver in use: serial
lspci -kvv: 00:19.0 Ethernet controller [0200]: Intel Corporation
82567LM-3 Gigabit Network Connection [8086:10de] (rev 02)
lspci -kvv: Kernel driver in use: e1000e
lspci -kvv: Kernel modules: e1000e
lspci -kvv: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #4 [8086:3a67] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #5 [8086:3a68] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #6 [8086:3a69] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB2 EHCI Controller #2 [8086:3a6c] (rev 02)
lspci -kvv: Kernel driver in use: ehci_hcd
lspci -kvv: Kernel modules: ehci-hcd
lspci -kvv: 00:1b.0 Audio device [0403]: Intel Corporation 82801JD/DO
(ICH10 Family) HD Audio Controller [8086:3a6e] (rev 02)
lspci -kvv: Kernel driver in use: HDA Intel
lspci -kvv: Kernel modules: snd-hda-intel
lspci -kvv: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JD/DO (ICH10
Family) PCI Express Port 1 [8086:3a70] (rev 02)
lspci -kvv: Kernel driver in use: pcieport-driver
lspci -kvv: Kernel modules: shpchp
lspci -kvv: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801JD/DO (ICH10
Family) PCI Express Port 2 [8086:3a72] (rev 02)
lspci -kvv: Kernel driver in use: pcieport-driver
lspci -kvv: Kernel modules: shpchp
lspci -kvv: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #1 [8086:3a64] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #2 [8086:3a65] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB UHCI Controller #3 [8086:3a66] (rev 02)
lspci -kvv: Kernel driver in use: uhci_hcd
lspci -kvv: Kernel modules: uhci-hcd
lspci -kvv: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801JD/DO
(ICH10 Family) USB2 EHCI Controller #1 [8086:3a6a] (rev 02)
lspci -kvv: Kernel driver in use: ehci_hcd
lspci -kvv: Kernel modules: ehci-hcd
lspci -kvv: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge
[8086:244e] (rev a2)
lspci -kvv: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801JD (ICH10D)
LPC Interface Controller [8086:3a1a] (rev 02)
lspci -kvv: 00:1f.2 SATA controller [0106]: Intel Corporation 82801JD/DO
(ICH10 Family) SATA AHCI Controller [8086:3a02] (rev 02)
lspci -kvv: Kernel driver in use: ahci
lspci -kvv: Kernel modules: ahci
lspci -kvv: 00:1f.3 SMBus [0c05]: Intel Corporation 82801JD/DO (ICH10
Family) SMBus Controller [8086:3a60] (rev 02)
lspci -kvv: Kernel modules: i2c-i801

lspci -s 00:19 -vvv:

00:19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network
Connection (rev 02)
Subsystem: Dell Device 027f
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 219
Region 0: Memory at fe6e0000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at fe6d9000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at ecc0 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e
Kernel modules: e1000e

Hopefully the e1000e driver in D-I can be fixed before the official Lenny
release so I can reinstall my workstation using that. Or an addition to
the release notes documenting this issue if it cannot be fixed before the
official release in the coming weekend.

Kind regards,

Bas


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Christian Perrier

unread,
Feb 11, 2009, 1:40:11 PM2/11/09
to
Quoting Sebastiaan Couwenberg (seba...@xs4all.nl):

> Hopefully the e1000e driver in D-I can be fixed before the official Lenny
> release so I can reinstall my workstation using that. Or an addition to
> the release notes documenting this issue if it cannot be fixed before the
> official release in the coming weekend.


I'm afraid that none of these is an option.

Fix D-I: too late...much too late
Add an item to the release notes: too late, they're frozen.

The only option could be adding something to an errata file.


signature.asc

Sebastiaan Couwenberg

unread,
Feb 11, 2009, 4:50:08 PM2/11/09
to
-----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....@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-----

Christian Perrier

unread,
Feb 12, 2009, 3:40:08 AM2/12/09
to
Quoting Sebastiaan Couwenberg (seba...@xs4all.nl):

> 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?

Such improved support is exactly the purpose of Lenny'n'half, yes.

Really sad that the new line of Dell Optiplex desktops will not be
supported out-of-the-box by lenny. I think we can blame the damn habit
of those HW manufacturers to change their product line every 6 months.:-(

> 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:

This is their responsibility. I personnally think that such backports
of kernel N+1 into kernal N add more mess in the kernel land than
solving problems, but apparently some people think differently.

We indeed don't have much to do with that bug report.

We could reassign it to the kernel with "please support <foo>" but we
already know this should be closed when the kernel team uploads
2.6.28. So, reassigning it to the kernel just adds more hassle to the
kernel team: think about closing that BR when uploading
2.6.28....without much benefit.

Any other opinions before I close the bug report?


signature.asc

Holger Levsen

unread,
Feb 12, 2009, 4:20:12 AM2/12/09
to
reassign 512546 linux-2.6
thanks

On Donnerstag, 12. Februar 2009, Christian Perrier wrote:
> > 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?
> Such improved support is exactly the purpose of Lenny'n'half, yes.

I don't think so, AFAIK missing PCI IDs are routinily added to kernel updates
also in pointreleases.

> > 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
> >

> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/275453/comments/3
> >

+ /* 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


regards,
Holger

signature.asc

Bastian Blank

unread,
Feb 12, 2009, 4:50:09 AM2/12/09
to
On Thu, Feb 12, 2009 at 10:16:09AM +0100, Holger Levsen wrote:
> I don't think so, AFAIK missing PCI IDs are routinily added to kernel updates
> also in pointreleases.

Yes they are. But you have not shown the upstream commit ids.

Bastian

--
No problem is insoluble.
-- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4


--
To UNSUBSCRIBE, email to debian-bo...@lists.debian.org

Bastian Blank

unread,
Feb 12, 2009, 5:00:16 AM2/12/09
to
On Thu, Feb 12, 2009 at 10:49:14AM +0100, Bastian Blank wrote:
> On Thu, Feb 12, 2009 at 10:16:09AM +0100, Holger Levsen wrote:
> > I don't think so, AFAIK missing PCI IDs are routinily added to kernel updates
> > also in pointreleases.
> Yes they are. But you have not shown the upstream commit ids.

The upstream commit to add this IDs and generic ICH10 support is
f4187b56e1f8a05dd110875d5094b21b51ebd79b.

As there are explicit differences in the init for ICH8/9 and ICH10
devices, I don't consider the hacked addition of ID with reuse of
ICH9-init as safe for now.

Bastian

--
I'm a soldier, not a diplomat. I can only tell the truth.
-- Kirk, "Errand of Mercy", stardate 3198.9

Otavio Salvador

unread,
Feb 13, 2009, 10:50:08 AM2/13/09
to
Bastian Blank <wa...@debian.org> writes:

> On Thu, Feb 12, 2009 at 10:49:14AM +0100, Bastian Blank wrote:
>> On Thu, Feb 12, 2009 at 10:16:09AM +0100, Holger Levsen wrote:
>> > I don't think so, AFAIK missing PCI IDs are routinily added to kernel updates
>> > also in pointreleases.
>> Yes they are. But you have not shown the upstream commit ids.
>
> The upstream commit to add this IDs and generic ICH10 support is
> f4187b56e1f8a05dd110875d5094b21b51ebd79b.
>
> As there are explicit differences in the init for ICH8/9 and ICH10
> devices, I don't consider the hacked addition of ID with reuse of

Did you looked how different and how difficult would be to backport
them?

--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: ota...@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."

0 new messages