[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#933294: marked as done (QNAP TS-109 (orion): ttyS / PIC communication fails)

Your message dated Sun, 27 Nov 2022 16:47:44 +0100 (CET)
with message-id <20221127154744.0F5DABE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #933294,
regarding QNAP TS-109 (orion): ttyS / PIC communication fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
933294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933294
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qcontrol
Version: 0.5.6-4~bpo9+1
Severity: important

Greetings, package maintainer!

I am running a QNAP TS-109 NAS on Debian, and post installation I noticed that qcontrol seemed not
to work properly: the NAS does not beep post-boot, and the status led stays red/green blinking.

Trying to use qcontrol directly outputs no error, but does nothing:
---8<---
root@vault:~# qcontrol --direct statusled greenon
Register evdev on /dev/input/by-path/platform-gpio-keys-event
confdir: loading from /etc/qcontrol.d...
(no led change)
root@vault:~# qcontrol --direct buzzer short
Register evdev on /dev/input/by-path/platform-gpio-keys-event
confdir: loading from /etc/qcontrol.d...
(no buzzer sound)
---8<---

It looks like it might be a kernel-related problem, as I can see in dmesg:
---8<---
root@vault:~# dmesg|grep gpio
[   21.616406] synth uevent: /gpiochip0: failed to send uevent
[   21.616455] gpio gpiochip0: uevent: failed to send synthetic uevent
[   31.732294] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   34.725122] synth uevent: /gpiochip0: failed to send uevent
[   34.725173] gpio gpiochip0: uevent: failed to send synthetic uevent
---8<---

-- System Information:
Debian Release: 9.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: armel (armv5tel)

Kernel: Linux 4.19.0-0.bpo.5-marvell
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qcontrol depends on:
ii  libc6        2.24-11+deb9u4
ii  liblua5.1-0  5.1.5-8.1+b2
ii  udev         232-25+deb9u11

qcontrol recommends no packages.

qcontrol suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: