On Thu, 2014-01-09 at 09:46 +0000, Dermot O'Dwyer wrote:
> On 3 January 2014 00:19, Ian Campbell <[email protected]> wrote:
> > Dermon, does commenting out the content of temp_high and temp_low in
> > qcontrol.conf and rebooting still end up with fan_error getting called
> > lots?
>
> Yes, fan_error still gets called when there are empty temp_high and
> temp_low functions.
I suppose there are few other things which could be tried if you are
able, there are some #defines for PIC commands relating to fans in the
QNAP kernel headers which are not currently used by qcontrol:
include/qnap/pic.h:#define QNAP_PIC_FAN_STOP 0x30
include/qnap/pic.h:#define QNAP_PIC_FAN_ENABLE 0x71
include/qnap/pic.h:#define QNAP_PIC_FAN_DISABLE 0x72
(these aren't used elsewhere in the kernel, so I can't see how qnap's
firmware uses them -- I guess this header is consumed by their
userspace)
Probably the easiest way to test these is to edit ts219.c and where
there is:
call_function("fan_error", "");
instead add (untested):
{
unsigned char code = 0x30;
serial_write(&code, 1);
}
Try this for 0x72 as well. I don't imagine 0x71 would be much use.
Hrm... qcontrol could really use a way to send arbitrary bytes to the
PIC from LUA code.
Ian.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
