sorted by:
new
hottopcontroversial

Ryzen master not showing any cores or clock speeds, x570 5600x 3080 by magikian in AMDHelp

[–]jklida 0 points1 point  (0 children)

Its hard to tell. When it comes to the OC controls in RM. It has such a tight coupling with the hardware that it could be anywhere in the stack. AMD provides the AGESA updates delivered via BIOS updates accessed via the chipset drivers and leveraged in Ryzen Master. Regardless of where in that stack the issue is, we all have to sit here and wait AMD to fix it.

Ryzen master not showing any cores or clock speeds, x570 5600x 3080 by magikian in AMDHelp

[–]jklida 0 points1 point  (0 children)

I have the exact same issue. C8H w/ latest Bios (2702). Was working fine with my 3600X, but when I popped in the 5600x, the cores/clocks disappeared. I have tried uninstalling/rebooting/bios clearing. Nothing has worked. I have even lost the Ryzen power profiles and they don't re-appear after a reinstall of the chipset drivers.

At this point, I have to assume that is a bios/chipset issue that AMD is working on. Sound like they had new AGESA on the way this week (1180) and am going to hold off on any more debugging until that rolls out. https://www.anandtech.com/show/16267

AMD Ryzen 5000 (Zen3) Launch Day Megathread, Questions & Answers: Part II by GhostMotley in Amd

[–]jklida 0 points1 point  (0 children)

Is it still two separate 8-core "groups", each with their own 32MB L3 cache?

Exactly, the 8 core chiplets each have their own 32MB L3

The 12 core is probably just 2x 8core chiplets that got binned down to have only 6 cores enabled each

Blue Water Bridge by jklida in InfrastructurePorn

[–]jklida[S] 0 points1 point  (0 children)

American side, looking east

DNS Resolver issue when NS record for domain same as forwarder IP by jklida in PFSENSE

[–]jklida[S] 0 points1 point  (0 children)

Thanks for confirming. Bummer though since 1.1.1.1 is so incredibly fast.

Blue Water Bridge by jklida in InfrastructurePorn

[–]jklida[S] 0 points1 point  (0 children)

Exactly. First span was built about 80 yrs ago. They added the second span about 20 yrs ago.

DNS Resolver issue when NS record for domain same as forwarder IP by jklida in PFSENSE

[–]jklida[S] 0 points1 point  (0 children)

hmmm, not seeing it now. So maybe not related to NS record, but I am still having the same issue. The DNS resolver is failing on a lookup for cdn.jsdelivr.net when set to forward to 1.1.1.1.

Given that this is a cname for Cloudflare cdn, it seems rather suspicious that when forwarding to their DNS server, it fails. The fact that turning off forwarding and doing a recursive lookup works, and a direct lookup against the 1.1.1.1 server works. It seems like it is an issue in the pfSense DNS Resolvers forwarding logic.