A rant about AMD things. Recently, I’ve been developing in a Linux environment and encountered a frustrating issue: the critical parameters like per-core temperature and power of AMD processors simply cannot be read. It’s really maddening.
At first, I planned to tough it out and write my own solution, but later I simply asked AI to generate a set of solutions. After the code was generated, the problems arose—discovering that each CPU’s PM Table configuration is different, which means a universal solution is impossible.
One pitfall after another began to appear. Sometimes it’s driver compatibility issues, sometimes it’s BIOS black box settings. Through the troubleshooting process, I realized that AMD’s documentation support in this area is indeed lacking, and the Linux ecosystem’s adaptation is still in the exploratory stage.
Now I finally understand why so many developers have opinions about this. But from another perspective, these challenges can also be considered part of the technical adventure.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
10 Likes
Reward
10
4
Repost
Share
Comment
0/400
MoonRocketTeam
· 4h ago
AMD this time is like giving you the rocket launch pad blueprints directly, but the PM Table configuration diagram is blank, which is ridiculous.
Wait, has anyone successfully read out single-core temperatures on Linux, or are we all just warming each other in this pit?
BIOS black box settings are really more difficult than reverse engineering. AMD's documentation definitely needs to be improved in this area.
View OriginalReply0
WalletAnxietyPatient
· 4h ago
This AMD PM Table pitfall is really unbelievable; each one is different, which is just outrageous.
View OriginalReply0
GhostWalletSleuth
· 4h ago
AMD, this pit is really incredible. Each CPU has a different configuration, and they still want a universal solution. That's hilarious.
View OriginalReply0
GasGuru
· 4h ago
AMD is really outrageous. The PM Table varies for each CPU, how can there be a universal solution?
I've also encountered reading temperature parameters under Linux, with a bunch of black-box documentation. After messing around for a while, I found out it was the BIOS causing the issue.
The flaw in AMD documentation should have been fixed long ago; developers have been complaining about it.
So, AI-generated code isn't万能. When faced with AMD's configuration that varies from person to person, even the most powerful models are useless.
Driver layer adaptation combined with BIOS black-boxes—this combo truly can't be beaten. No wonder so many people choose Intel.
A rant about AMD things. Recently, I’ve been developing in a Linux environment and encountered a frustrating issue: the critical parameters like per-core temperature and power of AMD processors simply cannot be read. It’s really maddening.
At first, I planned to tough it out and write my own solution, but later I simply asked AI to generate a set of solutions. After the code was generated, the problems arose—discovering that each CPU’s PM Table configuration is different, which means a universal solution is impossible.
One pitfall after another began to appear. Sometimes it’s driver compatibility issues, sometimes it’s BIOS black box settings. Through the troubleshooting process, I realized that AMD’s documentation support in this area is indeed lacking, and the Linux ecosystem’s adaptation is still in the exploratory stage.
Now I finally understand why so many developers have opinions about this. But from another perspective, these challenges can also be considered part of the technical adventure.