tg3 driver 1.28 does not recognize the NetXtreme BCM57766 chip

Bug #1182868 reported by Smurphy
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Joseph Salisbury

Bug Description

Since 13.04 came out officially, the NetXtreme BCM57766 gigabit ethernet chip is not recognized by the tg3 driver.
Have to recompile the kernel and apply a simple patch over and over again.
A fix exists - which consists adding the vendor identification, but it has not made it into kernel 3.8.0-19 neither 3.8.0-21

+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57766)},
+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57782)},
+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57786)},

Has been discuessed on askubuntu.com

http://askubuntu.com/questions/288454/ubuntu-13-04-on-mac-mini-6-2-ethernet-port-broadcom-netxtreme-bcm57766-not-detec

Thx for including this 3liner into the next kernel update.
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: smurphy 2218 F.... pulseaudio
 /dev/snd/controlC0: smurphy 2218 F.... pulseaudio
 /dev/snd/pcmC0D0p: smurphy 2218 F...m pulseaudio
DistroRelease: Ubuntu 13.04
MachineType: Apple Inc. Macmini6,2
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-21-generic root=UUID=b1fa0e2f-1cac-41b4-b0a6-407c240030a3 ro elevator=deadline noapic vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-21-generic N/A
 linux-backports-modules-3.8.0-21-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk lpadmin mertin plugdev sambashare sudo uucp vboxusers
dmi.bios.date: 11/16/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM61.88Z.0106.B03.1211161202
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F65AE981FFA204ED
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini6,2
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F65AE981FFA204ED
dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED:
dmi.product.name: Macmini6,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Smurphy (smurphy-linux) wrote :

Here the entire patch snippet:

--- linux-source-3.8.0/drivers/net/ethernet/broadcom/tg3.c 2013-05-02 04:35:43.000000000 +1200
+++ tg3-3.128x/src/tg3.c 2013-05-06 10:30:07.542039601 +1200
@@ -330,6 +330,9 @@
    {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_5719)},
    {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_5720)},
    {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57762)},
+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57766)},
+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57782)},
+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57786)},
    {PCI_DEVICE(PCI_VENDOR_ID_SYSKONNECT, PCI_DEVICE_ID_SYSKONNECT_9DXX)},
    {PCI_DEVICE(PCI_VENDOR_ID_SYSKONNECT, PCI_DEVICE_ID_SYSKONNECT_9MXX)},
    {PCI_DEVICE(PCI_VENDOR_ID_ALTIMA, PCI_DEVICE_ID_ALTIMA_AC1000)},

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1182868

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Smurphy (smurphy-linux) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected raring
description: updated
Revision history for this message
Smurphy (smurphy-linux) wrote : BootDmesg.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : CRDA.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : HookError_cloud_archive.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : IwConfig.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : Lspci.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : Lsusb.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : ProcEnviron.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : ProcModules.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : PulseList.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : RfKill.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : UdevDb.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : UdevLog.txt

apport information

Revision history for this message
Smurphy (smurphy-linux) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu):
status: Incomplete → In Progress
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This looks like a duplicate of bug 1162665. That bug was fixed in Ubuntu-3.8.0-20.31. However, it sounds like there may be a regression in 3.8.0-21.32.

From the bug description, it sounds like you tested 3.8.0-19 and 3.8.0-21. Would it be possible for you to test 3.8.0-20? If you confirm this bug does not exist there, I can see what introduced this regression in 3.8.0-21.

I don't see any changes to the tg3 driver in Raring since the fix for bug 1162665, which is the following commit:
3baed5a - tg3: Add 57766 device support

This may require a bisect.

tags: added: regression-update
Revision history for this message
Smurphy (smurphy-linux) wrote :

If you tell me where to get 3.8.0-20 directly, I can.
It is not in the repositories. However, I definitely confirm that the driver of 3.8.0-21 does not recognize the NetXtreme BCM57766 gigabit ethernet chip on my mac mini.

Revision history for this message
Smurphy (smurphy-linux) wrote :

Just checked the 3.8.0-22 source, and according to the linux_3.8.0-22.33.diff.gz file, the tg3.c is patched to support the 57766 chip.

--- linux-3.8.0.orig/drivers/net/ethernet/broadcom/tg3.c
+++ linux-3.8.0/drivers/net/ethernet/broadcom/tg3.c
@@ -330,6 +330,7 @@
        {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_5719)},
        {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_5720)},
        {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57762)},
+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57766)},
        {PCI_DEVICE(PCI_VENDOR_ID_SYSKONNECT, PCI_DEVICE_ID_SYSKONNECT_9DXX)},
        {PCI_DEVICE(PCI_VENDOR_ID_SYSKONNECT, PCI_DEVICE_ID_SYSKONNECT_9MXX)},
        {PCI_DEVICE(PCI_VENDOR_ID_ALTIMA, PCI_DEVICE_ID_ALTIMA_AC1000)},

Will confirm once I reboot the system.

Revision history for this message
Smurphy (smurphy-linux) wrote :

Confirmed - 3.8.0-22.33 boots and detects the 57766 chip out of the box. No recompile required.
Guess you can close this bug.
Thx.

Revision history for this message
James Cameron (quozl) wrote :

I upgraded from 3.8.0-20.31 to 3.8.0-22.33 on my Macmini6,1 and the ethernet device went away again as per #1162665, judging by my gkrellm on nodm display. USB also went away, preventing further easy diagnosis. Grub would not respond to a held down shift key.

I was able to boot from an external USB DVD drive with the Ubuntu 13.04 desktop amd64+mac image, chroot to the filesystem, apt-get remove the 3.8.0-22.33 kernel, update-grub, and reboot. Back to normal again.

I'm happy to try anything else. Let me know.

Revision history for this message
Smurphy (smurphy-linux) wrote :

The grub will not answer to an held down shift-key as the keyboard mode is changed.
You have to shutdown the mac mini, and restart it. warm-boot won't work.

Note that I am using the plain KUbuntu 13.04 image. Not the amd64+mac image.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

The patch mentioned in comment #22 was introduced in Ubuntu-3.8.0-20.31, so I'm not sure why there was an issue with -21.32 that was then resolved in -22.33:

commit 3baed5acfc8c0a35885782edb1fa16b44646bf71
Author: Matt Carlson <email address hidden>
Date: Thu Feb 14 14:27:51 2013 +0000

    tg3: Add 57766 device support.

Thanks for confirming the bug no longer exists. I'll mark as invalid for now.

Changed in linux (Ubuntu):
status: In Progress → Invalid
Revision history for this message
James Cameron (quozl) wrote :

Joseph, -22.33 did _not_ fix the problem for me.

Are there any further tests you would like me to make?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Smurphy, can you confirm whether or not this bug still exists in 3.8.0-22.33?

@James Cameron, if the bug is fixed for Smurphy, it would probably be best to open a new bug for you, so we can focus specifically on your system.

Revision history for this message
Smurphy (smurphy-linux) wrote :

I can confirm that I didn't have to compile the kernel/driver for it to recognize that network chip.
So yes - the OOB provided driver works for me - version 3.8.0-22.33 - see below.

smurphy@Pandora:~$ uname -a
Linux Pandora 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I am using the stock kernel from ubuntu.

smurphy@Pandora:~$ modinfo tg3
filename: /lib/modules/3.8.0-22-generic/kernel/drivers/net/ethernet/broadcom/tg3.ko
firmware: tigon/tg3_tso5.bin
firmware: tigon/tg3_tso.bin
firmware: tigon/tg3.bin
version: 3.128
license: GPL
description: Broadcom Tigon3 ethernet driver
author: David S. Miller (<email address hidden>) and Jeff Garzik (<email address hidden>)
srcversion: 6F1354F540E5DB7A8585AA7
...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@James Cameron, it's probably best to open a new bug, if you confirm all your versions match up from comment #30.

Revision history for this message
James Cameron (quozl) wrote :

Thanks Joseph. The module version and source version are identical (see below), but the kernel version is not ... because I am running the latest kernel that works for me. I will schedule downtime and carefully boot the new kernel, in order to avoid losing control of the system again. I would appreciate a pointer to a procedure for (a) opening a new kernel bug with no network connectivity, and (b) configuring grub to show a kernel selection menu.

esk:~$ uname -a
Linux esk 3.8.0-20-generic #31-Ubuntu SMP Mon May 6 17:03:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
esk:~$ /sbin/modinfo tg3
filename: /lib/modules/3.8.0-20-generic/kernel/drivers/net/ethernet/broadcom/tg3.ko
firmware: tigon/tg3_tso5.bin
firmware: tigon/tg3_tso.bin
firmware: tigon/tg3.bin
version: 3.128
license: GPL
description: Broadcom Tigon3 ethernet driver
author: David S. Miller (<email address hidden>) and Jeff Garzik (<email address hidden>)
srcversion: 6F1354F540E5DB7A8585AA7
...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

There is some documentation on GRUB[0], but basically you just need to comment out the following two lines in /etc/default/grub and then re-run 'sudo update-grub':
GRUB_HIDDEN_TIMEOUT=10
GRUB_HIDDEN_TIMEOUT_QUIET=false

There is also a wiki page[1] that describes how to file a bug without an Internet connection. Search for 'Filing bugs when off-line' on that page.

[0]https://help.ubuntu.com/community/Grub2
[1] https://help.ubuntu.com/community/ReportingBugs

Revision history for this message
pmeerw (pmeerw) wrote :

I have an Acer Aspire E1-572 which has a BCM57786 GE NIC

01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57786 Gigabit Ethernet PCIe (rev 01)
01:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card Reader (rev 01)
02:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)

the BCM57786 is not detected by Ubuntu 2013.10

adding the following devices to tg3.c
+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57766)},
+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57782)},
+ {PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, TG3PCI_DEVICE_TIGON3_57786)},
and building a custom tg3.ko fixes the problem and the NIC works

please apply above patch to the Ubuntu source tree, thanks!

Revision history for this message
pmeerw (pmeerw) wrote :

fix has been accepted upstream, see
http://patchwork.ozlabs.org/patch/276813/

Revision history for this message
Niklas Fischer (niklasfi) wrote :

Hi, we have just tried the fix proposed by pmeerw with an Acer Aspire E1-572 which accomodates a netxtreme BCM57786 chip. However after successfully compiling and installing a 3.11.6 kernel with the patch, we are still missing the ethernet device (does not show up in ip a s). Is this expected? What are the next steps we should take?

Revision history for this message
pmeerw (pmeerw) wrote :

Niklas, how do you know your self-compiled driver is actually loaded? I had an issue where the self-compiled driver was installed in /lib/modules/.../extra but not actually loaded by modprobe

have you tried insmod'ing your self-compiled .ko?
have to tried putting some printk()s in your self-compiled driver to see if it is actually loaded/executed and how far it gets? you can take this further to see where is actually fails...

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.