Can't read MCLK FCLK and UCLK on my 7945hx lenovo computer #57
Comments
|
the debug report is here:ZenTimings 1.33.1535 Debug Report ###################################################### ###################################################### P0 CHANNEL B | DIMM 0 ###################################################### Channel0: True ###################################################### ###################################################### ###################################################### ###################################################### ###################################################### ###################################################### ###################################################### ###################################################### ###################################################### ###################################################### ###################################################### |
|
Thanks for the report. Version 1.34 should improve the readings. |
|
Thanks for your effort! As a college student majoring in EE, I'm also a little bit curious about the reason why it doesn't work. So if you could tell me more details about the bugs and how you fix it later, that would be appreciated 🥰.
…---Original---
From: "Ivan ***@***.***>
Date: Thu, Jan 2, 2025 22:10 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [irusanov/ZenTimings] Can't read MCLK FCLK and UCLK on my 7945hxlenovo computer (Issue #57)
Thanks for the report. Version 1.34 should improve the readings.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
The brief explanation would be that BIOS exposes a table called AOD (AMD OverDrive, I believe, which is the old application name) that is later used in RyzenMaster to show various parameters. A multiple versions of that table seem to exist based on the hardware and firmware - AGESA version, socket, cpu, memory type and size. The parameters are located in that table at specific offsets, but the offsets and the structure of the tables are different and I haven't figured out a good way to detect where these offsets are. That AOD table is located in memory and the starting address can be found by parsing the ACPI tables. The fallback is to get the ACPI tables from the registry which sometimes is required on laptops. The other problem with laptops is that most parameters are just missing, not sure if it is only on Lenovo (they seem to use their customized ACPI tables), but I have the same problem on my 6800HS-based Ideapad. Maybe I can use the version of the ACPI table as an identifier, if that changes, but this is not included in the debug logs atm and need to research it first. |
|
I understand, thank you.🥳
…---Original---
From: "Ivan ***@***.***>
Date: Thu, Jan 2, 2025 22:31 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [irusanov/ZenTimings] Can't read MCLK FCLK and UCLK on my 7945hxlenovo computer (Issue #57)
The brief explanation would be that BIOS exposes a table called AOD (AMD OverDrive, I believe, which is the old application name) that is later used in RyzenMaster to show various parameters. A multiple versions of that table seem to exist based on the hardware and firmware - AGESA version, socket, cpu, memory type and size. The parameters are located in that table at specific offsets, but the offsets and the structure of the tables are different and I haven't figured out a good way to detect where these offsets are.
That AOD table is located in memory and the starting address can be found by parsing the ACPI tables. The fallback is to get the ACPI tables from the registry which sometimes is required on laptops. The other problem with laptops is that most parameters are just missing, not sure if it is only on Lenovo (they seem to use their customized ACPI tables), but I have the same problem on my 6800HS-based Ideapad.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
The text was updated successfully, but these errors were encountered: