Aquantia AQC10x firmware update

[follower]

driver 2.2.3 and fw 121 are out

It was released about months ago. The date you visit their page doesn't mean the release date. It shows your present date. Don't be confused. Their website is an idiot.

 

[DonCatoli]

It was released about months ago. The date you visit their page doesn't mean the release date. It shows your present date. Don't be confused. Their website is an idiot.

Which is why I merely stated they were released and not mentioned any dates.

 

[follower]

Which is why I merely stated they were released and not mentioned any dates.

They don't care about their idiotic website.

 

[K750]

Thanks a looooooot for providing the method of diag.exe.
I just saved my adaptor.

The adaptor is QNAP QNA-T310G1S (Thunderbolt3 to 10Gbe SFP+, working at Thunderbolt3 40Gb/s, and PCI-E 3.0 x2 lane to AQC100S, made by QNAP),
and it dead after updating firmware to 3.1.90 with the tool provided on https://www.aquantia.com/support/driver-download/ (linked from QNAP website).

The update was successful, and the device can be detected by Windows or Mac OS X properly, also shows a link speed of 10Gbps, but doesn't have any data flow incoming to OS.

After downgrading to 3.1.84, the adaptor works fine.

Then I update it again to 3.1.90, it doesn't work again.
And I downgraded it to 3.1.84, and it works fine again...

So this is absolutely a firmware problem.

# How to downgrade your AQC100 AQC 107 AQC111 or Thunderbolt 10Gbe Adaptor with Aquantia chips firmware? #

Hello everyone.
I have the same problem with a QNAP QNA-T310G1S.
Currently there is firmware 3.1.118 and like version 3.1.121 it does not work.
I can't go back.
Did you solve your problem ?
Thank you in advance.

 

[K750]

Hello everyone
Do you know how to save an adapter QNAP QNA-T310G1S with Diag.exe ?.
Thank you in advance

 

[K750]

Hello.
Great, the update has been done and it works.
Thank you for warning us.
Claude.

 

[The_Grumpy_Cat]

After I flashed firmware, it appears that I've bricked my AQC111C. No matter what I do, I cannot get it to be detected by Windows (Showing code 31 in device manager). I also cannot rollback, or update firmware, as it is not detected... Anyone have this problem before, and have advice on how to get my adapter up and running again?

 

[L&LD]

Welcome to the forums @The_Grumpy_Cat.

What have you tried? What version of Windows (10, 11, Pro)?

Reboot?

Full power off?

Physically removed from the system?

 

[K750]

Rollback Firmware
1) Execute "atlflashupdate -r" at this command line window
2) Select the adapter number
3) Original firmware will be restored.

 

[The_Grumpy_Cat]

Rollback Firmware
1) Execute "atlflashupdate -r" at this command line window
2) Select the adapter number
3) Original firmware will be restored.

I've tried this before. The adapter isn't being detected by Windows, which means it is also not detected by the update utility. See screenshot for reference. I've tried manually adding the device via device manager using Marvell's drivers, but I get error code 31.

Welcome to the forums @The_Grumpy_Cat.

What have you tried? What version of Windows (10, 11, Pro)?

Reboot?

Full power off?

Physically removed from the system?

Windows 11. I've tried all of the steps you listed. Can't remove the adapter as it's built into my motherboard

 

[L&LD]

What motherboard do you have? Did you flash with the manufacturer's tools?

Does it work on Windows 10? Test with a small drive, and a clean install.

 

[DonCatoli]

driver 3.1.6 is out

 

[TheLostSwede]

driver 3.1.6 is out

Seemingly not that new, nor that important, unless you're using Windows 11.

##v3.1.6.0
_Date 19.10.2021_
* Updated Marvell product name to "Marvell AQtion Network Adapter"
* Add Win11 folder for driver binaries.

 

[L&LD]

I don't consider the changelog the final say in what was changed under the hood. Sometimes, they state changed items and don't want to (forget to?) indicate what fixes were also implemented.

 

[follower]

Seemingly not that new, nor that important, unless you're using Windows 11.

##v3.1.6.0
_Date 19.10.2021_
* Updated Marvell product name to "Marvell AQtion Network Adapter"
* Add Win11 folder for driver binaries.

There was an issue. Some systems don't work with previous version 2.2.3.0. The driver should be installed manually to be fixed. It's fixed with this version.

 

[MDK]

thank you I will give it a shot

Hello,

have the same problem, it just shuts down only disabling it or restarting the PC fixes it, did you find a solution ?

thanks for the help

Using this firmware

And this driver

I have a Asus rampage extreme encore X299

 

[MDK]

hello

or does any one found a solution for the problem above?

cheers

 

[Kolowski]

I do have the special OLD debug firmware which allows you to change MAC as well as device ID and sub system id. It did not enable WOL on my Asus card. But I can send it to anyone if they want along with video Tutorial.

Hi @sanke1 ,
would you please send me the debug firmware with the tutorial, please? I need it for my ASUS XG-C100C.

THX in advance

 

[d5aqoep]

@Kolowski I know it's too late but I found the link sanke1 sent me which had a video of how to restore firmware to older version along with correct MAC address. After firmware update is successful and you have rebooted your PC 2-3 times, you can proceed to update it to latest official firmware from Marvell.

You have to uninstall current driver and install a special Diag driver as shown in the video. It also includes readymade instructions to pass in cmd after editing AQC107-Config.aqc file with your correct MAC address.

Reasons for using this:
1. Your MAC address is showing 00-00-00-00-00-00 because you used it in Hackintosh and Apple's MacOS messed up the card's MAC address.
2. You used incorrect firmware and busted your card.
3. You want to change your MAC address and run from authorities.
4. You are Marvell employee and you accidentally deleted your only diagnostic folder.

1.2 GB file on MEGA

mega.nz

 

[RTWZ80]

Bricked my QNAP Thunderbolt 3 to 10GbE adapter (QNA-T310G1S) with the update and could not roll the Marvell firmware back to the original version too. Ended up doing an RMA back to QNAP and finally got it fixed.