• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About imthekuni

  • Rank


  • Gender

Recent Profile Visitors

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

  1. I did a little bit of troubleshooting in the meantime. I noticed that ipmisensors just pulls info from the ipmi.cfg file and passes it to /usr/sbin/ipmisensors via: [ $NETWORK == "enable" ] && OPTIONS=" -h $IPADDR -u $USER -p $(echo $PASSWORD | base64 --decode)" That is when I noticed it is expecting the password to be coded as base64. If I code my PW as base64 it prevents the "base64: invalid input" error I saw earlier. However, I still get the "/usr/sbin/ipmi-sensors: connection timeout" error. If I call /usr/sbin/ipmi-sensors directly I see all the correct info, but for some
  2. Likewise just throws that base64 error. root@Tower:~# /usr/sbin/ipmisensors base64: invalid input /usr/sbin/ipmi-sensors: connection timeout Much appreciated, I will try and figure out how to convert it to the shell script as well.
  3. I recently noticed that the Controlr plugin is stopped. Disabling and enabling it will set the status to Running for a short while, but then it will switch back to stopped after a few seconds. The controlr.log is: I: 2020/12/20 15:52:51 app.go:58: controlr v2020.05.09|2.19.0 starting ... I: 2020/12/20 15:52:51 app.go:66: No config file specified. Using app defaults ... I: 2020/12/20 15:52:51 app.go:171: host( I: 2020/12/20 15:52:51 core.go:81: starting service Core ... I: 2020/12/20 15:52:51 core.go:307: Created ipmi sensor ... I: 2020/12/20 15:52:51 c
  4. What exactly is the problem? The fan speed is not "locking" in to what you entered? Fans are always spinning high? They are ramping up and down? Depending on the system fan model, the optimal setting of 30% PWM could be around 4k rpm (~13k max rpm. I think the original server fans spin pretty fast/loud. Might have to upgrade to slower/quieter ones like the Noctua NF-A8 PWM (2200 max rpm) May run into the ramping issue when switching. I found this guide ( to be the easiest to follow and may help with the rampin
  5. Might be a long shot, but if you have an extra SSD, or can get one cheap, you could boot Windows off that to debug the board
  6. Someone can correct me if I'm wrong, but I think docker containers must run some *nix OS. Unfortunately it does not look like MSI makes a compatible application (Windows only) which limits you to a VM, however I am not sure if it possible to access SuperI/O from a VM...
  7. Darn. I was hoping since your MB has the same SuperI/O chip that it would just work. I tried looking at the source code, but it is a little over my head at that point.
  8. Oh yes, should have mentioned this. It should default to docker-msi-rgb. I did have another docker container called msi-rgb that I have since deleted, so be sure to install docker-msi-rgb
  9. Oh, you'll have to get into your docker container first. So once you're logged into the server (telnet, ssh, or webgui terminal): docker exec -it docker-msi-rgb bash
  10. Its a little janky (I am not the best at making docker containers) but hopefully it works! You should only need to set the docker to privileged. No need to open ports, variables, etc. Not as user friendly as an app with a GUI, but hopefully useful enough that you don't have to constantly run a VM. Also, there is probably a way to have the code run on restart so that the lights are set if you ever reboot your unraid server
  11. So I was curious and I made Docker container that has a linux utility to adjust RGB on MSI motherboards. Possible it will work on yours. Give it a shot, just search for my name (imthekuni) on the community app store, it won't show up so search Docker Hub from the link, and install docker-msi-rgb. Install as a privileged docker. You can then telnet or ssh into your server, or if you are on 6.4, you can use the terminal from the web GUI. To change color settings: For Green /msi-rgb/target/release/msi-rgb 00000000 FFFFFFFF 00000000 For Heartbeat /msi-rgb/target/release/msi-
  12. A cursory Google search is not providing much. Not sure you can access the chip required to control RGB through a VM, but you might be able to get away using this tool and creating a docker container for it?
  13. This may be a stretch, but could you somehow pass RGB through to VM? Does it show up as a separate IOMMU group? (Tools > System Devices)
  14. RT-AC56U with stock firmware. At this point in my life I just need something that works!
  15. I just picked up 2 of these for my Dell H310 and they work like a charm.