EU Gigabyte Mainboard MC12-LE0 Re1.0 AMD B550 AM4 Ryzen

[_Dejan_]

Replaced the battery, still nothing.



No, I don't have any graphics card installed.

So the last few days have been a bit chaotic...
I manage to get another PC to test the Ryzen 5 4650G, and it got to the BIOS in a B450 Tomahawk Max.
Also I tried again in my MC12-LE0 motherboard with the Ryzen 5 3600 but now with my RAM and I was able to POST and get to the BIOS.

So I'm not sure what to do I think I will give up on the 4650G and buy a 3600, what do you guys think or have any CPU suggestion?
Did I forgot to test anything?

Thanks.

I don't think that problem is in battery... Also BMC version do not effect board boot...

I had 3 boards, 3 CPU's and 3 memory's and run them in this configuration without issue:
1.) MB + CPU 5600 + 64GB(2x32GB) NON ECC RAM
2.) MB + CPU 5600 + 64GB(2x32GB) ECC RAM
3.) MB + CPU PRO 4650G + 8GB(1x8GB) NON ECC RAM

System with PRO 4650G CPU boot normaly with stock BIOS and F18...

 

[zr0dfx]

Replaced the battery, still nothing.



No, I don't have any graphics card installed.

So the last few days have been a bit chaotic...
I manage to get another PC to test the Ryzen 5 4650G, and it got to the BIOS in a B450 Tomahawk Max.
Also I tried again in my MC12-LE0 motherboard with the Ryzen 5 3600 but now with my RAM and I was able to POST and get to the BIOS.

So I'm not sure what to do I think I will give up on the 4650G and buy a 3600, what do you guys think or have any CPU suggestion?
Did I forgot to test anything?

Thanks.

I run mine off a 5600 from Ali Express. I think it cost £60 Happy with it.

 

[zr0dfx]

BIOS released seem to have slowed right down for this mobo.

 

[RolloZ170]

BIOS released seem to have slowed right down for this mobo.

recent updates solved some AMI BIOS vulnerabilities.
things ASRock Rack never do.

 

[helskor]

Got a 5900X running on one of these boards I have. I finally found Eco-Mode for this version of the BIOS (ver. F18) but was wondering if anyone saw any impact of the "cTDP" option set to manual.
Setting a value (example 65W) doesn't seem to do anything. Has anyone gotten this to work by chance?

Edit: After some more digging around, I found this German forum that has a lot of useful info too around this MB:

[Sammelthread] - Gigabyte MC12-LE0 (AM4, B550, servertauglich: IPMI, Dual Lan, ECC)

Vorvorwort: Danke an @pumuckel für das ursprüngliche Erstellen des Threads. Ich habe mich bereit erklärt den Thread zur Pflege zu übernehmen und um neue Inhalte zu ergänzen. Der ursprüngliche starter bleibt vorerst als Spoiler im letzten Abschnitt angehängt, damit keine Inhalte verloren gehen...

www.hardwareluxx.de

(obviously in German)

 

[zr0dfx]

2 New BIOS releases in the last few days. I assume F20 is a bug fix for F19 but no release notes.

Edit: from relase notes in F20:
F20
1. Fixed Gigabyte Logo display.
---------------------------------------------------------------------------------------------------------------------
F19
1. Update AGESA 1.2.0.E.
2. [Security Update] CVE-2024-0179, CVE-2024-21925, CVE-2024-36347.
-----------------------------------------------------------------------------------------------------------

 

[helskor]

View attachment 43290

2 New BIOS releases in the last few days. I assume F20 is a bug fix for F19 but no release notes.

Edit: from relase notes in F20:
F20
1. Fixed Gigabyte Logo display.
---------------------------------------------------------------------------------------------------------------------
F19
1. Update AGESA 1.2.0.E.
2. [Security Update] CVE-2024-0179, CVE-2024-21925, CVE-2024-36347.
-----------------------------------------------------------------------------------------------------------

My av went mental when I unzipped F20, did you have any issues?

 

[zr0dfx]

My av went mental when I unzipped F20, did you have any issues?

No issues here. What did it say?

 

[helskor]

No issues here. What did it say?

looks to be a false alarm with one of the included amibios flash file "amifldrv64.sys"
but good to know, thanks!

 

[zr0dfx]

looks to be a false alarm with one of the included amibios flash file "amifldrv64.sys"
but good to know, thanks!

Just installed it via BMC all is good as far as I can see

 

[helskor]

Thanks for the info, updating a machine now via UEFI shell

 

[RolloZ170]

F20 ( Build Date: 2025/03/14 )
1. Fixed Gigabyte Logo display.
---------------------------------------------------------------------------------------------------------------------
F19 ( Build Date: 2025/02/22 )
1. Update AGESA 1.2.0.E.
2. [Security Update] CVE-2024-0179, CVE-2024-21925, CVE-2024-36347.

 

[Eric_on_Fire]

My MC12-LE0 seems to have went through an hour of boot loops today and now while IPMI looks fine, it won't boot, suspiciously only a few days after installing F20. My initial assumption is that the PSU partially failed, but I haven't had time to properly troubleshoot yet. Anyone else seen anything similar on F20?

Spoiler: IPMI log

2025-04-29 12:22:00 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 12:17:37 (-10) Tuesday oem_timestamped was deasserted
2025-04-29 12:17:37 (-10) Tuesday C: boot completed was asserted
2025-04-29 12:17:32 (-10) Tuesday Extended SEL data was asserted
2025-04-29 12:17:32 (-10) Tuesday Extended SEL data was asserted
2025-04-29 12:17:32 (-10) Tuesday boot completed - boot device not specific was asserted
2025-04-29 02:15:38 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 02:15:35 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 12:15:46 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 12:15:45 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 12:15:42 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 12:15:30 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 12:15:27 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 12:13:36 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 12:13:24 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 12:13:20 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 12:08:18 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 12:08:16 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 12:07:52 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 12:07:40 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 12:07:37 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 12:04:44 (-10) Tuesday oem_timestamped was deasserted
2025-04-29 12:04:44 (-10) Tuesday C: boot completed was asserted
2025-04-29 12:04:40 (-10) Tuesday Extended SEL data was asserted
2025-04-29 12:04:40 (-10) Tuesday Extended SEL data was asserted
2025-04-29 12:04:39 (-10) Tuesday boot completed - boot device not specific was asserted
2025-04-29 12:02:55 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 12:02:44 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 12:02:40 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 11:57:52 (-10) Tuesday oem_timestamped was deasserted
2025-04-29 11:57:52 (-10) Tuesday C: boot completed was asserted
2025-04-29 11:57:47 (-10) Tuesday Extended SEL data was asserted
2025-04-29 11:57:47 (-10) Tuesday Extended SEL data was asserted
2025-04-29 11:57:47 (-10) Tuesday boot completed - boot device not specific was asserted
2025-04-29 01:56:00 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 01:55:56 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 11:56:06 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 11:56:06 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 11:56:03 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 11:55:52 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 11:55:50 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 11:30:54 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 11:30:50 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 01:29:12 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 01:29:09 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 11:29:19 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 11:29:19 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 11:29:16 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 11:29:04 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 11:29:01 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 11:18:16 (-10) Tuesday oem_timestamped was deasserted
2025-04-29 11:18:16 (-10) Tuesday C: boot completed was asserted
2025-04-29 11:18:11 (-10) Tuesday Extended SEL data was asserted
2025-04-29 11:18:11 (-10) Tuesday Extended SEL data was asserted
2025-04-29 11:18:11 (-10) Tuesday boot completed - boot device not specific was asserted
2025-04-29 11:16:27 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 11:16:15 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 11:16:12 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 11:04:03 (-10) Tuesday oem_timestamped was deasserted
2025-04-29 11:04:03 (-10) Tuesday C: boot completed was asserted
2025-04-29 11:03:58 (-10) Tuesday Extended SEL data was asserted
2025-04-29 11:03:58 (-10) Tuesday Extended SEL data was asserted
2025-04-29 11:03:58 (-10) Tuesday boot completed - boot device not specific was asserted
2025-04-29 11:02:14 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 11:02:02 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 11:01:59 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 10:59:36 (-10) Tuesday oem_timestamped was deasserted
2025-04-29 10:59:36 (-10) Tuesday C: boot completed was asserted
2025-04-29 10:59:31 (-10) Tuesday Extended SEL data was asserted
2025-04-29 10:59:31 (-10) Tuesday Extended SEL data was asserted
2025-04-29 10:59:31 (-10) Tuesday boot completed - boot device not specific was asserted
2025-04-29 10:57:46 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 10:57:34 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 10:57:31 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 10:51:47 (-10) Tuesday oem_timestamped was deasserted
2025-04-29 10:51:46 (-10) Tuesday C: boot completed was asserted
2025-04-29 10:51:42 (-10) Tuesday Extended SEL data was asserted
2025-04-29 10:51:42 (-10) Tuesday Extended SEL data was asserted
2025-04-29 10:51:41 (-10) Tuesday boot completed - boot device not specific was asserted
2025-04-29 00:49:52 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 00:49:48 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 10:49:58 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 10:49:58 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 10:49:55 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 10:49:43 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 10:49:39 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 10:44:20 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 10:44:16 (-10) Tuesday Power Off / Power Down was asserted
2025-04-29 00:42:26 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 00:42:23 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 10:42:33 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 10:42:33 (-10) Tuesday Timestamp Clock Synch was asserted
2025-04-29 10:42:30 (-10) Tuesday OEM System Boot Event was asserted
2025-04-29 10:42:19 (-10) Tuesday Power Off / Power Down was deasserted
2025-04-29 10:42:15 (-10) Tuesday Power Off / Power Down was asserted

 

[SlowmoDK]

My MC12-LE0 seems to have went through an hour of boot loops today and now while IPMI looks fine, it won't boot, suspiciously only a few days after installing F20. My initial assumption is that the PSU partially failed, but I haven't had time to properly troubleshoot yet. Anyone else seen anything similar on F20?

It's probably not the update, but why update anyway ?

F19 was a major update with new AGESA and security fixes, but this is a logo update.
None of my systems are getting F20 installed

Why fix if not broken

 

[helskor]

My MC12-LE0 seems to have went through an hour of boot loops today and now while IPMI looks fine, it won't boot, suspiciously only a few days after installing F20. My initial assumption is that the PSU partially failed, but I haven't had time to properly troubleshoot yet. Anyone else seen anything similar on F20?

I have a few machines running on F20, no issues yet

 

[sOid]

Hi all!

I've recently acquired this motherboard. I've updated it successfully to BCM 12.61.35 and BIOS F20. All installed hardware shows up in the BCM interface. Most notably:
- Ryzen 5Pro 4650G
- 2x Hynix HMA82GU7CJR8N-VK 16G (from the QVL list) in slots A1 and B1
- NVMe
- Some HDD's and SSD's
- PCIE SATA-card

I've also successfully installed Proxmox on the NVMe drive.

So most things seem to be working fine. However, there are a few issues/weird things going on.
1. There are no sensors in the BCM interface! Also tried with an IPMI-command from another Linux device on the same LAN, with the same results. Only Watchdog and SEL are available (wihout any actual data it seems). Everything is installed correctly. All fans are spinning, both CPU and casefans. But there's no way to control them. Settings > Fan Profile isn't available either (although I can select it in the Quick Links thingy, but as there are no sensors, there's no way to create an actual fan profile). I've ran memtest for 8 hours or so and that tool does display CPU temp...
2. The web interface crashes when I click on FRU Information.
3. When I try BCM Cold Reset the host also reboots. Is this expected behaviour?
4. Sometimes I 3 beeps from the motherboard when booting. Not sure what this means.

I've searched for hours in order to fix these issues. Especially 1 is fairly crucial. But to no avail... I really hope any of you can provide some insight!

 

[richard.dzavoronok]

I don't know who the seller is as I don't have premium Merkandi account, but this looks like a good deal? The prices are excluding VAT so only for EU VAT registered.
Seller is from Pland and motherboard comes with Gelid cooler.

I recommend the offer: Gigabyte MC12-LE0 Re 1.0 AMD B550 AM4 Ryzen 5000 4000 3000 motherboard + new cooling - Poland, New - The wholesale platform

For sale 1000pcs Gigabyte MC12-LE0 Re 1.0 AMD B550 AM4 Ryzen 5000 4000 3000 motherboards with new coolers. The boards are designed for servers. Specification: -

merkandi.com

edit: user->seller
edit2: added additional info

 

[etorix]

As long as you can buy as a private person, being charged VAT in the process, 60 E excl. VAT would be a good price for this board. But the registration fee for opening a Merkandi account makes it unpalatable if you don't need a few tens of boards.
Hopefully, with some motre research it should be possible to get in touch directly with a Polish reseller.

 

[Unrest5078]

I don't know who the seller is as I don't have premium Merkandi account, but this looks like a good deal? The prices are excluding VAT so only for EU VAT registered.
Seller is from Pland and motherboard comes with Gelid cooler.

I recommend the offer: Gigabyte MC12-LE0 Re 1.0 AMD B550 AM4 Ryzen 5000 4000 3000 motherboard + new cooling - Poland, New - The wholesale platform

For sale 1000pcs Gigabyte MC12-LE0 Re 1.0 AMD B550 AM4 Ryzen 5000 4000 3000 motherboards with new coolers. The boards are designed for servers. Specification: -

merkandi.com

edit: user->seller
edit2: added additional info

That's a scam site, 99.9%.

 

[richard.dzavoronok]

I don't think so. They are just mediator for sales.
Two years ago I purchased their membership for ~160 eur. I got the contact info to seller, but they told me the ad was already expired.
Long story short, I got a refund.

Sellers could be scammers, but that's up to you to decide.