Re: TBS driver breaks lirc_serial

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

 



Hi Karim,

Karim schrieb am 25.05.2016 um 00:24:
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.
You do not need journalctl, because your system is no systemd-system obviously.
On my system there is no syslog or other logfile in directory /var/log :)

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 /var/run/lirc/lircd
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 /var/run/lirc/lircd
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
nothing.
Strange...

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 :
/lib/modules/3.2.0-4-amd64/kernel/drivers/media/
/lib/modules/3.2.0-4-amd64/kernel/drivers/staging/media/

(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.
It is not important in which directory structure the modules are installed.
But it is important, that you have no mixture of modules, that are build from different configurations
or that are incompatible in any other way. The package from TBS install its own version of v4l (Video4Linux)
and your system should use only these modules, not the originals or both of them.
Normally you will not need backups, but to have it is better :)

Maybe it is a good idea to reinstall your Debian system to be sure, that all modules are clean.
Than create a backup of the entire modules tree (/lib/modules/*) and install TBS stuff without deleting any directories.
After that you are able to compare the mixed modules to the backup (diff -Nqr /lib/modules /your.backup) and find out,
what you should delete before installing TBS.

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"
LIRCD_LISTENPORT=
LIRCD_CONNECT=
vdr:~ # find /etc -name 'lirc*'
/etc/lirc
/etc/lirc/lircd.conf
/etc/init.d/lirc
/etc/sysconfig/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
#START_LIRCMD=false

#Don't start irexec, even if a good config file seems to exist.
#START_IREXEC=false

#Try to load appropriate kernel modules LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER=""
# 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=""
LIRCMD_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 ?
Debian and OpenSUSE are different. Logging is different, configuration is different, ... but both are linux :)
Do you have an old system with running DVB and LIRC? If so, try to find the LIRC configuration...

I do not know Debian and which version is stable or not.
But why not - "latest is greatest" :)

Best regards
Andreas Böttger


_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr




[Index of Archives]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Big List of Linux Books]     [Fedora Users]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux