Hi. I came across this bug report after I locked myself out of a new Dell PE 1950 III machine by upgrading from etch to lenny (for getting openvz and drbd in one kernel without much hacking).
For me it was enough to install firmware-bnx2 and reboot. On suspicion that it helps I attach some details anyway: The versions of the packages (that seem relevant to me) are: firmware-bnx2 0.13 linux-image-2.6.26-1-openvz-amd64 2.6.26-8 lspci identifies the cards as "03:00.0 0200: 14e4:164c (rev 12)" resp.: 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) I believe the firmware gets loaded at least once, this is from dmesg: [ 1.540613] Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.7.5 (April 29, 2008) [ 1.540613] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 1.540613] firmware: requesting bnx2-06-4.0.5.fw ... [ 1.618800] eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 16, node addr 00:1e:c9:b9:c6:5a [ 1.618800] ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 1.618800] firmware: requesting bnx2-06-4.0.5.fw ... [ 12.865463] bnx2: eth0: using MSI ... [ 15.118883] bnx2: eth1 NIC Copper Link is Up, 100 Mbps full duplex, receive & transmit flow control ON [ 15.119030] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 15.920613] bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON [ 15.922157] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Even the MAC address based renaming by udev works (according to some posts I ran over somewhere, due to some Dell related problem somehow kernels from 2.6.19-something on detects the two cards in exactly the opposite order compared to former kernels): [ 1.626793] udev: renamed network interface eth1 to eth0 [ 1.667732] scsi 0:0:32:0: Enclosure DP BACKPLANE 1.05 PQ: 0 ANSI: 5 [ 1.676673] udev: renamed network interface eth0_rename to eth1 [ 1.681846] scsi 0:2:0:0: Direct-Access DELL PERC 6/i 1.21 PQ: 0 ANSI: 5 Regards, Christoph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
