PCIe x4 to Single-Port 10G Ethernet Adapter - Setup Assistance

Hello!

I purchased a PCIe x4 to Single-Port 10G Ethernet Adapter AQC113 Chipset from the ZimaSpace website for my Zimaboard 2.0 (I finally retired the 1.0).

Is there anything I need to do from a software point of view to get it working? I see the lights are on where the ethernet cable is connected, but I’m not getting a connection when using the port on the adapter. Could this be driver related or it could be something silly I’m missing.

Thank you so much in advance!

You usually don’t need to install anything, but there are two common gotchas with the AQC113 on ZimaBoard 2.

What I believe is happening

ZimaOS is Buildroot-based, not a full desktop Linux. The AQC113 driver is present, but the interface does not auto-activate in some cases.

Things I suggest checking (quick and simple)

  1. Reboot once with the card installed
    Sounds obvious, but the NIC often only registers after a cold boot.
  2. Check if the interface exists
  • Go to Settings > Network
  • Look for a new interface like eth1 or enp*
  • If it’s there but inactive, enable DHCP manually
  1. Cable & switch compatibility
  • AQC113 is 10G / 5G / 2.5G / 1G, but:
    • Some switches need the port forced to auto-negotiation
    • Try a known-good Cat6a cable
    • Test against a 2.5G or 10G switch, not a basic 1G-only port
  1. Power & seating
  • I’ve seen this be something simple:
    • Reseat the card
    • Make sure the PCIe x4 adapter is fully locked in

What I think is not the issue

  • You normally do not need to install drivers
  • This is unlikely to be a faulty card if link lights are on
  • Not a ZimaBoard 2 hardware limitation (it supports this NIC)

If it still doesn’t come up

I suggest posting:

  • A screenshot of Settings > Network
  • Whether the interface appears at all
  • What switch/router you’re plugging into

Thank you for the detail reply!

I followed your directions and I do see a “eth1” in the Settings under Network.

When you say enable “DHCP” manually - I see settings for eth1-Ethernet. There is a “DHCP” and “Manual” toggle for “Configure iPv4” and “Configure iPv6”. Should I toggle it from “DCHP” to “Manual”.

If so, would you be able to assist/point me in the right direction on how to generate the below?

  • IP,
  • Subnet Mask,
  • Gateway Address
  • DNS

[Sorry I know I’m asking too much]

Thanks!
E

Not asking too much at all, that’s exactly what we’re here for
Happy to help, and you’re doing everything right so far.

Short answer (the important bit)

Do NOT switch from DHCP to Manual.
If your network has a router (which 99% do), leave IPv4 set to DHCP.

What you’re seeing there is normal.

Slightly longer explanation (plain English)

  • DHCP = your router automatically gives the NIC:
    • IP address
    • Subnet mask
    • Gateway
    • DNS
  • Manual = you must enter all of that yourself

Unless you specifically want a fixed/static IP, DHCP is the correct choice.

So for eth1:

  • Configure IPv4 > DHCP (leave it as-is)
  • Configure IPv6 > optional (can stay DHCP or Disabled, doesn’t matter for now)

When would you use “Manual”?

Only if:

  • You want the ZimaBoard to always have the same IP
  • Or you’re troubleshooting a very specific network issue

If you did go manual (not required), the values would usually come from your router, for example:

  • IP: 192.168.1.50
  • Subnet Mask: 255.255.255.0
  • Gateway: 192.168.1.1
  • DNS: 192.168.1.1 or 8.8.8.8

But again, you do not need this right now.

What I suggest you do next

  1. Leave IPv4 = DHCP
  2. Toggle eth1 OFF, wait 5 seconds, toggle it ON
  3. Give it ~10–20 seconds
  4. See if:
  • It shows an IP address
  • Network becomes reachable

If it still doesn’t pass traffic, tell us:

  • Does eth1 show an IP at all?
  • What speed does your switch support (1G / 2.5G / 10G)?
  • Are you plugging directly into a switch or router?
2 Likes

So it looks like:

eth0 (Ethernet) - DHCP [Some IP Address]
eth1 (Ethernet) - DHCP [No IP Address]

I can’t seem to find how to toggle it on and off (I’m in Settings → Network → Under “Connection”).

Thank you again!

What this shows is simple:
eth0 is working (it has an IP), and eth1 is detected but not completing network negotiation.

In ZimaOS this is usually not a driver or configuration issue. The AQC113 is supported, and leaving IPv4 on DHCP is correct.

I believe this is most likely related to cable or switch negotiation. With 10G NICs it’s common to see link lights but still get no IP if the port doesn’t negotiate cleanly.

I suggest:

  • Trying a Cat6a cable if available
  • Connecting eth1 to a 2.5G or 10G capable port
  • If your switch allows it, set the port to auto-negotiation or force 2.5G
  • Doing a full power-off (shutdown, unplug for 30 seconds, power back on)

ZimaOS doesn’t expose an on/off toggle for individual interfaces in the UI, so you’re not missing anything there.

If it still doesn’t pick up an IP, let us know what switch or router model you’re connected to, that usually points straight to the cause.

Hello!

I ended up upgrading my network switch to be 2.5gb ports + two SPF ports at 10gb.

I bought this adapter for the switch:

I also purchased a cable rated for the data transfer. I then connected the network switch to the 10gb adapter on Zima. The PCIe card shows a solid green light, but it still doesn’t seem to want to connect.

The solid green LED on the NIC usually means the card has power and detects a physical connection, but it does not guarantee that the link has successfully negotiated with the switch.

The next step is to check what the system itself sees for the interface.

Please SSH into the ZimaOS machine and run:

ip link

You should see interfaces such as:

eth0
eth1

(or possibly a different name depending on the NIC driver).

Then check the link status of the interface connected to the 10G adapter:

ethtool eth1

Look for these lines in the output:

Speed:
Duplex:
Link detected:

The key line is:

Link detected: yes

If it shows:

Link detected: no

then the NIC and the switch are not negotiating a usable link, even though the LED is on.

A few things to be aware of with SFP+ RJ45 modules:

  • Some switches do not support copper SFP+ modules, even if they physically fit.
  • Some SFP+ ports only support 1G or 10G, not 2.5G / 5G negotiation.
  • RJ45 SFP+ modules can run hot and occasionally have vendor compatibility issues with certain switches.

If possible, it would help to know:

  • The exact switch model
  • The output of:
ip link

and

ethtool eth1

Those outputs will usually show immediately whether this is a driver issue, link negotiation problem, or switch compatibility issue.