Jump to content
HWBOT Community Forums

Leaderboard

Popular Content

Showing content with the highest reputation on 01/07/20 in all areas

  1. Hello everyone! Long story short, someone developed an app called AsusZenStates, originally meant to give the user control over P-States on first gen Zen CPUs, with some additional options. It was ASUS motherboards only. However, he doesn't support it anymore and made it open-source. I've made an own fork and now trying to support it for all Ryzen generations and for all motherboard vendors. Since Zen2 launch things have changed significantly in the way some things are controlled through the SMU and MSRs. The lack of meaningful public documentation from AMD side makes it really difficult, especially for a person like me. I'm a front-end developer and don't have much experience with C#, let alone bios development for desktop, although I've had some personal projects for android kernels and co. So I'm trying to do my best, but all I've done so far is mostly reverse-engineered. I still haven't figured out how to control PBO limits (perhaps scalar doesn't work with all motherboards either), so some of the controls are currently disabled. "SMU Power Limits" is also blocked by AMD (the command to disable the feature gets blocked), so this control is disabled as well. Additionally most of the things are SMU/AGESA version and CPU gen dependant, so there might be some logic errors in the code regarding this. I've quickly made a small website, which fetches currently released version. If someone is willing to help with the development and testing, please let me know. Download the app and test it (VID control only works if you use Auto or Offset mode for voltage, but that's to be expected). I will later write a little more info about different CPU generations and features available. Unfortunately I only have access to Ryzen 5 3600 and Ryzen 7 1800X with Crosshair VI Hero (X370) and Asrock B350 K4 (B350). In order to test other combinations I would need to burn more money and buy a Zen+ CPU and next gen motherboards. There are also differences between different vendors. Download: https://zenstates.protonrom.com/ Source: https://github.com/irusanov/ZenStates Current version: 0.8.0-beta3 PS: Also, if someone needs the source of the simple "website", feel free to request it. It's IE-friendly, uses bootstrap for the layout and I've setup a nodejs project for it to automate the build process with sass to css compilation, js transpiling and optimizations.
    2 points
  2. Thx all for the great participation, a handful of new records, on old hardware is always amazing. Congratz to the winners; Australia and the runner ups Germany and Italy.
    2 points
  3. Why add a bench that has vendor lock-in? Wait until it runs on AMD I would say... It's not like we're short on good 3D benches
    2 points
  4. Bad cold is bad cold, SP32 takes more than CPU freq.
    1 point
  5. Received! Everything is in great shape! Good packaging!
    1 point
  6. You can choose the cooling if you want to only check enthusiast scores. Just select the cooling at the top of the table as shown above. If you're wanting seperate points pools then I'd anybody thinks people cheating with their cooling is bad now it would become 100 times worse in my opinion.
    1 point
  7. Not being able to get all the missing bits needed to fix the ZenStates app for all supported CPUs I've developed a debug tool to help me test them easier. It started as an internal tool, but grew up and is now available to the public, hoping that it will help me understand things better. TL;DR - Skip to How Can You Help Semi-technical Info Ryzen uses the so-called SMN Mailboxes. As I understand it is a bit of an extension of the standard PCI communication protocol. Basically using special registers/ports for index/data and a set of custom commands for communicating with the SMU (System Management Unit). There are 2 types of commands - "read" which doesn't require a parameter and "write" which sets certain parameter by sending a value to the SMU with the corresponding command. ZenStates and SMUDebugTool use OpenLibSys and WinRing driver for the PCI read/write operations and wraps the SMU read/write around them. There are 3 addresses (+ a pair of standard PCI index/data ports): - MSG Address: Where the Command ID is sent to - RSP Address: Holds the status of the function execution - ARG Address (+5 more, but only one is used): Read the result of a function or where you send the parameter value if the command is of type "write" The workflow for sending a command is as follows: The RSP register is first reset (set to 0), the argument is written to the ARG address and at last the command ID is sent to the MSG address. To check for successful execution you poll the RSP address until a status is returned (0x1 for success, but there are other status coded). If succeeded, you can now read back the ARG address which holds the result. Problem The biggest problem is there's no public documentation for this. Different generations have different addresses and/or commands. SMU version, socket type and CPUID also matter. Throw an ES CPU in the mix and things get even uglier. What I see is AMD kind of unified the 3rd generation and they are more similar than different, but older gens are all over the place. The other problem is to find which commands (IDs) are supported and what their function is. More about the tool It's all manual. The tool detects CPUID and based on that preloads a set of addresses that I *think* would work. It has 3 tabs for now - SMU, PCI and Info. Will add MSR later. 1. SMU Used to test the workflow described above. [Reset] button loads the default set (detected on startup). Scan attempts to find usable mailboxes, which then can be tested with the textboxes on the left and [Send] button. 0x1 command is "Test Message", 0x2 is "Get SMU version". Both are perfectly safe and are the only ones that are always the same for all generations. On the sample screenshot I've first clicked on [Scan] button and then sent 0x6E which for Matisse is returning the maximum (fused) boost frequency. 2. PCI This is no more than a wrapper using the standard PCI write/read. The PCI register is read with [Read] button and the value then displayed in the second field. [Write] button obviously does the opposite - writes the value/config back to the register. On the screenshot I've read the PROCHOT status. This (PCI read/write) can be used on all systems, not just on Ryzen. MSR will be cross-platform as well. 3. Info Displays a basic system info. I'm most interested in the [Export] button. It generates a JSON file, containing the displayed information and also runs the SMU scanner to add the addresses. The file is saved in the same directory where the tool is. A report from my system looks like this: { "CpuId": "870F10", "CpuName": "AMD Ryzen 9 3900X 12-Core Processor", "MbVendor": "ASUSTeK COMPUTER INC.", "MbName": "CROSSHAIR VI HERO", "BiosVersion": "7704", "SmuVersion": "46.54.00", "Mailboxes": [ { "MsgAddress": "0x03B10524", "RspAddress": "0x03B10570", "ArgAddress": "0x03B10A40" }, { "MsgAddress": "0x03B10528", "RspAddress": "0x03B10574", "ArgAddress": "0x03B10A60" }, { "MsgAddress": "0x03B10530", "RspAddress": "0x03B1057C", "ArgAddress": "0x03B109C4" } ] } How Can You Help - Download the app from my github: https://github.com/irusanov/SMUDebugTool/releases - Extract and run it (might need elevated privileges - "Run as admin" if you get WinRing initialization error) - Click the [Export] button in Info tab and share the output here (or where deemed appropriate) Although it seems to be running without issues, I have one report that the scan feature causes BSOD on one Epyc ES, so be aware there's such possibility. As always, I'm not responsible for any induced damage, you run it entirely on your own risk 😛 It seems ZenStates is not that interesting to the community, but I'd be glad if more people participate, so I can collect more data for different systems and CPU generations. Thanks in advance!
    1 point
  8. Thanks guys! Just participating in the Great 2020 Sandbag Yourself Challenge brought to you by stupidcheaters@hwbot.org
    1 point
  9. Fortunately this CPU is still in the hands of someone who can make proper use of it. As far as I know Boris had a long wait to use it in a Country-/Team-Cup someday. So the least I/we could do was to give it a shot in this years cup. Even it was cascade only due to the lack of ln2. Oh yeah. Was a great pleasure to touch this hardware again after so many years. Felt like coming home... Wish all of you a good start in 2020!
    1 point
  10. Wango Tango I Overclocko!! We should rock the HWBot forums more often. Good tunes!
    1 point
  11. Fucking awesome. I love UFO. Movie in first vid was Vanishing Point BTW.
    1 point
  12. Does anyone have the awardfabrik wprime tweaker?
    1 point
  13. I still wonder how the OC scene would be if points were never implemented.... The day that many used to overclock for fun.... It's never been about points to me... hell i barely post subs.. thats what hwbot is about... why not just remove the points? Any slackers going to CES?
    1 point
  14. We have a secure forum now but pretty much all threads before late 2018 are unusable, it's a real shame (I know it was necessary and appreciate the dev work put into the site, it's just a real shame how much got deleted)
    1 point
  15. Some more electro music for the haters 😅
    0 points
×
×
  • Create New...