Hacker News new | past | comments | ask | show | jobs | submit login

Yet I can still not read CPU core temperatures of my ryzen 2600 on Linux (5.0-rc2). I am not sure what is going on but I think next time I'll go with Intel again. I read this may be related to some NDA by AMD but not sure.

Temperature monitoring for the first gen Ryzen chips has been in the kernel for about a year. The patch for second gen is there but narrowly missed the 5.0 release window, so it should land in the first release after 5.0.

Intel is a bit faster about this but it's not like they have perfect day 1 kernel support either. i.e. temperature monitoring drivers for both first gen Ryzen and Coffee Lake landed in 4.15. At the time Ryzen was almost a year old and Coffee Lake was about half a year old.


Phoronix[1] is usually good at monitoring Linux hardware news.

1 - https://www.phoronix.com

Based on personal experience temperature monitoring on Coffee Lake worked just fine with 4.14. I'm pretty sure there hasn't been a breaking change in Intel's interface for this since at least Sandy Bridge.

Interesting, 4.15 had a patch specifically for Coffee Lake thermal support. Maybe it was specific to the mobile chips.


Thanks. It's not easy to find information like this. How did you find it?

I just Googled "ryzen temperature monitoring linux".

I've had a Ryzen 1700 since they first came out so I was following the Linux support for that fairly closely at the time, mostly by browsing Phoronix fairly frequently. Thankfully after a few months I didn't need to because things were working pretty well by then, other than the thermal monitoring that took quite a while to land. Linux and brand new hardware rarely seem to get along well regardless of the vendor unfortunately.

Perhaps someone could just reverse engineer what the Windows driver does to get the values.

It could be a nice way to learn a tool like Binary Ninja or IDA (pro).

It's probably some DeviceIoControl call. Once you know the call 12-bit (I think?) ID from userland code, it should be relatively straightforward to follow the driver code to see where it ends up and what hardware registers it uses.

Or maybe it's just something through ACPI?

just when AMD looks like they will be the safe bet on CPU for the next few years you bolt? =)

It's not like I'll upgrade any time soon. A lot can happen in all those years! I'll see

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact