Page 2 of 2

Re: Marvell AQtion (atlantic) NIC in F4-424 MAX not supporting GRO

Posted: 18 Nov 2024, 06:49
by awl29
bugacha wrote: 17 Nov 2024, 21:53 There is some discussion here with guys having same 0x0001 last 4th ID

https://www.station-drivers.com/index.p ... rt=30#2878
@bugacha, I am aware of all these discussions, and I fully second what you are saying.

Without an official statement/instructions from TerraMaster on how to update the NIC firmware, I will definitely NOT do so and warn everybody else to do it because of the huge danger to destroy the NIC and void your warranty.

But most likely, it would have a noticeably positive effect on the device's performance if TerraMaster would officially support to update the NIC's firmware and also update the NICs "atlantic" driver in the "6.1.58+" kernel to the latest code from Marvell (only available under NDA)...

The big question is: why do we still wait for an official reaction from TerraMaster's side? It's obvious that the brand new F424-MAX devices (and others) using the on-board Marvell AQtion (atlantic) NIC have been released with both an ancient firmware and a suboptimal driver.

So @TMLeeh, are you listening? What is TerraMaster's statement to us?

Re: Marvell AQtion (atlantic) NIC in F4-424 MAX not supporting GRO

Posted: 30 Nov 2024, 19:54
by awl29
Hallo @ Terra Master,
TMLeeh wrote: 02 Nov 2024, 11:25 Thank you for your feedback. We will address this issue to the product team.
are you willing to provide any reply to this topic? In case you continue to ignore me, I am considering to return the Device to Amazon/paid through Paypa and request my money back because TerraMaster - the seller - is not helpful at all to resolve important issues with the product.

So please finally reply to the following three clearly stated questions as first asked on Nov 1st:

(1) Are the issues mentioned in my Nov1st post - e.g. inability to support Generic Receive Offload (GRO) with current kernel/drivers - already known to TerraMaster Engineering/Support?
(2) What is your plan to address/fix them to get GRO working?
(3) Is it supported (i.e. will it keep my warranty intact) to boot into Windows from USB NVMe and update the NIC's firmware to the version above? If not, is there nay way to update the atlantic/Antigua firmware through TOS/Linux?

(Note that I am about to lose patience with TerraMaster Support/Engineering!)

Many thanks for listening/reading!
awl29

Re: Marvell AQtion (atlantic) NIC in F4-424 MAX not supporting GRO

Posted: 30 Nov 2024, 23:42
by crisisacting
If all you're doing is just posting to this thread, go contact technical support directly, not on this community forum.

Otherwise, cut your losses & return it (since you apparently still have that ability) if this currently unavailable feature is mission critical for your use case.

Re: Marvell AQtion (atlantic) NIC in F4-424 MAX not supporting GRO

Posted: 18 Jul 2025, 18:39
by MikeZhang
awl29 wrote: 30 Nov 2024, 19:54
Hi dear friend, sorry to make you wait long.

The following is our laboratory's verification conclusion on the GRO function of the F4-424 Max network interface:

1. The laboratory used the command

Code: Select all

ethtool -k eth0 | grep generic-receive-offload
to verify that the Linux kernel already supports the GRO function. It may be because the Marvell AQC113C network card chip hardware does not support this function, resulting in the failure to implement GRO function support.

2. The firmware can be updated to the latest version 1.5.42 in the following way, but after testing, it is confirmed that the new firmware still does not support the GRO function. But if you want to try by yourself, please check following method:

1. Download and decompress the firmware package. The compressed package download link is:
https://download2.terra-master.com/AQC113_FW_1.5.42.zip

Transfer the file to the NAS shared directory via the SMB protocol

2. Log in to the terminal and refer to the following link method:viewtopic.php?f=78&t=2350

3. Use the cd command to enter the SMB shared folder directory
Image

4. Run command

Code: Select all

 chmod 777 ./*
to give the files in the current folder read, write and execute permissions.
Image

5. Run command

Code: Select all

 ./listDevices
Image

6. The two devices 0000-02:00.0 and 0000-03:00.0 in the above figure are the devices that need to update the firmware. To update the firmware of 0000-02:00.0, excute command

Code: Select all

./flashBurn2 -d 0000-02:00.0 ./1.5.42.clx
. If you see Device burned and verified at the end, it means that the firmware of 0000-02:00.0 has been successfully updated. If you want to update 0000-03:00.0, run

Code: Select all

./flashBurn2 -d 0000-03:00.0 ./1.5.42.clx
.
Image

7. Check the firmware version by running

Code: Select all

./readstat2 -d 0000-02:00.0
. The MAC Bundle Version in the echo information is the updated firmware version.