Jump to content

dmacias

Community Developer
 View Profile  See their activity

  • Posts

    2,803

  • Joined

  • Last visited

  • Days Won

    6

 Content Type 

Everything posted by dmacias

  1. dmacias
    What are the variable on the NUT details page in settings? What UPS?
  2. dmacias
    It's in the first post and it's available in CA
  3. dmacias
    If you don't wanna wait. You can install pip. Then run pip install setuptools --upgrade and the pip install docker-compose --upgrade
  4. dmacias
    Try running just pip3
  5. dmacias
    Yes. I'm about 90% done. Just working on manual server selection and some backwards compatibility. I think this is important because I have found a couple servers close to me that consistently give higher results than my connection. They are consistent results but double my connection. Although in testing this past week those were not selected and all results were consistent and inline with my connection. Also python is not necessary. This one is written in C.
  6. dmacias
    Finally got around to working on a new version using a different script I compiled for unRAID thanks to EmeraldPi https://github.com/taganaka/SpeedTest You can install this package using wget and installpkg from the command line https://github.com/dmacias72/unRAID-speedtest/raw/master/packages/SpeedTest-1.14-x86_64-1.txz Then run SpeedTest to test this script
  7. dmacias
    I'll look into it. It could just be a nut problem with this ups.
  8. dmacias
    What, no X10s? I'll see if I can implement the ole hi, med, low I had started before for the X9s
  9. dmacias
    That sucks. Where'd you get that info or did you test on an X9SCM-F or similar?
  10. dmacias
    First make sure your BIOS and BMC are on the latest firmware. Are your fans 4pin pwm fans? For missing FANA, check the Settings page under Display settings and Global available sensors and make sure FANA is checked. You also need to use the Sensor Config editor to change your fan thresholds. Check back through the thread around 2018/05/20 is when I implemented fan control for X9 boards.
  11. dmacias
    I assume you have it shutdown based on time on battery. What time did you set it to? If you have a monitor hooked up, watch the console when that time expires and see if it's starting shutdown.
  12. dmacias
    I updated a few c compiler packages and added a few. Also updated glibc to add a couple missing files. The files with o extensions (e.g. crtl.o) in /usr/lib64. You'll need to deselect glibc, apply then reselect and apply
  13. dmacias
    Sorry for the late reply. I would set FAN1234 to CPU temp and FANA to hard drive temps.
  14. dmacias
    I was refering to adding an override to the plugin settings. Latest update provides an override for virtual machines.
  15. dmacias
    I think I got it fixed. Updated plugin and added delay after full fans. I think the first fan control commands were happening too soon after full fan commands and not taking. So fan speeds weren't changing on script start and eventually changing on the next poll when the temp changed.
  16. dmacias
    Thanks for the info. I looked back through the releases and lbzip2 was included in 6.6.0. I have removed it from the 6.6 repo
  17. dmacias
    I was wondering if your BRNAME was actually capitalized as BR0? It may have an affect on the python script and command line. While unRAID is case sensitive, maybe the python script doesn't handle it well. You had mentioned earlier running the command line and using br0 and it worked.
  18. dmacias
    Interesting. My X10 and now X11 would only take multiples of 100. Have you checked if your bios is up to date and bmc? Just curious if that's the norm for the X9 boards.
  19. dmacias
    I'll update in a little bit. I fixed the error reporting. But here's the command. You'll have to edit the file manually too usr/sbin/ipmi-sensors-config --filename=/boot/config/plugins/ipmi/ipmi-sensors.config --commit
  20. dmacias
    I cannot find any emacs with no X available for slackware
  21. dmacias
    Sorry this requires too many packages for this plugin
  22. dmacias
    For whatever reason I could never get the writing of a bad config to come back as an error. It's not saving because it doesn't like the value you are using for the lower threshold. If you were to run the command from the command line you'd see the complaint. What values have you tried? Try only numbers like 300, 400, 500
  23. dmacias
    You can add this to the plg install chmod +0755 /usr/local/emhttp/plugins/dynamix.cache.dirs/scripts/* Or create an "install" directory within the dynamix.cache.dirs.txz package and place a doinst.sh file with that command in the install directory. That's the way all slackware packages handle permissions and other install functions. E.g. This is from NerdPack doinst.sh #!/bin/shln -sf /usr/local/emhttp/plugins/NerdPack/scripts/packagemanager /usr/sbin/packagemanagerchmod +0755 /usr/sbin/packagemanager
  24. dmacias
    virbr0 would not work. The script monitors all packets looking for wol packets on the bridged network for your VMs. It gets the bridge name from BRNAME in /boot/config/domain.cfg. Do you have that variable in the domain.cfg? Maybe that variable isn't set anymore? Do you have bridging enabled in network settings?
  25. dmacias
    Is the VM stopped or paused? It has to be shutdown or hibernated. It can't be sleeping or in any other state. I would stop the service. Then run "ps aux | grep libvirtwol". To make sure another instance isn't running then start the service and run that again. You can also run manually /etc/rc.d/rc.libvirtwol start/stop. You should see /usr/bin/python /usr/local/emhttp/plugins/libvirtwol/scripts/libvirtwol.py br0 running. Edit: also is your bridge named BR0 or br0? Could make a difference. The service gets this from /boot/config/domain.cfg
×
×
  • Create New...