Markus Meissner

hope you like it!

Generally this seems to be an issue with the watchdog component: if any path within the chosen directory is not readable for the current user, this exception will be raised....

how about a circular buffer

I've seen exactly the same behavior with my UV32VD zenbook and have to the slightest idea why this is happening, in fact, and I've also looked into this earlier, simply...

fix merged, thank you @savisitor15

ok, took some time, but at least have some ideas/clarifications: * [line 976](https://github.com/daringer/asus-fan/blob/eed0b68b33fc6ca9e0a58622214edeeb45c5042d/asus_fan.c#L976) is likely not causing problems, this is just my fail as I originally thought it is possible...

Can you please also show me the dmesg output (of the debug-build-module) after you tried to `insmod asus_fan.ko` *without* `force-load=1`, there we maybe see what fails... further acpi_call is under...

uh, ok so there I see a dmesg message without `force-load=1` ... ok so loading of the module seems fine, for acpi, see this [post](https://github.com/daringer/asus-fan/issues/39#issuecomment-264635950) there you see what to...

you should try it directly being root, and with "".... ``` $ sudu su $ echo "\_SB.PCI0.LPCB.EC0.SFNV 0" > call $ cat call; echo 0x0called ``` This should be the...

Sounds like this is a clear candidate to be exposed using asus_fan ...