MZ32-AR0 REV 1 > 3

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

nutsnax

Active Member
Nov 6, 2014
335
135
43
113
before you start:
where is your MZ32-AR0 from ?
old used one 1.0 form china may not work for this, they are out of old OEM/GB servers.
Mine is from China, but it came in a bulk-packaged type box and sold as new - it was from tugm. It also came with an I/O shield etc.

edit: The reason I'm thinking of doing this is because I'm having weird nvme detection issues. I'm trying to use a number of bifurcation cards but it takes a complete BIOS reset to pick up on additional NVME drives (it will eventually do it, just really time consuming).
 
Last edited:

RolloZ170

Well-Known Member
Apr 24, 2016
6,669
2,063
113
--
Mine is from China, but it came in a bulk-packaged type box and sold as new - it was from tugm. It also came with an I/O shield etc.
looks good to me.
tugm, Seller Notes
“Gigabyte mz32-ar0 motherboard Rev 1.0 supports 7001 7002 7003 series CPU processors”
so if it not work, ask tugm for help.
 
  • Like
Reactions: nutsnax

nutsnax

Active Member
Nov 6, 2014
335
135
43
113
--

looks good to me.
tugm, Seller Notes
“Gigabyte mz32-ar0 motherboard Rev 1.0 supports 7001 7002 7003 series CPU processors”
so if it not work, ask tugm for help.
OK thanks, I'll try to direct flash to the newer 3.0 BIOS
 

nutsnax

Active Member
Nov 6, 2014
335
135
43
113
It worked. this thing flashed straight to the 3.0 BMC and BIOS just fine. Thanks for the help!

For future people reading this: The boards tugm sells (and probably others) will flash to the 3.0 BIOS. IMO to be on the safe side I'd flash to the latest 1.0 BIOS on the site first as an intermediate step but that may not be necessary.

Update your BMC firmware first before upgrading the BIOS.
 

upalachango

New Member
May 28, 2023
24
4
3
I was able to update my BIOS to the stock rev3.0 (M18/R34) that's current on the GB site without issue. The most recent R28 for rev1 gave me an infinite power cycle loop, but the R25 worked too (my board came with R19). I am using a 7D12 CPU though, so the R28 boot cycle could be a result of the non-retail part rather than any intrinsic problem with the BIOS.

My system boots up fine with 8gb of test ECC memory, my LRDIMMS though aren't working (i suspect LRDIMM might not work with the shaved down memory channels of the 7d12, which would be a huge bummer).
 

gb00s

Well-Known Member
Jul 25, 2018
1,256
670
113
Poland
LRDIMM works perfectly fine with R34 and 7D12 here (e.g. Samsung M386A4G40DMo-CQB0Q). I can even OC it to 2400Mhz and it passes tests. Also NVDimm-N does work and so on.
 
Last edited:
  • Like
Reactions: upalachango

upalachango

New Member
May 28, 2023
24
4
3
I'm using m386a8k40cm2-cvfby which is 2933 which isn't posting. I may try to manually set memory timings to massage it past an initial memory training. On another thread others had inconsistent lrdimm compatibility and the eBay seller says 2Rx4 is best supported.

I really don't want to have to buy another 128gb of memory, so I'll keep chipping away until I've exhausted all options lol
 

gb00s

Well-Known Member
Jul 25, 2018
1,256
670
113
Poland
On this mobo all LRDimms work with any CPU up to 8 channels. Other mobos do not support LRdimm at all.
 

upalachango

New Member
May 28, 2023
24
4
3
I wouldn't say that as myself and others have had significant trouble or been unable to even post using LRDIMMs.

I do have a promising update though. I was finally able to POST my LRDIMMs but it's still a work in progress. I had to first boot with an 8GB RDIMM. From there I have to manually set several memory timings in the AMD CBS page of the BIOS. I then save, shutdown, swap in my LRDIMM sticks and then reboot. This will get me into the OS at speeds up to 2666mhz but not 2933mhz. The single RDIMM stick though will boot up to 2933mhz without issue.

The issue seems to be that for some reason the BIOS isn't pulling timings from my LRDIMM and is unable to train the DDR on boot, so it never gets to POST. My memory is Samsung and on the QVL for LRDIMMs so it's not likely a memory issue (and the memory works fine at lower speeds).

If it was just an issue of being unable to hit 2933 it'd be disappointing but not awful, the problem though is that it can't POST at all. So clearing the CMOS means I won't be able to boot my server without swapping out the LRDIMMs. So it's frustrating to test timings as there is no way to boot the machine if timings are off without doing a physical memory swap.

I'm narrowing in on the specific settings by going through the LRDIMM datasheets and trying to match specs with slightly different named BIOS settings. It's beyond tedious. I suspect the issue is the BIOS applies 2R timings and not 4R timings for some tertiary settings, causing the no-POST. I just have to find which ones have to be manually set and which ones can be left on AUTO for normal boot memory training. Now that I know the memory is good and works I'll eventually find the magic combo.

gb00s, if you have any screenshots of 2933mhz timings for your LRDIMM setups on the MZ32, it'd be greatly appreciated!
 
  • Love
  • Like
Reactions: RedX1 and RolloZ170

RolloZ170

Well-Known Member
Apr 24, 2016
6,669
2,063
113
@upalachango
BIOS is easy moddable. if you investigated all the required changes we may create a LRDIMM BIOS,
means you can POST even after options set to defaults.
 

dodgy route

Member
Aug 12, 2020
48
66
18
Australia
Is it possible to flash the V3 7002 bios on this board?
Havent found anyone talking about it ever.

V1 bios seems to have stopped development and V3 is ongoing.
I tried to flash straight up via web but no success. Checksum errors.

So I don't get how the Milan bios is working straight up compared to Rome.

Anyone have more info?
Thanks!
 

dodgy route

Member
Aug 12, 2020
48
66
18
Australia
via BMCWebGUI you have to use the RBU file (RBU = remote BIOS update)

in the 32GB package are a Rome and a Milan BIOS. if you have Rome(7002) the MIlan BIOS makes no sense.
Sorry for the confusion, I was trying to flash "flash_R.rom" from the v3 bios pack.
I see, so my mistake was flashing only the Rome rom, instead of the RBU. This makes complete sense, as this is how I was always updating the V1 bios too.

Thanks!
 
  • Like
Reactions: RolloZ170

nazar-pc

New Member
Jan 7, 2024
3
0
1
For those who did 1.0 to 3.0 upgrade, is it possible to then use BMC and BIOS from 3.0 going forward?
I'm thinking about this just to get BIOS security upgrades even without having 7003 processor (yet).
 

nazar-pc

New Member
Jan 7, 2024
3
0
1
Milan BIOS is active only if you run a Milan.
do you still run Naples ?
No, I'm running Rome and will definitely not go back to Naples.
I think Rome CPUs should still get security fixes, but Gigabyte didn't release any BIOS updates for 1.0 since May 17 2022 and would be great to just "upgrade" the whole thing to 3.0 so I can still enjoy updates for some time.
 

nazar-pc

New Member
Jan 7, 2024
3
0
1
For example latest M18_R34 BIOS for 3.0 mentions in changelog two updates for Rome processors:
1. Updated Milan AGESA 1.0.0.A
2. Updated Rome AGESA 1.0.0.G
3. Updated Rome Microcode 0830107A for CVE-2023-20593 issue
 

nobodz

New Member
May 4, 2024
2
0
1
Did you get this working? Also the Rev 3.0 has the U.2 ports listed as pcie Gen 4 vs the Gen 3 listed for the Rev 1.0. Is this "unlocked" by the new firmware?
Did anyone affirm that the U.2 ports get pcie gen 4 with the firmware update to Rev. 3?