• Content Count

  • Joined

  • Last visited

Community Reputation

11 Good

About cakes044

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That’s right. I remember the ipmi2json not being quite smooth had to do some manual switches to get it to work. Once the board.json is configured the ipmifan will just work fine now 👌🏼 Glad to see it working
  2. Hi All, Here is the forked repo with the details of my "fix", keep in mind this is only for X570D4U and X570D4U-2L2T users, I purposely didn't include this to be backwards compatible because I didn't have those boards to do the proper testing or the time to make this backwards compatible. This is the commit in question that has my "fix", I also fixed some minor bugs with the shell commands: I can't quite remember if the ipmi2json script works flawlessly or not, I may have hacked in some va
  3. Sorry I never posted my actual solution ages ago, I was actually going to fork the plug-in and submit a PR but I thought the author was going to do it. Ill post my changes that have a working solution for these boards later in the day, essentially it was a change to the ‘ipmi2json’ and the ‘ipmifan’ scripts.
  4. Yeah totally, these kinds of things are expected but you do get a board that has all the bells and whistles that are not being offered in other boards for this price. If it gives you any confidence my friend has been using the 2L2T with no issues so far with Unraid. So fingers crossed most of the major bugs have been ironed out No worries, was happy to help. 👍
  5. Might be late to the party but everything has been working fine on this board with Unraid apart from all the IPMI fan stuff which I hacked together a solution that you can see in that post. There is actually a bug on this board that you may not have noticed yet, but RX traffic on the network adapters with the specific version of the firmware/BIOS is actually degrading the network performance to 1/3 of the speed. Again, only on RX. I have already raised this issue with Asrock Rack and they have confirmed the issue with a specific AMD driver combination after many many em
  6. FWIW, I was being facetious when I said "hacked" around, was meaning that I dug into the code and figured out a way to do it just not clean yet. This is the result of that command by the way: root@tower:~# dmidecode -qt2|awk -F: '/^\tProduct Name:/ {print $2}' X570D4U So, I made the ipmi2json script generate the correct json object and then modified the ipmifan tool as well to run with the correct commands. There are some caveats and changes to the way this board needs to run. 1. Fan needs to be put in "manual" mode before the values will act
  7. Okay I hacked around the source code of the fan tools all day and got a working version of it for this board 🎉 Happy to clean it up and submit a patch to the github page. Will have to wait till this weekend though when I have some time just a few different things required for this board.
  8. OKAY Good news! Got back correct command from Asrock. On this specific board, the commands are slightly different and has 16 fan duty options: Set fan to manual mode: ipmitool raw 0x3a 0xd8 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 Set fan to auto mode: ipmitool raw 0x3a 0xd8 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Set fan duty to 100 the valid values are 14h to 64h (20% - 100%): ipmitool raw 0x3a 0xd6 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x
  9. Conversation going with ASRock right now about it, just going back and forth, so will 100% tell you the results in here when its all done. 👍
  10. I wouldn't try anything like that Yeah not gonna do that and brick my motherboard I think we’re dead in the water without the correct raw commands, hopefully ASrock get back to me soon and I’ll submit a patch/issue to the GitHub plugin page and refer it back here with the update.
  11. I usually alway update the bios and bmc if there's an update. I guess if depends on the release notes of it's worth it. Yeah I could always update with the 2L2T version of the board: Which AFAIK is identical to my one except the 10GB NIC. Just unsure if there are anythings in the firmware that could brick my board, I'm not too familar with the BMC side of things, I would assume that the firmware is separate to the board.
  12. Maybe try ipmitool. Could be a freeipmi problem. Also is the bmc firmware up to date. Yeah tried that with the same results, well the thing is, this is a brand new board and I dont have any drivers to downloads at the Asrock website: Never had a BMC board before, is updating the firmware on the BMC wise if not specified by the manufacturer? Might also help to see the output of the sensors and the fans: root@tower:~# ipmisensors -t fan ID | Name | Type | R
  13. Yeah I've tried the dual CPU commands and no results. Yeah all Noctua PWM fans. Here is the output of trying to send the command via the terminal: root@tower:~# ipmi-raw 00 3a 01 00 00 00 00 00 00 00 00 --debug ===================================================== OEM - Unknown Request ===================================================== [ HEX DUMP ..... ] = HEX[ 9B] [ 01h 00h 00h 00h 00h 00h 00h 00h ] [ 00h ] ===================================================== OEM - Unknown Response ===================================================== [ HEX DUMP ..... ] = HEX[ 2B] [
  14. You are probably correct that the ipmi commands may be different for this board. I would need the correct commands to make it work. I have emailed Asrock support on this to see what the correct commands are, doesn't look like their official guide over here is correct for my board: Are there any ways I can figure out the raw commands to use via the ipmitool that you are aware of? I haven't had much luck searching for that answer, I'm more than happy to debug this at a lower level if I knew where to look.
  15. Hey mate! Just trying to use this plugin and getting the "fan is not configured" messages when trying to run the "Configure" button. If I were to guess, the ipmi raw commands that the plugin is running behind the scenes aren't compatible with this for some reason? As per below: I'm unsure as to what is going on here, its a brand new board which is probably running into some new compatibility issue with ipmi maybe? Motherboard: Asrock Rack X570D4U Anything that I can try to debug this further? Or a anything else I can provide? Othe