NIC 82545EM not recognized by Ubuntu Server 32 or 64bit

Bug #145503 reported by Nick Barcet on 2007-09-27
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
linux-source-2.6.22 (Ubuntu)
Colin Watson

Bug Description

Installing Ubuntu Server Gutsy B1 candidate 32 ou 64 under wmware, the NIC is not recognized by the server.

Can't copy the lspci output dure to the lack of network access :-(, but the NIC is reported as :
Intel Corporation 82545 Gigabit Ethernet Controller (Copper) (Rev 01)
subsystem: VMWare Inc Unknown device 0750

Not sure I have reported this in the right place though....

William F Pearson (wfpearson) wrote :

I can confirm this bug on an install of Gutsy Beta on VMware server 1.0.4. I can post any and all configuration files and outputs necessary to troubleshoot.

William F Pearson (wfpearson) wrote :

From my VMX configuration

# First network interface card
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.connectionType = "bridged"
ethernet0.addressType = "generated"
ethernet0.generatedAddressOffset = "0"

From lspci -vvnn
console screenshot attached

From lsmod (on boot, with no changes after installation)
The proper module is loaded for the NIC, but the devices does not appear in ifconfig

Colin Watson (cjwatson) wrote :

Nicolas, could you run 'lspci -vvnn' and extract the vendor and device numbers? For example, in the following output:

09:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5755M Gigabit Ethernet PCI Express [14e4:1673] (rev 02)

... we would need the "14e4:1673" bit.

Changed in linux-restricted-modules-2.6.22:
assignee: nobody → kamion
status: New → Incomplete
Colin Watson (cjwatson) wrote :

Actually, never mind that; William's attachment is sufficient there.

Could somebody please attach /var/log/syslog from the installer on a system suffering from this problem? You can extract it by using the "Save debug logs" item from the installer's main menu; you may need to attach an emulated USB stick or something.

Nick Barcet (nijaba) wrote :

Please find enclosed the syslog file requested.
Note that at this point, the card is correctly detected and configured.

Colin Watson (cjwatson) wrote :

This log appears to show the device being detected and configured correctly. We need a log of it failing.

Colin Watson (cjwatson) wrote :

11:39 <nijaba> cjwatson: regarding the network card detection in vmware, problem is that the card is detected fine during installation, but after first reboot not anymore. What do you need ?

This indicates that this is a duplicate of bug 145382.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers