Support for Qnap 5Gbe USB adapter


Bruno

Recommended Posts

  • 2 months later...
On 2/14/2020 at 3:41 AM, mnemonicman said:

I too am curious if/when that adapter would be supported. It shows up as a device but no network interface is added.

Got an server with a Silverstone DS380 so that means mini-itx and very few if any has better than 1gbe.

So currently it does not work with Unraid? was considering to purchase it. Sound like a perfect upgrade on paper for ITX system which PCIe slot is occupied by controller card.

 

Hope Unraid will add support soon

  • Like 1
Link to comment
  • 3 months later...
  • 5 months later...
2 hours ago, jtbtroon said:

I'd like to bump this also. Support for the AQC111U drivers would be great for users like me who don't have any spare PCIe slots and are looking at USB Ethernet adapters.

Try the 6.9 beta, it has a newer kernel which I believe should have this driver as it landed in the kernel just after the intel/realtek 2.5G drivers (which are in the 6.9 beta).

Edited by tjb_altf4
Link to comment
  • 2 weeks later...

I tried with the Version 6.9.0-beta30 .

root@Tower:~# modinfo aqc111
modinfo: ERROR: Module aqc111 not found.

 

It does not work. AQC111 is not available.

Would be great to include it.

 

Sadly, i am also not able to pass it through to a Windows 10 VM.

(Device cannot be startet: Code 10)

Link to comment
  • 2 months later...
  • 2 months later...
  • 3 weeks later...
  • 3 weeks later...
  • 1 month later...
4 hours ago, ich777 said:

Try to do:



modprobe -v atlantic

 

 

Can somebody attach the Diagnostics to this thread (Tools -> Diagnostics -> Download -> drop the downloaded zip file here in the text box).

Hi @ich777 I think it may need # CONFIG_USB_NET_AQC111 is not set

Edited by SimonF
Link to comment
12 minutes ago, ich777 said:

On my server I have the atlantic drivers built with the Kernel, would be super nice to know which hardware ID's that those cards have. ;)

Controller: AQC111U
I/O: 1 x USB 3.2 Gen 1 Type-C; 1 x 5GbE/NBASE-T port
Operating temperature: -5 - 45°C (23°F - 113°F)
Package content: QNA- UC5G1T; 0.2M USB 3.2 Gen 1 Type-C to Type-A cable and installation guide
Port and cable: RJ-45

Note:
● Windows 10, 8.1, 8, 7 requires a driver. Requires the Marvell® AQtion AQC111U driver. Click here to download the driver.
● QNAP NAS: QTS 4.3.6 (or later) or QuTS hero h4.5.0 (or later) is required.
● QNAP has ended official support for MacOS and Linux since 2021/01. Users can download the Marvell® AQtion AQC111U driver from Marvell®’s official website. Click here to download the driver.

  • Like 1
Link to comment
  • 1 month later...
On 7/7/2021 at 1:23 PM, Golmak said:

I have tested on UnRaid 6.9.2 it is the same.

 

It shows up in System Devices but is not assigned as a network interface ...

 

Have a good day

ich777 has created a package for me and I have create a plugin to install that should appear in CA to install the module. I have not been able to test if it works with an adapter or if you can use with Unraid network settings.

 

image.png.27c26a4e579b53a4a10e9e2039baa167.png

Edited by SimonF
  • Like 3
Link to comment
On 8/22/2021 at 3:18 PM, SimonF said:

ich777 has created a package for me and I have create a plugin to install that should appear in CA to install the module. I have not been able to test if it works with an adapter or if you can use with Unraid network settings.

 

image.png.27c26a4e579b53a4a10e9e2039baa167.png

 

thanks for your works, but when i install this module in Unraid 6.9.2 , The OS add this Qnap AQC111 usb ethernet card, but in [ Interface Rules ] Coloum i can't see this usb ethernet card info, so i can't chanage eth0 to Qnap aqc usb ethernet card, which i want to replace the system original 1Gbps i350 nic to boot and for unraid main use. is there need to change /boot/config/network-rules.cfg to add this usb aqc111 card info?

Edited by gzelvis
Link to comment
1 hour ago, gzelvis said:

 

thanks for your works, but when i install this module in Unraid 6.9.2 , The OS add this Qnap AQC111 usb ethernet card, but in [ Interface Rules ] Coloum i can't see this usb ethernet card info, so i can't chanage eth0 to Qnap aqc usb ethernet card, which i want to replace the system original 1Gbps i350 nic to boot and for unraid main use. is there need to change /boot/config/network-rules.cfg to add this usb aqc111 card info?

what do you get from ifconfig.

Link to comment
19 hours ago, SimonF said:

what do you get from ifconfig.

 

root@HOMESERVER:~# ifconfig
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:9fff:fe03:8684  prefixlen 64  scopeid 0x20<link>
        ether 02:42:9f:03:86:84  txqueuelen 0  (Ethernet)
        RX packets 769736  bytes 503056618 (479.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 731398  bytes 568106147 (541.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.0.88  netmask 255.255.255.0  broadcast 0.0.0.0
        ether b4:7a:f1:a0:bb:c4  txqueuelen 2000  (Ethernet)
        RX packets 150754356  bytes 177547905334 (165.3 GiB)
        RX errors 0  dropped 4148724  overruns 0  frame 0
        TX packets 189578572  bytes 275264539550 (256.3 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0x87400000-874fffff  

eth3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fd27:f9d1:9a96:1:265e:beff:fe4e:d20  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::265e:beff:fe4e:d20  prefixlen 64  scopeid 0x20<link>
        ether 24:5e:be:4e:0d:20  txqueuelen 1000  (Ethernet)
        RX packets 167  bytes 40214 (39.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 35  bytes 7376 (7.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 293689  bytes 357824408 (341.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 293689  bytes 357824408 (341.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth2f7ce7d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::d8bd:a9ff:fe56:d8fb  prefixlen 64  scopeid 0x20<link>
        ether da:bd:a9:56:d8:fb  txqueuelen 0  (Ethernet)
        RX packets 260551  bytes 333788126 (318.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 377938  bytes 128551510 (122.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth4690b2c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::287f:c1ff:fed6:85ad  prefixlen 64  scopeid 0x20<link>
        ether 2a:7f:c1:d6:85:ad  txqueuelen 0  (Ethernet)
        RX packets 35817  bytes 10980138 (10.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1643  bytes 1377443 (1.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth83343a5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::64df:dbff:fe0b:7199  prefixlen 64  scopeid 0x20<link>
        ether 66:df:db:0b:71:99  txqueuelen 0  (Ethernet)
        RX packets 346240  bytes 135829660 (129.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 298284  bytes 352301682 (335.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth978f18c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::c82e:56ff:feaf:17d6  prefixlen 64  scopeid 0x20<link>
        ether ca:2e:56:af:17:d6  txqueuelen 0  (Ethernet)
        RX packets 5028  bytes 1589778 (1.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 40363  bytes 31394156 (29.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethbf14116: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::68d2:7dff:fe18:8b5  prefixlen 64  scopeid 0x20<link>
        ether 6a:d2:7d:18:08:b5  txqueuelen 0  (Ethernet)
        RX packets 87685  bytes 22856750 (21.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 118597  bytes 22230503 (21.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:47:39:b2  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

 

---------------------------------------------------

 

eth3 is the usb aqc111 usb ethernet card . and i found it will not auto get ipv4 adresss 

Link to comment

IOMMU group 3:[8086:a36d] 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 002: ID 0424:2660 Standard Microsystems Corp. Hub

Bus 002 Device 004: ID 1c04:0015 QNAP System Inc. QNAP QNA-UC5G1T USB to 5GbE Adapter

Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 003 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive

Link to comment
1 hour ago, gzelvis said:

if any more information u need, plz let me know。 eth3 can't be found in [Interface Rules]  so i cant chage unraid to use it as eth0 for main network use 

ScreenClip.png

Have you tried a reboot following install of the plugin?

 

I have one of these on the way.  So cant do my own testing at present. It may need a rule adding to udev rules as I think this only gets build at boot time.

 

root@computenode:/etc/udev/rules.d# cat 70-persistent-net.rules 

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="2c:f0:5d:d7:2a:11", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
--

# PCI device 0x15b3:0x1003 (mlx4_core)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:52:14:0e:b5:c1", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x15b3:0x1003 (mlx4_core)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="f4:52:14:0e:b5:c0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
root@computenode:/etc/udev/rules.d# 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.