Re: Sun Fire V210 NIC's don't work
On 11/19/2012 04:28 PM, Richard Mortimer wrote:
On 19/11/2012 15:46, Kaya Saman wrote:
On 11/19/2012 03:36 PM, Richard Mortimer wrote:
So as I suspected eth0 and eth1 are the ports labelled net0 and net2
Did you try connecting the cable to those ports and testing. From what
I've see and what others have said I suspect that will just work.
I've connected cables to eth0 and eth1 or NICs 0 and 1. In addition I
tried NIC 2 but because Debian doesn't show the card itself I wasn't
able to get any connectivity.
I think you may be getting confused here. eth0 and eth1 are just
arbitrary names that are assigned to the devices and they do not
correspond to the names printed on the V210 chassis.
In your case eth0 looks to be NET0 and eth1 is NET2.
Well, I thought with the Backport I would have more luck but
unfortunately even kernel 3.2 is causing issues:
# dmesg | grep tg3
[ 41.528377] tg3.c:v3.121 (November 2, 2011)
[ 42.096605] tg3 0000:00:02.0: vpd r/w failed. This is likely a
firmware bug on this device. Contact the card vendor for a firmware
update.sym0: No NVRAM, ID 7, Fast-80, LVD, parity checking
[ 42.249670] tg3 0000:00:02.0: vpd r/w failed. This is likely a
firmware bug on this device. Contact the card vendor for a firmware update.
[ 42.305863] tg3 0000:00:02.0: vpd r/w failed. This is likely a
firmware bug on this device. Contact the card vendor for a firmware update.
[ 42.308810] tg3 0000:00:02.0: eth0: Tigon3 [partno(none) rev 2100]
(PCI:66MHz:64-bit) MAC address 00:14:4f:5d:1e:7e
[ 42.446140] tg3 0000:00:02.0: eth0: attached PHY is 5704
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
[ 42.575463] tg3 0000:00:02.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0]
ASF[0] TSOcap[1]
[ 42.679542] tg3 0000:00:02.0: eth0: dma_rwctrl[763f0000] dma_mask[32-bit]
[ 43.278806] tg3 0000:00:02.1: BAR 2: can't reserve [mem
0x7f700000000-0x7f70000ffff]
[ 43.380653] tg3 0000:00:02.1: Cannot obtain PCI resources, aborting
[ 43.741325] tg3: probe of 0000:00:02.1 failed with error -16
[ 44.072115] tg3 0003:00:02.0: vpd r/w failed. This is likely a
firmware bug on this device. Contact the card vendor for a firmware update.
[ 44.129861] tg3 0003:00:02.0: vpd r/w failed. This is likely a
firmware bug on this device. Contact the card vendor for a firmware update.
[ 44.559842] tg3 0003:00:02.0: vpd r/w failed. This is likely a
firmware bug on this device. Contact the card vendor for a firmware update.
[ 44.562363] tg3 0003:00:02.0: eth1: Tigon3 [partno(none) rev 2100]
(PCI:66MHz:64-bit) MAC address 00:14:4f:5d:1e:80
[ 44.699696] tg3 0003:00:02.0: eth1: attached PHY is 5704
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
[ 44.829020] tg3 0003:00:02.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0]
ASF[0] TSOcap[1]
[ 44.933095] tg3 0003:00:02.0: eth1: dma_rwctrl[763f0000] dma_mask[32-bit]
[ 45.125173] tg3 0003:00:02.1: BAR 2: can't reserve [mem
0x7c700000000-0x7c70000ffff]
[ 45.227044] tg3 0003:00:02.1: Cannot obtain PCI resources, aborting
[ 45.317544] tg3: probe of 0003:00:02.1 failed with error -16
[ 57.680406] tg3 0000:00:02.0: eth0: No firmware running
[ 59.335720] tg3 0000:00:02.0: eth0: Link is up at 100 Mbps, full duplex
[ 59.422695] tg3 0000:00:02.0: eth0: Flow control is off for TX and
off for RX
uname -a
3.2.0-0.bpo.4-sparc64-smp #1 SMP Debian 3.2.32-1~bpo60+1 sparc64 GNU/Linux
[...]
From what I have seen you are using squeeze with kernel 2.6.32. I
believe that there is a backport of 3.2.x available so it might be
worth trying that to see if it is already fixed there.
http://packages.debian.org/search?suite=all&arch=sparc&searchon=names&keywords=linux-image
It wou
ld also be useful if you could report a bug into the Debian tracking
system.
Doesn't look like it's fixed yet :-( Will post bug!
Regards
Richard
Regards,
Kaya
Reply to: