Hi Andreas,

> 2/
> I found a problem with lirc (I don't know if there is a relation with mode2 :
> setserial /dev/ttyS0 uart none
> /etc/init.d/lirc start
> [ ok ] Loading LIRC modules:.
> [FAIL] Starting remote control daemon(s) : LIRC : failed!
> You mean lirc or lircd ? (I use lircd in my vdr)
LIRC is a daemon (/usr/sbin/lircd on my system) and /etc/init.d/lirc is the 
script to start this daemon.
If I restart LIRC I see the following in syslog (on my systemd system via 
journalctl -f):

Unfortunately I don't have journalctl, and I didn't afford to install it on 
Debian Wheezy.

Your line "[FAIL] Starting remote control..." means that LIRC has any problem.
Please try to find any other entries in any logfiles that may be related with 
this problem.
This failed start should be visible in syslog...

You've right. But curiously, I didnt find error :

grep lirc /var/log/syslog
May 24 23:01:00 pctest lircd-0.9.0-pre1[4396]: lircd(default) ready, using 
May 24 23:02:00 pctest lircd-0.9.0-pre1[4396]: caught signal
May 24 23:09:01 pctest lircd-0.9.0-pre1[4414]: lircd(default) ready, using 
May 24 23:09:09 pctest lircd-0.9.0-pre1[4414]: caught signal
May 24 23:35:51 pctest kernel: [ 4171.326315] lirc_serial: Manually using 
active low receiver
May 24 23:35:51 pctest kernel: [ 4171.326409] lirc_serial lirc_serial.0: 
lirc_dev: driver lirc_serial registered at minor = 2

grep lirc /var/log/user.log

> 3/
> During workflow, theses commands returns "no file", I don't know if it's 
> normal :
>     mv /lib/modules/`uname -r`/kernel/drivers/media/* $SICDIR/media/
>     mv /lib/modules/`uname -r`/kernel/drivers/staging/media/* 
> $SICDIR/staging/media/
On my system the package from TBS installs in different directories than the 
original modules are.
This way I had a mixture of original modules and modules from TBS. After 
deleting the original "media" subdirs and reinstalling TBS stuff all was ok. 
But if it become necessary to restore the originals you need a backup...
Maybe your system has a different directory structure?

Yes, I think so. I see 2 path :

(I am afraid that if I restore media from backup it erase news modules from 
TBS).Theses points (path and need/or don't need to restore backup) are not very 
clear for me.

> 4/
> I can't check this because "/etc/sysconfig" doesn't exist in my Debian 7.7.0.
> Do you know the path for Debian ?
> vdr:~ # grep '^[A-Z]' /etc/sysconfig/lirc LIRCD_DEV_PERMISSIONS="660"
> LIRCD_DEV_OWNER="root:video"
> LIRCD_DRIVER="default"
> LIRCD_DEVICE="/dev/lirc0"
> LIRC_MODULE="lirc_serial"
vdr:~ # find /etc -name 'lirc*'

Try this on your system...

Unfortunately I didn't find this file :-(

> 5/
> /etc/lirc/hardware.conf
> # /etc/lirc/hardware.conf
> #
> # Arguments which will be used when launching lircd LIRCD_ARGS=""
> #Don't start lircmd even if there seems to be a good config file 
> #Don't start irexec, even if a good config file seems to exist.
> #Try to load appropriate kernel modules LOAD_MODULES=true
> # Run "lircd --driver=help" for a list of supported drivers.
> # If DEVICE is set to /dev/lirc and udev is in use /dev/lirc0 will be 
> # automatically used instead DEVICE=""
> MODULES="lirc_serial"
> # Default configuration files for your hardware if any LIRCD_CONF=""

Your /etc/lirc/hardware.conf could be somewhat that /etc/sysconfig/lirc is on 
my system.

Yes, that's why I did'nt find /etc/sysconfig.

At this time, I think **the point** is to clarify is the configuration file :
path, name and content.

In case I can't find/fix this, do you think it could be interesting to try with 
a fresh install of  Debian Jessie **8.4.0** which kernel 3.16 ?

Thanks again for your support.
Best regards.


vdr mailing list

Reply via email to