network driver not loaded for PCI ID 8086:10be

[komputes]

Intel Montevina has an Ethernet port which can't be detected. Debian installer notifies the user when installing. and lspci will show the following:

00:19.0 Ethernet controller: Intel Corporation Unknown device 10be (rev 02)

My educated guess is that the kernel cannot recognize this hardware and does not know what driver to assign to it.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, it would be helpful to know which particular kernel version you noticed this bug with and the numeric id for the PCI device. You can find these two things out via 'uname -a' and 'lspci -vvnn'. Thanks in advance.

[Harrison Bergeron (drey-bigney)]

I've come across this same issue, and have discovered the following:

The device is an Intel 82567 Gigabit network card, which should be supported by the e1000e driver. However, as of 7/10/08, the most recent version, e1000e-0.4.1.7, does not support this device. I created the following patch to add support for this device - It works, but is not very clean; It would be better to add a #define for the device in e1000_hw.h, but I'm not sure what the "correct" device name is (ie, E1000_DEV_ID_???):

--- e1000e-0.4.1.7/src/netdev.c.orig 2008-06-23 10:27:33.000000000 -0600
+++ e1000e-0.4.1.7/src/netdev.c 2008-07-05 12:25:30.000000000 -0600
@@ -5550,6 +5550,7 @@ static struct pci_device_id e1000e_pci_t
   { PCI_VDEVICE(INTEL, E1000_DEV_ID_ICH9_IGP_M), board_ich9lan },
   { PCI_VDEVICE(INTEL, E1000_DEV_ID_ICH9_IGP_M_AMT), board_ich9lan },
   { PCI_VDEVICE(INTEL, E1000_DEV_ID_ICH9_IGP_M_V), board_ich9lan },
+ { PCI_VDEVICE(INTEL, 0x10BE), board_ich9lan },

   { PCI_VDEVICE(INTEL, E1000_DEV_ID_ICH10_R_BM_LM), board_ich9lan },
   { PCI_VDEVICE(INTEL, E1000_DEV_ID_ICH10_R_BM_LF), board_ich9lan },

[Dana Goyette (danagoyette)]

Here's a note that may be relevant: Intel's document, "Intel® 82567 Gigabit Ethernet
Controller Specification Update and
Sighting Information," ( http://download.intel.com/design/network/specupdt/82567_su.pdf ) states the following:

3. 82567-LM Device ID for Montevina Platform
   Changed from 10BE to 10F5.
   Description: The Montevina 82567-LM Device ID (10BE) was incorrectly
                included with in-box drivers that are installed as part of Windows*
                Vista* Service Pack 1. Since support for this device was not fully
                developed for the in-box driver, the driver does not load correctly
                and presents the user with an error [Code 10 – driver could not
                start the device]. To prevent the user from having the Code 10
                error, the Device ID was changed to 10F5.
                For complete functionality with the new Device ID, the following
                are required to be updated to the following versions:
• Device Driver: Mount Angel 1
• NVM image: Revision 1.83 released in the 82567 SVK version
  1.6
• IBA version: Released in Mount Angel 1
• Tools: 82567 SVK version 1.6

It's possible, and likely, that the e1000e driver currently contains only the new device ID; for compatibility reasons, it does seem like a good idea to add a listing for the old device ID, to ensure it works on non-updated (as in BIOS update) systems.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Leann Ogasawara (leannogasawara)]

Hi All,

There is a serious bug which may affect some people subscribed to this report so I wanted to pass along the information. Due to an unresolved bug in the e1000e driver in the 2.6.27 Linux kernel, this driver/kernel should not be used on Intel ethernet hardware supported by the e1000e driver (Intel GigE). Doing so may render your network hardware permanently inoperable.

Older Intel ethernet hardware which uses the e1000 driver is not affected by this; however, some hardware which used the e1000 driver in previous Ubuntu releases, such as hardware that uses a PCI Express bus, has been moved from e1000 to e1000e in the latest kernel releases. If in doubt, do not use this driver/kernel and subscribe to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263555 to be notified when the bug is fixed.

Thanks.

[Ralph Janke (txwikinger)]

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

[Brian Murray (brian-murray)]

Looking at the modules.pcimap for 2.6.27-7-generic the e1000e driver should be used for this hardware now. It would be great to get confirmation though.

[Tim Gardner (timg-tpi)]

That PCI ID appeared by about 2.6.27-6.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.