iPXE discussion forum - Sonnet Twin 10g TB2 Adapter

I have a Sonnet Twin 10g TB2 Adapter plugged in to a MacPro (late 2013) (trash can) via a thunder bolt connector. It is recognized by ipxe.efi as a Intel® x540t.
It recognizes linkup/link down, dhcp fails with "no configuration methods succeeded.
I am able to set a static IP address on the interface and open the interface.
But am not able to ping the interface after it is opened.

Has anyone gotten these to work with ipxe?

I Only need to able to set static IP's on to these devices.
snp.efi does not see the interfaces.

User's Guide.
http://www.sonnettech.com/support/downlo...10g_ug.pdf

(2018-10-18 23:33)ebruno Wrote: [ -> ]I have a Sonnet Twin 10g TB2 Adapter plugged in to a MacPro (late 2013) (trash can) via a thunder bolt connector. It is recognized by ipxe.efi as a Intel® x540t.
It recognizes linkup/link down, dhcp fails with "no configuration methods succeeded.
I am able to set a static IP address on the interface and open the interface.
But am not able to ping the interface after it is opened.

Has anyone gotten these to work with ipxe?

I Only need to able to set static IP's on to these devices.
snp.efi does not see the interfaces.

User's Guide.
http://www.sonnettech.com/support/downlo...10g_ug.pdf

I have been looking at the make files, it is not clear to me how to add just the Intel 540 drivers to the snp.efi build target. so the target would have snp and 540 only.
Any pointers would be appreciated.

The snp build uses SNP or NII interface which must be provided by the firmware, so you need to have that loaded from NIC ROM or elsewhere for snp to work.

In regards to having a combination of drivers in one build use snp--intel.efi, as described at for example http://ipxe.org/appnote/buildtargets

But it seems that what you need is a debug session for the specific NIC and it's use in iPXE with it's native drivers.
could you grab the pciid, for example with lspci -nn ?

3b:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01)
3b:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 [8086:1528] (rev 01)

ok so it uses the intelx driver.

First, is there any chance that you could test this nic without the thunderbolt in a normal PC?
Just to verify if this is a possible TB issue or not.
If that isn't possible I would start building with DEBUG=intelx and see if that gives any leads
If not then move on to building with DEBUG=intelx:3 instead.

I built the following command:
bin-x86_64-efi/snp--intelx.efi EMBED=${IPXE_SCRIPTDIR}/myscript.ipxe DEBUG=netdevice,ipv4

Once I open the interface and the do a ifstat i see:
[link:up TX:0 TXE:5 RX:0 RXE:0]
TXE 4x "Operation cancelled http://ipxe.org/0b086095)
TXE 1x "Network unreachable (http://ipxe.org/28086090)

I rebuilt with DEBUG=netdevice,ipv4
set net1/ip 192.168.20.50
I get a message stating it cannot send the gratuitous ARP NETDRV net1 transmission 0x6e14cb90 failed
if do an ifopen net1
NETDRV net1 opening
NETDRV net1 link is up
NETDRV net1 link is up

Note the ping from the remote system does not succeed.

I close the interface by entering ifclose net1
put the same settings on net2 (which is plugged in to the same netgear 5 port unmanaged switch) . I get the "cannot send the gratuitous ARP message". on net2

i enter ifopen net2
This a Broadcom chip using the NII driver the interface pings succeeds.

If I open the the interface first then set gateway, netmask and then IP I do not get the gratuitous ARP message or other error messages, but he interface still does not ping.
I rebuilt and included ping in the ipxe image.
When I attempt to ping the gateway from ipxe I get
I tried increasing the time out put no difference.
connection time out errors http://ipxe.org/4c1b2092

(2018-10-19 22:44)NiKiZe Wrote: [ -> ]ok so it uses the intelx driver.

First, is there any chance that you could test this nic without the thunderbolt in a normal PC?
Just to verify if this is a possible TB issue or not.
If that isn't possible I would start building with DEBUG=intelx and see if that gives any leads
If not then move on to building with DEBUG=intelx:3 instead.

The NIC is in an enclosure that only has thunderbolt connectivity to the enclosure.
I will do some more testing tomorrow with the debug options you suggested.

(2018-10-23 01:51)ebruno Wrote: [ -> ]
(2018-10-19 22:44)NiKiZe Wrote: [ -> ]ok so it uses the intelx driver.

First, is there any chance that you could test this nic without the thunderbolt in a normal PC?
Just to verify if this is a possible TB issue or not.
If that isn't possible I would start building with DEBUG=intelx and see if that gives any leads
If not then move on to building with DEBUG=intelx:3 instead.

The NIC is in an enclosure that only has thunderbolt connectivity to the enclosure.
I will do some more testing tomorrow with the debug options you suggested.

With intelx:3 set for the debug mode. on the NIC that is plugged in what is reported is:
When first loading:
INTEL 0x6ec07bb0 reset (ctrl 0000000)
INTEL 0x6ec07bb0 has autoloaded NAC address 00:30:09:0c:22:06 at 5400
INTEL 0x6ec07bb0 link status is 30000008
INTEL 0x6ecc86d0 has autoloaded NAC address 00:30:93:0c:22:07 at 0x05400
INTEL 0x6ecc86d0
issue dhcp

INTEL 0x6ec086d0 link status is 60000080

DHCP fails.
Using wireshark to monitor the subnet I never see a DHCP request on the wire.

if I try setting a static ip and do an ifopen net1
links status shows as 60000080
not able to ping interface
ifstat shows interface open, linkup, network unreachable.

This require some deeper investigation into what is going on in your case. - meaning reading datasheets and debugging the actual nic.
Which interfaces are on it 2xSFP+ ?

(2018-10-23 22:11)NiKiZe Wrote: [ -> ]This require some deeper investigation into what is going on in your case. - meaning reading datasheets and debugging the actual nic.
Which interfaces are on it 2xSFP+ ?

2 10GBASE-T Ports
Dual Copper RJ45.
Runs 10GB, 1GB and 100MB

Let me see what suggestions on areas to look at I can get from the vendor.

I am finally get back to this. I was able to build with gdbudp included. But I am missing something when attempting to build with debug symbols . I tried setting EXTRA_CFLAGS to -g and CFLAGS to -g but when open the the image with gdb I get the message

Reading symbols from bin-x86_64-efi/snp--intelx.efi.tmp...(no debugging symbols found)...done.

Any pointers on how to enable "-g" during compile.