Re: TBS driver breaks lirc_serial

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

 



Hi Karim,

Karim schrieb am 21.05.2016 um 23:29:
grep lirc /var/log/syslog
May 21 22:40:05 pctest kernel: [    3.835944] lirc_dev: IR Remote Control driver registered, major 251
May 21 22:40:05 pctest kernel: [    3.836499] rc rc0: lirc_dev: driver ir-lirc-codec (saa716x) registered at minor = 0
May 21 22:40:05 pctest kernel: [    4.402162] rc rc1: lirc_dev: driver ir-lirc-codec (saa716x) registered at minor = 1
May 21 22:40:05 pctest kernel: [    7.364112] lirc_serial: Manually using active low receiver
May 21 22:40:05 pctest kernel: [    7.364198] lirc_serial lirc_serial.0: lirc_dev: driver lirc_serial registered at minor = 2
May 21 22:46:27 pctest kernel: [  388.677309] lirc_dev: module unloaded
May 21 22:48:32 pctest kernel: [  513.779622] lirc_dev: IR Remote Control driver registered, major 251
May 21 22:48:32 pctest kernel: [  513.780127] lirc_serial: Manually using active low receiver
May 21 22:48:32 pctest kernel: [  513.780224] lirc_serial lirc_serial.0: lirc_dev: driver lirc_serial registered at minor = 0

Questions :

1/
There is **2 modules**, but I think it's not a problem because modinfo is OK.
Are you OK ?
It seems to me that there are two rc-devices on receiver cards - rc0 and rc1.
After restart of LIRC only lirc_dev and lirc_serial are running - ok.

locate lirc_serial.ko
/lib/modules/3.2.0-4-amd64/kernel/drivers/linux/drivers/staging/lirc/lirc_serial.ko
/lib/modules/sic/2016-05-20_22:51/3.2.0-4-amd64/kernel/drivers/media/staging/media/lirc/lirc_serial.ko
.. the new one from TBS and a backup - ok.

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):

Mai 22 14:52:10 vdr systemd[1]: Stopping LSB: lirc daemon...
Mai 22 14:52:10 vdr lircd-0.9.0[980]: caught signal
Mai 22 14:52:10 vdr vdr[2522]: [2540] ERROR: lircd connection broken, trying to reconnect every 3,0 seconds
Mai 22 14:52:10 vdr lirc[1024]: Shutting down lircd ..done
Mai 22 14:52:10 vdr systemd[1]: Stopped LSB: lirc daemon.
Mai 22 14:52:12 vdr systemd[1]: Starting LSB: lirc daemon...
Mai 22 14:52:12 vdr lircd-0.9.0[1071]: lircd(default) ready, using /var/run/lirc/lircd
Mai 22 14:52:12 vdr lirc[1044]: Starting lircd (/dev/lirc0)..done
Mai 22 14:52:12 vdr systemd[1]: Started LSB: lirc daemon.
Mai 22 14:52:13 vdr vdr[2522]: [2540] reconnected to lircd
Mai 22 14:52:13 vdr lircd-0.9.0[1071]: accepted new client on /var/run/lirc/lircd

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...

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?

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...

5/
I use Homebrew too.
Could you confirm that parameters must be sent with theses 3 files ?

/etc/lirc/lircd.conf


/etc/serial.conf
/dev/ttyS0 uart none

/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=""
On my system there is no /etc/serial.conf.
Your /etc/lirc/hardware.conf could be somewhat that /etc/sysconfig/lirc is on my system.

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