spl147

seems to work perfectly

yes and the override thresholds follow the spun down sensor

Whats Bizarre is the fact that everyone just expects every board with any config to work. if any/all did any homework on the Fan Speed plugin you would have seen that it is BETA for 1 and for 2 it relies on HWMON support and HWMON is not all encompassing nor is it complete! hense why people have written plugins to add support for chips not yet supported by HWMON. no one bothers to check that the board they build with has the proper driver support for their intended purpose.

@SimonF can we get a update on this please? start there till the end

Driver `to-be-written': * ISA bus, address 0xa30 Chip `ITE IT8613E Super IO Sensors' (confidence: 9) Note: there is no driver for ITE IT8613E Super IO Sensors yet. Check https://hwmon.wiki.kernel.org/device_support_status for updates.

from terminal run sensors-detect and post output

Any updates on the seperate thersholds for HDD and CPU?

if you did your homework you would have your answer. on unraid open the terminal and run sensors-detect to see if your board is supported. post the output

the issue is the fan speed plugin zip file gets extracted on boot, thats why your changes are overwritten use the user scripts plugin and write a script to replace that line in the plugin with yours. or modify the zip with you changes, then it will persist on reboot

because if the plugin fails, or system crashes you fry the CPU!

CPU Fan should ONLY be controlled by the BIOS! controlling your cpu fan from a plugin is insane! CPU Fan = Bios Array Fan = Plugin

Set min pwm to as slow as you want it to go. Not 0. Usually 80-100 works well

Is you min. fan speed set to 0?

The min pwm value determines how slow the fans go, set it to the lowest speed you want when drive are spun down. as for the cpu, the cpu fan should always and only be controlled by the bios! It has a seperate header for a reason!

that is not the place to edit! that is the actual plugin, not the config file. config file is at /flash/config/plugins/ plugin name folder. delete all config files and start over

Screenshot?

So you are gonna rob the dev of income because it doesn’t say stable? ALL software these days is beta! Thats a poor way of thinking!

Just buy a damn key! you guys kill me with this i can not believe there is no new key, i've been using it this way for years! if you used it and the beta key expired, it's time to buy a key! then the program to old issue will go away! it will be a sad day for everyone when makemkv dissapears because no one supports the developers!

Just opened it here, works perfect!

Fork the repo, make changes and install the plugin from your fork, this is not rocket science.

Submit a pull request! You can also edit your version locally

UPDATE: Sorry i didnt realize the author changed the template. I updated to the new template and re created the docker and my drive is passed through properly using the new method (not sure why it is not included in the template) you should be looking in the docker log for the drive assignment, not system devices. below is the relevent info: [cont-init ] 54-check-optical-drive.sh: executing... [cont-init ] 54-check-optical-drive.sh: looking for usable optical drives... [cont-init ] 54-check-optical-drive.sh: found optical drive [/dev/sr0, /dev/sg5], group 19. [cont-init ] 54-check-optical-drive.sh: terminated successfully.

Post the log showing it

It usually happens when sgx changes

Have you passed through both /dev/SRx and /dev/SGx