I’ve been attempting to get the 10G interfaces working on my DoubleShot. I’ve tried Ubuntu 16.04.3 LTS from the software page, as well as Buildroot – both from the software page and by building my own from the buildroot source – however none of it works.
I get no link regardless if I try using the RJ45 ports or the SFP cages. If I plug in an SFP module into the SFP cage, a little orange light on the RJ45 port comes on. However in software on the board, using ifconfig or ethtool, it always shows that it has a link, even if nothing is plugged in.
So to summarise:
RJ45 10G doesn’t work, no link, no physical indication of anything reacting to being plugged in, no additional LEDs turn on, and no link flapping in software
SFP cages react to me plugging in an SFP+ module or SFP+ copper cable by an orange LED lighting up on the corresponding RJ45 connector belonging to that pair (eth1 -> SFP+/RJ45, eth0 -> SFP+/RJ45), but no link is actually established. I’ve tried plugging the other end into switches and directly into servers, still no link.
The software does react to something being plugged into the SFP cages when running Buildroot by printing out the detected module model, but again, no link.
What am I doing wrong?
I can’t see a way to edit posts but wanted to add for clarification:
All interfaces have been brought up in software, using for example ifconfig eth0 up
I have the same issue with my recently received DoubleShot. I have tried a couple of “standard” network configurations, the only only port I get up and running find is the 1GbE port. I really wanted this board because of the 2 x 10GbE copper ports. I could not find good instructions on how they were supposed to work..
I would be curious if anyone got them up and running and would be sharing their configuration.
Yep, eth2 works just fine, but eth0 and eth1 will not link at all
I do believe I got eth3 (up to 2.5Gbps) to link at 1 Gbps via a regular SFP module, but I’d have to check whether that was mainline kernel or not
I’d be great if someone responded with a bit more information because the information we have from Marvell/Solidrun hasn’t been enough to get them to work
I found that with ifconfig eth0 and ifconfig eth1 I am able to activate the 10GbE copper NICs. I have only connected eth1 with a cat7 cable.
cat /sys/class/net/eth1/operstate would then also report “up”
root@macchiatobin-node-1:~# ethtool eth1
Settings for eth1:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Link detected: yes
What I do find then is that dhclient eth1 doesn’t ever finish and if you cancel the operation; eth1 inet isn’t configured
eth1 Link encap:Ethernet HWaddr 00:51:82:11:22:01
inet6 addr: fe80::251:82ff:fe11:2201/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 B) TX bytes:2700 (2.7 KB)
I captured the packets during the dhclient eth1 call. It looks a lot different compared to dealing with eth2, it received an IP from the same dhcp server within seconds.
“1”,”0.000000″,”0.0.0.0″,”255.255.255.255″,”DHCP”,”342″,”DHCP Discover – Transaction ID 0x2a43b635″
“2”,”3.227463″,”0.0.0.0″,”255.255.255.255″,”DHCP”,”342″,”DHCP Discover – Transaction ID 0x2a43b635″
“3”,”9.930143″,”0.0.0.0″,”255.255.255.255″,”DHCP”,”342″,”DHCP Discover – Transaction ID 0x2a43b635″
“4”,”19.028635″,”0.0.0.0″,”255.255.255.255″,”DHCP”,”342″,”DHCP Discover – Transaction ID 0x2a43b635″
“5”,”33.800305″,”0.0.0.0″,”255.255.255.255″,”DHCP”,”342″,”DHCP Discover – Transaction ID 0x2a43b635″
“6”,”47.784562″,”0.0.0.0″,”255.255.255.255″,”DHCP”,”342″,”DHCP Discover – Transaction ID 0x2a43b635″
“7”,”60.478413″,”0.0.0.0″,”255.255.255.255″,”DHCP”,”342″,”DHCP Discover – Transaction ID 0x2a43b635″
Linux macchiatobin-node-1 4.4.52-armada-17.10.3-g6adee55 #6 SMP PREEMPT Tue Feb
Are you able to confirm that you actually got a link on the other end, and not only that the interface is reporting link?
My interfaces report that they have a link all the time, despite not having one. I suspect it might be the way they’re physically wired for us to be able to do SFP/Copper
My Switch XS716E is reporting that the cables are ok. But you are correct, on the switch I do not see any LED blinking indicating that a link was established.
This is really annoying! How long have been trying to make this work?
Yep, that’s the behaviour I see here
I’ve had a lot of other projects to take care of, but on and off since I got the board, which was in February
Edit: My bad! The November date was for a different board, since beginning of February for this one
I have called the US office, and was asked to open a support case, as the US office is only doing sales, which I just did. I have also forwarded the link to this conversation to them. I keep you posted.
Answer from support, we cannot really help you unless you buy support package 5 hours for $450..
You must be logged in to reply to this topic.
Technical specification tables can not be displayed on mobile. Please view on desktop