HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- tg3 driver on DL145 G2 = only 1 NIC
Operating System - Linux
1833472
Members
2903
Online
110052
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2006 02:20 AM
12-19-2006 02:20 AM
Hello. I'm only able to use one of the two onboard Gig-eth NICs on this machine with Debian etch or Ubuntu Dapper. (2.6.18 and 2.6.15 respectively) yet both are detected and shown by dmesg.
The NIC marked as '2' on the back of the machine becomes eth0, whilst 'eth1' seems to vanish into the ether (if you'll excuse the pun).
tg3.c:v3.65 (August 07, 2006)
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 16
GSI 18 sharing vector 0xE1 and IRQ 18
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNK1] -> GSI 16 (level, high) -> IRQ 225
PCI: Setting latency timer of device 0000:02:00.0 to 64
eth0: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:17:08:92:37:6f
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 19
GSI 19 sharing vector 0xE9 and IRQ 19
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNK4] -> GSI 19 (level, high) -> IRQ 233
PCI: Setting latency timer of device 0000:03:00.0 to 64
eth1: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:17:08:92:37:6e
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[76180000] dma_mask[64-bit]
hash:~# mii-tool eth0
eth0: negotiated 100baseTx-FD flow-control, link ok
hash:~# mii-tool eth1
SIOCGMIIPHY on 'eth1' failed: No such device
hash:~# ifconfig eth0 | head -1
eth0 Link encap:Ethernet HWaddr 00:17:08:92:37:6F
hash:~# ifconfig eth1 | head -1
eth1: error fetching interface information: Device not found
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)
02:00.0 0200: 14e4:1659 (rev 11)
03:00.0 0200: 14e4:1659 (rev 11)
Same behaviour with tg3 v3.66 directly from
http://www.broadcom.com/docs/driver_download/570x/linux-3.66d.zip
Help!
The NIC marked as '2' on the back of the machine becomes eth0, whilst 'eth1' seems to vanish into the ether (if you'll excuse the pun).
tg3.c:v3.65 (August 07, 2006)
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 16
GSI 18 sharing vector 0xE1 and IRQ 18
ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNK1] -> GSI 16 (level, high) -> IRQ 225
PCI: Setting latency timer of device 0000:02:00.0 to 64
eth0: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:17:08:92:37:6f
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth0: dma_rwctrl[76180000] dma_mask[64-bit]
ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 19
GSI 19 sharing vector 0xE9 and IRQ 19
ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [LNK4] -> GSI 19 (level, high) -> IRQ 233
PCI: Setting latency timer of device 0000:03:00.0 to 64
eth1: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:17:08:92:37:6e
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[1]
eth1: dma_rwctrl[76180000] dma_mask[64-bit]
hash:~# mii-tool eth0
eth0: negotiated 100baseTx-FD flow-control, link ok
hash:~# mii-tool eth1
SIOCGMIIPHY on 'eth1' failed: No such device
hash:~# ifconfig eth0 | head -1
eth0 Link encap:Ethernet HWaddr 00:17:08:92:37:6F
hash:~# ifconfig eth1 | head -1
eth1: error fetching interface information: Device not found
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)
02:00.0 0200: 14e4:1659 (rev 11)
03:00.0 0200: 14e4:1659 (rev 11)
Same behaviour with tg3 v3.66 directly from
http://www.broadcom.com/docs/driver_download/570x/linux-3.66d.zip
Help!
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2006 04:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2006 06:42 AM
12-19-2006 06:42 AM
Re: tg3 driver on DL145 G2 = only 1 NIC
What a great tip :)
It has turned up that 'eth1' is actually called 'eth1_rename' - how dumb! :/ At least it gives me a new term to search Google for =)
Thanks for the input! :)
It has turned up that 'eth1' is actually called 'eth1_rename' - how dumb! :/ At least it gives me a new term to search Google for =)
Thanks for the input! :)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP