Re: Sun Fire V210 NIC's don't work
On 11/14/2012 01:24 PM, Frans van Berckel wrote:
On Wed, 2012-11-14 at 12:47 +0000, Kaya Saman wrote:
Hi Frans,
previously I got the firmware directly from the site above and simply
did a wget to put it into the /lib/firmware directory.
As of now I did what Patrick suggested and ran: apt-get install
firmware-linux-nonfree
It still didn't work :-(
[ 43.836916] tg3 0000:00:02.0: eth0: Tigon3 [partno(none) rev 2100]
(PCI:66MHz:64-bit) MAC address 00:14:4f:5d:1e:7e
[ 43.974266] tg3 0000:00:02.0: eth0: attached PHY is 5704
(10/100/1000Base-T Ethernet) (WireSpeed[1])
[ 44.094448] tg3 0000:00:02.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0]
ASF[0] TSOcap[1]
[ 44.198525] tg3 0000:00:02.0: eth0: dma_rwctrl[763f0000] dma_mask[32-bit]
[ 45.138092] tg3 0003:00:02.0: eth1: Tigon3 [partno(none) rev 2100]
(PCI:66MHz:64-bit) MAC address 00:14:4f:5d:1e:80
[ 45.275418] tg3 0003:00:02.0: eth1: attached PHY is 5704
(10/100/1000Base-T Ethernet) (WireSpeed[1])
[ 45.395593] tg3 0003:00:02.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0]
ASF[0] TSOcap[1]
[ 45.499671] tg3 0003:00:02.0: eth1: dma_rwctrl[763f0000] dma_mask[32-bit]
[ 83.749175] tg3 0000:00:02.0: eth0: No firmware running
[ 83.866559] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 85.411107] tg3 0000:00:02.0: eth0: Link is up at 100 Mbps, full duplex
[ 85.498042] tg3 0000:00:02.0: eth0: Flow control is off for TX and
off for RX
[ 85.593597] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 91.991628] tg3 0003:00:02.0: eth1: No firmware running
[ 92.102114] ADDRCONF(NETDEV_UP): eth1: link is not ready
Here is requested output:
# ls -l /lib/firmware/tigon
total 16
-rw-r--r-- 1 root root 2668 Sep 19 2011 tg3.bin
-rw-r--r-- 1 root root 3884 Sep 19 2011 tg3_tso5.bin
-rw-r--r-- 1 root root 7004 Sep 19 2011 tg3_tso.bin
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:4f:5d:1e:7e
inet addr:192.168.1.116 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6504 errors:0 dropped:0 overruns:0 frame:0
TX packets:3567 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:461831 (451.0 KiB) TX bytes:274816 (268.3 KiB)
Interrupt:6
eth1 Link encap:Ethernet HWaddr 00:14:4f:5d:1e:80
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:31
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:124 errors:0 dropped:0 overruns:0 frame:0
TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10162 (9.9 KiB) TX bytes:10162 (9.9 KiB)
uname -a shows:
2.6.32-5-sparc64 #1 Sun Sep 23 10:01:20 UTC 2012 sparc64 GNU/Linux
Hi Kaya,
That's clear. For me, just to be sure, what does these two do?
# ifconfig eth1 192.168.2.116 up
# ping 192.168.2.116
I am getting icmp echo responses.
I rejigged the interface to sit inside a new vlan:
eth1 Link encap:Ethernet HWaddr 00:14:4f:5d:1e:80
inet addr:192.168.140.2 Bcast:192.168.140.3 Mask:255.255.255.252
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:31
ping 192.168.140.2
PING 192.168.140.2 (192.168.140.2) 56(84) bytes of data.
64 bytes from 192.168.140.2: icmp_req=1 ttl=64 time=0.057 ms
64 bytes from 192.168.140.2: icmp_req=2 ttl=64 time=0.036 ms
64 bytes from 192.168.140.2: icmp_req=3 ttl=64 time=0.040 ms
ping 192.168.140.1
PING 192.168.140.1 (192.168.140.1) 56(84) bytes of data.
From 192.168.140.2 icmp_seq=1 Destination Host Unreachable
From 192.168.140.2 icmp_seq=2 Destination Host Unreachable
while similar config on eth0 works fine.....
Check your settings with # ifconfig again. And does # update-initramfs
also complains about the missing firmware files, as asked?
update-initramfs -u
update-initramfs: Generating /boot/initrd.img-2.6.32-5-sparc64
Thanks,
Frans van Berckel
Regards,
Kaya
Reply to: