Bug#712841: A bit late, but still an issue...

2018-04-22 Thread Axel Sommerfeldt
On Thu, Apr 19, 2018, at 12:47, Martin Michlmayr wrote:
> * Axel Sommerfeldt <axel.sommerfe...@f-m.fm> [2018-04-16 21:25]:

> Based on Ian's comments, I added a has_fan to the configuration file.
> I believe the attached patch should do the trick.
> 
> Axel, can you test this (after restoring the original config).

Looks good to me. Right after patching:

Apr 22 11:40:26 qnap systemd[1]: Started LSB: Start qcontrol daemon.
Apr 22 11:40:26 qnap qcontrol[338]: qcontrol 0.5.5 daemon starting.
Apr 22 11:40:26 qnap qcontrol[338]: Register evdev on 
/dev/input/by-path/platform-gpio_keys-event
Apr 22 11:40:26 qnap qcontrol[338]: confdir: loading from /etc/qcontrol.d...
Apr 22 11:40:26 qnap qcontrol[338]: System status: start
Apr 22 11:40:30 qnap qcontrol[338]: ts219: temperature 55
Apr 22 11:40:30 qnap qcontrol[338]: ts219: temperature 55 setting fan to "high"
Apr 22 11:40:37 qnap qcontrol[338]: ts219: fan error
Apr 22 11:41:27 qnap qcontrol[338]: ts219: fan error
Apr 22 11:42:17 qnap qcontrol[338]: ts219: fan error

And after setting "has_fan" to "false":

Apr 22 11:44:26 qnap systemd[1]: Starting LSB: Start qcontrol daemon...
Apr 22 11:44:26 qnap qcontrold[323]: Starting qcontrol daemon: qcontrol.
Apr 22 11:44:26 qnap systemd[1]: Started LSB: Start qcontrol daemon.
Apr 22 11:44:26 qnap qcontrol[333]: qcontrol 0.5.5 daemon starting.
Apr 22 11:44:26 qnap qcontrol[333]: Register evdev on 
/dev/input/by-path/platform-gpio_keys-event
Apr 22 11:44:26 qnap qcontrol[333]: confdir: loading from /etc/qcontrol.d...
Apr 22 11:44:26 qnap qcontrol[333]: System status: start
Apr 22 11:44:30 qnap qcontrol[333]: ts219: temperature 55

> > the temperature gets hot and make a beep (and a red blinking status
> > led) if it gets too hot!?
> 
> Maybe, although the fanless devices are designed to work without a fan
> so this shouldn't happen.  But what would you consider "too hot"?

I have no idea what max. temperature the qnap can handle. Maybe 70? Maybe it 
should not beep but at least change the status of the status led? Or change the 
status led at 70 and beep at 75? (But this is only clueless guessing of mine.)



Bug#712841: A bit late, but still an issue...

2018-04-16 Thread Axel Sommerfeldt
On Mon, Apr 16, 2018, at 20:12, Martin Michlmayr wrote:

> Axel, can you restore the original config and 1) see if you get the beeps
> and 2) whether running
> 
> qcontrol fanspeed stop
> 
> makes them stop. (change setfan in the config to do nothing, otherwise
> the fan will be turned on again)

1) Done
2) "qcontrol fanspeed stop" makes the beeping stop

> Do you know if /etc/default is Debian-specific or generic?

It's not part of the Filesystem Hierarchy Standard (3.0) but at least I can 
confirm that this directory exists in CentOS and Fedora, too, containing the 
files "grub" and "useradd".

> As a workaround, until this is fixed, users can create a file
> /etc/qcontrol.d/90_no_fan with:
> 
> function fan_error(  )
> end
> 
> function setfan( temp, speed )
> end
> 
> I believe this should work but is completely untested. (Alex,
> Christian, maybe you can test after restoring the original config.)

Creating /etc/qcontrol.d/90-no-fan.conf with the content above makes the 
beeping stop, too.

Log:
Apr 16 21:08:59 qnap-backup qcontrol[330]: confdir: loading from 
/etc/qcontrol.d...
Apr 16 21:08:59 qnap-backup qcontrol[330]: confdir: including 
/etc/qcontrol.d/90-no-fan.conf

Maybe it's a good idea to overwrite the temp() function in 
/etc/qcontrol.d/90-no-fan.conf, too? It could create a log entry if the 
temperature gets hot and make a beep (and a red blinking status led) if it gets 
too hot!?



Bug#712841: A bit late, but still an issue...

2018-04-14 Thread Axel Sommerfeldt
Just a reminder that this bug is still a thing. And yes, the model can be found 
in uLinux.conf:

root@qnap119:~# mount -o ro -t ext2 /dev/mtdblock5 /mnt
root@qnap119:~# more /mnt/uLinux.conf 
[System]
Model = TS-119
Internal Model = TS-119
...

BTW: Martin, thanks a lot for all the work. Having Debian on a qnap really 
rocks.



Bug#609716: installation-reports

2011-01-11 Thread Axel Sommerfeldt
]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [E]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

For installation I simply copied the installation iso image with dd to
the usb stick, and booted from this stick afterwards. The installation
itself went fine, but afterwards I had an entry in /etc/fstab where
/dev/sdb1 (= the usb stick) was linked to /media/cdrom0 and the real CD
rom drive was linked to /media/cdrom1. But the usb stick shouldn't be in
/etc/fstab at all and the CD rom drive should have been linked to
/media/cdrom0 instead.
-- 
  Axel Sommerfeldt
  axel.sommerfe...@arcor.de




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#432517: (fwd) Bug#432517: Just upgraded from tetex to texlive. Latex package caption no longer works

2008-11-30 Thread axel . sommerfeldt
Dear Hilmar and Arthur,

The caption package is only adapted to specific document classes which
are listed in the caption package documentation, section Document
classes  Babel support. The aastex document class is not on the list.

But since I changed the name of the command \captionbox to
[EMAIL PROTECTED] in version v3.1f (2007/11/11) to avoid incompatibilities
with existing \captionbox definitions, newer versions of the caption
package hopefully make less trouble when used with the aastex document
class.

In fact the example below compiles fine when using the actual version
v3.1j (2008/08/24) of the caption package. (It results in the warning
Package caption Warning: Unsupported document class (or package)
detected, usage of the caption package is not recommended. See the
caption package documentation for explanation. but this is OK and
documented.)

Warm regards,
Axel


On Sat, 29 Nov 2008 23:04:11 +0100, Hilmar Preusse [EMAIL PROTECTED]
said:
 Dear Axel, dear Arthur,
 
 down here in the Debian Bug tracking system we got bug report a while
 ago. It tells that the compilation of documents fails after upgrading
 to TL 2007. The minimal example is:
 
 \documentclass{aastex}
 \usepackage[labelformat=simple]{caption}
 \title{Test}
 \author{Author}
 \begin{document}
 \maketitle
 \begin{abstract}
 abstract
 \end{abstract}
 \section{section 1}
 bla bla
 \end{document}
 
 It fails with the error message: \captionbox already defined.
 
 Note that not a standard class is used but the American Astronomical
 Society format, which seems to contain an own definition of
 \captionbox. When using the standard article class the problem
 disappears. Hence I guess it is the fault of the fault of the aas
 class.
 
 Please discuss this topic and provide a possible approach how to
 solve the problem.
 
 Thanks,
   Hilmar
 -- 
 sigmentation fault



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]