Thanks for the info, I'll figure some way to integrate that.
Unless we can determine how to distinguish a 209 from a 109 it might
still have to be something which is enabled locally. Martin -- still no
word from QNAP I take it?
I do have some code (in experimental) to ask via debconf when the
On Thu, 2014-01-16 at 08:29 +, Ian Campbell wrote:
Unless we can determine how to distinguish a 209 from a 109 it might
still have to be something which is enabled locally.
It took me about 2s from pressing send to wake up and realise that
stopping the fan in the fan error hook might be the
* Ian Campbell i...@hellion.org.uk [2014-01-16 08:29]:
Unless we can determine how to distinguish a 209 from a 109 it might
still have to be something which is enabled locally. Martin -- still no
word from QNAP I take it?
Unfortunately, I haven't heard from QNAP.
--
Martin Michlmayr
The following appears to work OK in ts209.c:
case 0x73:
/* call_function(fan_error, ); */
{
unsigned char code = 0x30;
serial_write(code, 1);
}
break;
No errors in logs.
The
On 3 January 2014 00:19, Ian Campbell i...@hellion.org.uk 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
On Thu, 2014-01-09 at 09:46 +, Dermot O'Dwyer wrote:
On 3 January 2014 00:19, Ian Campbell i...@hellion.org.uk 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
On Thu, 2014-01-09 at 09:46 +, Dermot O'Dwyer wrote:
On 3 January 2014 00:19, Ian Campbell i...@hellion.org.uk 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
On Sat, 2013-08-17 at 14:05 +0100, Martin Michlmayr wrote:
* Ian Campbell i...@hellion.org.uk [2013-08-15 10:19]:
I have a TS-209 and will try to find the time to check. Unfortuntely,
I cannot remember whether GPIO 44 also works on the Orion models.
Did you have any luck with this?
* Ian Campbell i...@hellion.org.uk [2014-01-03 00:19]:
I suppose you never heard back?
Correct; I'll ask again.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
* Ian Campbell i...@hellion.org.uk [2013-08-15 10:19]:
I have a TS-209 and will try to find the time to check. Unfortuntely,
I cannot remember whether GPIO 44 also works on the Orion models.
Did you have any luck with this?
I sent an email to QNAP a few days ago but haven't received a
On Wed, 2013-07-10 at 15:42 +0100, Martin Michlmayr wrote:
* Dermot O'Dwyer derm...@gmail.com [2013-07-06 02:38]:
It's possible that there is a GPIO e.g. you can distinguish TS-119 from
TS-219 via GPIO 44. Unless you've got a 209 to compare your 109 against
though I'm not sure how to
* Dermot O'Dwyer derm...@gmail.com [2013-07-06 02:38]:
It's possible that there is a GPIO e.g. you can distinguish TS-119 from
TS-219 via GPIO 44. Unless you've got a 209 to compare your 109 against
though I'm not sure how to find out.
Perhaps Martin (CCd) has a 209 and/or can ask QNAP?
On 30 June 2013 15:58, Ian Campbell i...@hellion.org.uk wrote:
In 0.4.2-7+wheezy2 the fan_error function would have been empty, so do
you know for sure it wasn't being triggered previously too?
I reinstalled 0.4.2-7+wheezy2 and added beep to the fan error
function. Got plenty of beeps so it
On Thu, 2013-06-20 at 01:54 +0100, Dermot O'Dwyer wrote:
Package: qcontrol
Version: 0.5.1-3
Severity: important
Tags: upstream
On a TS109, after upgrading from 0.4.2-7+wheezy2 to 0.5.1-3 qcontrol then
reports fan error in syslog and beeping every minute approximately.
How annoying!
Package: qcontrol
Version: 0.5.1-3
Severity: important
Tags: upstream
On a TS109, after upgrading from 0.4.2-7+wheezy2 to 0.5.1-3 qcontrol then
reports fan error in syslog and beeping every minute approximately.
Setting SOUND_BUZZER=no in /etc/default/qcontrol does not stop the beeping.
I have
15 matches
Mail list logo
