I've bought an Asrock x370 Gaming ITX/ac mobo, and installed a Ryzen 5 2400G (after I used a random crap Bristol Ridge APU to power it up the first time to update the "bios" aka UEFI firmware to the latest version). Now the UEFI is 4.50 (and I also upgraded to 4.51 later to see if something changed).
I tried with both OpenSUSE tumbleweed + latest daily kernel build (4.16.something) and with Debian Testing + kernel 4.16 from Ubuntu mainline kernel builds.
Aaand.... ECC isn't working, nor I see options in the UEFI settings to enable it. There are only some auxiliary ones like DRAM scrubbing interval.
And from AIDA64 (within Windows) the situation is also the same:
while the RAMs are detected as ECC properly
I've googled around and from a german forum with screenshots of AIDA64 it seems that Raven Ridge has no ECC also on the Gigabyte mini itx board (and the owner states that his board also runs with ECC enabled with Summit Ridge Ryzen)
while on my board a Ryzen 7 1700 (Summit Ridge) has ECC enabled.
On the flip side, there is a confirmation that the Biostar Racing X370-GTN ITX has ECC enabled with a Summit Ridge (so the specs on their site are not lying), and as said above that the Gigabyte mini itx board also supports ECC correctly with Summit Ridge.
I saved the relevant pages in the forum discussion (translated with Google translate) in this zip file
I'm very annoyed, as it seems I'll have to buy a Summit Ridge (probably a Ryzen 5 1600) and use a discrete GPU, but I was strongly suspecting this would happen, so whatever.
Posting this here in the hope that it is useful, I'm not blaming AMD for lack of esoteric features like ECC in an APU that has its own share of complexity and issues.
If you have any feedback or tips or tricks, feel free to share.
I tried with both OpenSUSE tumbleweed + latest daily kernel build (4.16.something) and with Debian Testing + kernel 4.16 from Ubuntu mainline kernel builds.
Aaand.... ECC isn't working, nor I see options in the UEFI settings to enable it. There are only some auxiliary ones like DRAM scrubbing interval.
Code:
root@debian-test:~# dmesg | grep EDAC [ 0.132242] EDAC MC: Ver: 3.0.0 root@debian-test:~# ls /sys/devices/system/mc ls: cannot access '/sys/devices/system/mc': No such file or directory root@debian-test:~# ls /sys/devices/system/edac/mc power subsystem uevent root@debian-test:~# ls /sys/devices/system/edac mc power uevent root@debian-test:~# ls /sys/devices/system/edac/mc power subsystem uevent root@debian-test:~# edac-util -s edac-util: EDAC drivers loaded. No memory controllers found test@debian-test:~# dmidecode -t memory | grep Width Total Width: 128 bits Data Width: 64 bits Total Width: 128 bits Data Width: 64 bits
while the RAMs are detected as ECC properly
I've googled around and from a german forum with screenshots of AIDA64 it seems that Raven Ridge has no ECC also on the Gigabyte mini itx board (and the owner states that his board also runs with ECC enabled with Summit Ridge Ryzen)
while on my board a Ryzen 7 1700 (Summit Ridge) has ECC enabled.
On the flip side, there is a confirmation that the Biostar Racing X370-GTN ITX has ECC enabled with a Summit Ridge (so the specs on their site are not lying), and as said above that the Gigabyte mini itx board also supports ECC correctly with Summit Ridge.
I saved the relevant pages in the forum discussion (translated with Google translate) in this zip file
I'm very annoyed, as it seems I'll have to buy a Summit Ridge (probably a Ryzen 5 1600) and use a discrete GPU, but I was strongly suspecting this would happen, so whatever.
Posting this here in the hope that it is useful, I'm not blaming AMD for lack of esoteric features like ECC in an APU that has its own share of complexity and issues.
If you have any feedback or tips or tricks, feel free to share.
Comment