You should have read some of the above posts before flashing any firmware. Hanson has bricked his front USB3 ports (with my "generous" help) by crossflashing. What we didn't knew at the time, was that there are two types of controller - 1042 and 1042A. The last firmware for 1042 is 130125_00_02_00 and for 1042A is 131025_10_11_03.

DON'T make the mistake of crossflashing. Either visually check the controller (not sure if it has the A letter) or dump your current firmware and check for U2104_RCFG = 1042 or 2104B_RCFG = 1042A.

I have an Asus X79 Sabertooth which comes with 1042 chipset I believe. (This is what it says in the motherboard manual chipset diagram). Currently I have the 120816_02_02_6D firmware, where can I download the 130125_00_02_00 and how do I dump the current firmware to double check it is the 1042 not 1042A?

Zitat von Wam7 im Beitrag #34I have an Asus X79 Sabertooth which comes with 1042 chipset I believe. (This is what it says in the motherboard manual chipset diagram). Currently I have the 120816_02_02_6D firmware, where can I download the 130125_00_02_00 and how do I dump the current firmware to double check it is the 1042 not 1042A?

If you have 120816_02_02_6D firmware, then you most likely have an ASM1042 controller. You can check this by dumping current firmware with "104xfwdl.exe /A" and search for U2104_RCFG. It is recommended to do that, because your board seems to have an embedded ASM1042A firmware in UEFI.

Firmware 130125_00_02_00 is attached. Just boot from DOS, run d.bat for verifying current firmware, u.bat for updating, or any of the supported commands:

When I flashed the firmware that I got from station-drivers, how could it "not touch" the firmware of my board if it was an ASM1042? Did it practically downgrade it to v (which is what I see when verifying the firmware)?

When I said untouched, I meant not modified by anyone. Probably the controllers are similar and one firmware can work on another controller, but it will be limited. This is why you get the version 10083_00_00_0d, which is probably the oldest version known by the flasher (10-08-03, YY-MM-DD), instead of unknown version. Hanson had the same report, which shows that the firmware is not properly communicating with your controller.

Given the fact that you get the same wrong version and you have an old mainboard (probably 1042A was not even released at that time), there is 95% chances that your controller is ASM1042. So you should flash the above firmware.

Zitat von lordkag im Beitrag #38When I said untouched, I meant not modified by anyone. Probably the controllers are similar and one firmware can work on another controller, but it will be limited. This is why you get the version 10083_00_00_0d, which is probably the oldest version known by the flasher (10-08-03, YY-MM-DD), instead of unknown version. Hanson had the same report, which shows that the firmware is not properly communicating with your controller.

Given the fact that you get the same wrong version and you have an old mainboard (probably 1042A was not even released at that time), there is 95% chances that your controller is ASM1042. So you should flash the above firmware.

Ok. I'm assuming the firmware above is an untouched version of the latest firmware for the 1042?

Zitat von plutomaniac im Beitrag #44There is no point in dumping your firmware now, you have already flashed something on top of it so you will only dump what you flashed whether it's right or wrong.

Let's not make our lives harder for no reason. Check your motherboard and find the ASMedia chip, does it say ASM1042 or ASM1042A? It's very simple.

Well, that's what I was thinking. But lordkag suggested me to dump the firmware anyway, I just trusted his suggestion. I was thinking his reason was probably because the firmware flashed was still for the correct version of my board because I was still able to use it Windows.

I'm just looking for a way to not do that because I don't want to disassemble everything again. But if there's no other way to check the correct chip, then I'll be all for it.