One of the best extensions that I installed was “HTTPS Everywhere”. It tells you when you are hitting an HTTP site and has you manually click whenever that happens. I will also automatically attempt to find and https:// channel if there is one. If the site you are trying to hit has bad cert or handshake it will let you know.
I agree with the sentiment. It’s 2019 and all web traffic should be secured.
2x 16GB Kingston KSM26ED8/16ME (32GB DDR4-2666 ECC) @ 1333Mhz stock settings:
@ 1800Mhz:
almost 33% faster 
BUT, it seems like ECC is not properly working and is not reporting when corrections happen. I’m still investigating this a bit further, but I will make an extensive post on this issue soon in ASRock Rack X470D4U2-2T
This is quite a big issue, especially when overclocking, because you actually can’t know if it is really stable (it could be that unreported ECC corrections make it “seem” stable, while it is actually not!)
yeah thats a good browser plugin, but it doesn’t work when the site you hit doesn’t have an https:// interface, like in the case with asrock’s bios and bmc file hosting.
Can anyone recommend me a low profile graphic card. High value for a reasonable price. Minor plex with 6 streams. Thanks in advance.
Thanks a lot for the tip. I bought 4 from newegg.
Corsair had a 20% off during cycber monday + befrugal 3% + 5% chase freedom category.
I’m struggling to change any memory settings on my board and it seems that the highest frequency I can set it to is 3000MHz
Where did you get your bios revision? The highest version I can find is 3.20
For getting above 3000MT/sec, you best use a Ryzen 3000 CPU. Ryzen 1000 or 2000 may have difficulty with that.
I found the following way the easiest to figure out the highest possible frequency:
My 2666MT/sec ECC RAM went to 3800MT/sec-4000MT/sec like this before it started showing issues 
Perhaps the auto settings in the BIOS do the same, but I’m not sure, as that is not the way I tried it…
Also note that 3000Mhz != 3000MT/sec. If you really mean 3000Mhz (= 6000MT/sec) I think you should be happy with that speed already
Where did you get your bios revision? The highest version I can find is 3.20
In post #535 in this thread somebody posted the login credentials for the asrockrack ftp server. Don’t use the links from that post, because they are for the “X470D4U2-2T” board. But if access the ftp server you will find a directory for the x470d4u board with the 3.25 bios file.
Hey fellow X470D4U owner here, again. Sorry i didn’t contribute much.
Been trying to trouble shoot a lot of issues with Unraid, harddrives and file systems. But that is a story for another time.
I am having a weird issue where i sporadically get incoming traffic of 7.2 ish mbps ( the speed is very consistent) on both bond0 and eth0. No storage device is being written too. It doesn’t matter if i block access to the web. Killing all dockers and smb shares changes nothing. The traffic on bond0 and eht0 is simultaneous and both incoming.
Is this some ipmi/kvm weirdness? It randomly happens and seems to last for over an hour. Nothing on my network seems responsible … i think.
Thank you for your cheeky explanation, I forgot about the D in DDR. I got the memory set correctly now with the bios reporting it correctly. I’m still pretty new to Linux so I’m not sure how to benchmark on Debian, suggestions would be appreciated
For those interested:
I’ve finally posted my findings regarding ECC not working on the Asrock Rack X470D4U2-2T using a Ryzen 3000 CPU. I expect this the same for the Asrock Rack X470D4U…
FYI: New BIOS v3.30 and BMC v1.90 versions were just released on the official website.
Nice.
So glad they dropped these on the site without sha256 sums.
I was hoping these would be agesa 1.0.0.4 patch B so I wouldn’t have to patch my kernel vfio.
Hi,
Is anyone actually capable of reading the SPD inside Windows on this (x470D4U or x470D4U2-2T) motherboard?
Or is it my memory - Kingston KSM26ED8/16ME - (or perhaps ?broken? mobo) that is causing this…?
No one here running Windows 10? (perhaps in dual boot like me)
In meanwhile I’ve figured out that it is not the RAM. I’ve just received most parts for my new desktop build and on my x570 mobo there is no problem reading the SPD from this RAM…
Can someone please check on their mobo? It should be a very quick check…
Yes, access to individual system memory module properties is unfortunately broken, cp. my posting from August:
ASRock Rack knows about it but I’ve never received a response when they plan to solve it 
Now that version 3.30 is out… has anyone retested?
@aBav.Normie-Pleb
Thanks for the response!
I was working with Vitaliy (creator of Thaiphoon Burner) to try and figure this out. He send me a couple of debug versions of his tool that gather more debug info, but he wasn’t able get it fixed without Asrock Rack their help
This was his latest answer:
It confirms that the SMBus controller of your CPU is configured and functioning properly. I have the same SMBus settings absolutely, but Thaiphoon and other software detect all SPD EEPROMs of my DRAM modules.
Well, the BIOS of your motherboard somehow reads SPD information and saves it to DMI tables. As you can see, Thaiphoon Burner reads the part number of your DIMM modules (9965745-002.A00G) from the DMI tables without issues. So, I believe ASRock implemented a non-typical way of accessing SPD on your motherboard model and it is not documented.
@nx2l
SPD reading under Windows doesn’t work on 3.31, which should be the same as 3.30 + a few bug fixes
Under Proxmox I can’t detect any i2c device neither.
root@pve:~# i2cdetect -r -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – -- – -- – -- – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- – -- – --
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- – -- – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -- – -- – -- – --
70: – -- – -- – -- – --
root@pve:~# i2cdetect -r -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – -- – -- – -- – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- – -- – --
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- – -- – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -- – -- – -- – --
70: – -- – -- – -- – --
root@pve:~# i2cdetect -r -y 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – -- – -- – -- – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- – -- – --
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- – -- – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -- – -- – -- – --
70: – -- – -- – -- – --
root@pve:~# i2cdetect -r -y 3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – -- – -- – -- – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- – -- – --
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- – -- – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -- – -- – -- – --
70: – -- – -- – -- – --
root@pve:~# i2cdetect -r -y 4
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – -- – -- – -- – -- – -- – -- –
10: – -- – -- – -- – -- – -- – -- – -- – --
20: – -- – -- – -- – -- – -- – -- – -- – --
30: – -- – -- – -- – -- – -- – -- – -- – --
40: – -- – -- – -- – -- – -- – -- – -- – --
50: – -- – -- – -- – -- – -- – -- – -- – --
60: – -- – -- – -- – -- – -- – -- – -- – --
70: – -- – -- – -- – --
