[dib0700] ir-receiver inside dvb-usb not working

[avware]

Hi,
 i'm unable to use the IR-receiver inside an USB DVB receiver (Terratec T3). The device is correctly configured:
...
[13565.385801] usbcore: registered new interface driver dvb_usb_dib0700
[13569.785206] usb 2-1.1: new high-speed USB device number 19 using ehci_hcd
[13569.878691] usb 2-1.1: New USB device found, idVendor=0ccd, idProduct=10a0
[13569.878701] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[13569.878707] usb 2-1.1: Product: TerraTec T3
[13569.878712] usb 2-1.1: Manufacturer: TerraTec GmbH
[13569.878717] usb 2-1.1: SerialNumber: 0000000001
[13569.879585] dvb-usb: found a 'Terratec Cinergy T USB XXS (HD)/ T3' in cold state, will try to load a firmware
[13569.883741] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[13570.085838] dib0700: firmware started successfully.
[13570.588887] dvb-usb: found a 'Terratec Cinergy T USB XXS (HD)/ T3' in warm state.
[13570.589013] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[13570.589119] DVB: registering new adapter (Terratec Cinergy T USB XXS (HD)/ T3)
[13570.814960] DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
[13571.039905] DiB0070: successfully identified
[13571.039928] Registered IR keymap rc-dib0700-rc5
[13571.040208] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/rc/rc12/input24
[13571.040409] rc12: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/rc/rc12
[13571.040657] dvb-usb: schedule remote query interval to 50 msecs.
[13571.040666] dvb-usb: Terratec Cinergy T USB XXS (HD)/ T3 successfully initialized and connected.

cat /proc/bus/input/devices
...
I: Bus=0003 Vendor=0ccd Product=10a0 Version=0100
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:00:1d.0-1.1/ir0
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/rc/rc12/input24
U: Uniq=
H: Handlers=kbd event12
B: PROP=0
B: EV=100013
B: KEY=14afc336 284284d 0 0 0 4 80058000 2190 40000801 9e96c0 0 900200 ffc
B: MSC=10

udev rule:
KERNEL=="event*", ATTRS{name}=="IR-receiver inside an USB DVB receiver", SYMLINK+="input/dvb-ir"

Info from Ubuntu reporting guidelines:

1)
root@avware-K53SC:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal

2)
root@avware-K53SC:~# apt-cache policy linux-firmware
linux-firmware:
  Installato: 1.95
  Candidato: 1.95
  Tabella versione:
 *** 1.95 0
        500 http://it.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages
        100 /var/lib/dpkg/status

3)
root@avware-K53SC:~# cat /dev/input/dvb-ir
[..should produces output when i'm pressing buttons on the remote]

4)
root@avware-K53SC:~# cat /dev/input/dvb-ir
[..produces no results when i'm pressing buttons on the remote]

Same procedure with old firmware "dvb-usb-dib0700-1.10.fw" show me the output (from remote input), but repetly (i think for some firmware's bug). This bug is also present in ubuntu precise 12.04.1.

Edit - Dec 11 2012: as suggested, I tested the upstream kernel version

root@avware-K53SC:~# uname -a
Linux avware-K53SC 3.7.0-030700-generic #201212102335 SMP Tue Dec 11 04:47:31 UTC 2012 i686 i686 i686 GNU/Linux

..but no progress, same result

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-raring/

[sander (s-devrieze)]

The problem is the driver sets the wrong remote protocol and there is no way to make the protocol change persistent between reboots (or suspend).

Try the following (this is the way it works for me):
1) Change /etc/lirc/hardware.conf:
REMOTE_DRIVER="devinput"
REMOTE_DEVICE="/dev/input/event14" <-- this line probably needs adaption to your system: check "cat /proc/bus/input/devices"
LOAD_MODULES="true"

2) Change /etc/lirc/lircd.conf:
include "/usr/share/lirc/remotes/devinput/lircd.conf.devinput"

3) Unplug the USB stick after each reboot, otherwise it will not work (at least not for me). This is not needed after suspend.

4) Run a script as root containing these commands:
rmmod dvb_usb_dib0700
modprobe dvb_usb_dib0700
ir-keytable -s `ls /sys/class/rc/` -p nec

5) Run /usr/bin/irexec -d

6) Check if it works by running the command "irw", then press a button on the remote.

Step 4 needs to be done after each suspend.

[sander (s-devrieze)]

Please also not this bug likely is a duplicate of Bug #1035822.

[avware (avwarez)]

Hi sander and thanks for reply. I stopped before using lirc, because I thought a dib0700 driver bug, but I'll try the same.

1) On my system your configuration won't start:
root@avware-K53SC:~# /etc/init.d/lirc start
 * Loading LIRC modules
 * Unable to load LIRC kernel modules. Verify your
 * selected kernel modules in /etc/lirc/hardware.conf

..with hardware.conf: LOAD_MODULES="false" lircd start successfully:

root@avware-K53SC:~# /etc/init.d/lirc start
 * Starting remote control daemon(s) : LIRC [ OK ]

root@avware-K53SC:~# ps aux | grep lircd
root 3608 0.0 0.0 5368 604 ? Ss 21:54 0:00 /usr/sbin/lircd --output=/var/run/lirc/lircd --driver=devinput --device=/dev/input/dvb-ir --listen
...

2) Done.

3) I've plugged my usb stick only after an open console ;)

4) Script executed, ko reloaded and: Protocols changed to NEC

5)
root@avware-K53SC:~# /usr/bin/irexec
irexec: could not open config files /home/avware/.lircrc and /etc/lirc/lirc/lircrc
irexec: No such file or directory
root@avware-K53SC:~# touch .lircrc <-- uhm, maybe i have to write something?
root@avware-K53SC:~# /usr/bin/irexec
^C
root@avware-K53SC:~# /usr/bin/irexec -d
root@avware-K53SC:~#

6) root@avware-K53SC:~# /usr/bin/irw
..no results

I also tried to reset protocol with RC5, RC6 but no progress. I only have a doubt, maybe I have to load nec ko ?

root@avware-K53SC:~# lsmod | grep dib0700
dvb_usb_dib0700 102037 0
rc_dib0700_rc5 12461 0
dib0090 38124 1 dvb_usb_dib0700
dib7000p 34023 2 dvb_usb_dib0700
dib7000m 22995 1 dvb_usb_dib0700
dib0070 18144 2 dvb_usb_dib0700
dvb_usb 23899 1 dvb_usb_dib0700
dib8000 47911 1 dvb_usb_dib0700
dib9000 38008 1 dvb_usb_dib0700
dib3000mc 22907 1 dvb_usb_dib0700
rc_core 21295 4 dvb_usb_dib0700,rc_dib0700_rc5,dvb_usb
dibx000_common 18457 6 dvb_usb_dib0700,dib7000p,dib7000m,dib8000,dib9000,dib3000mc

root@avware-K53SC:~# find /lib/modules/ -name *dib0700*
/lib/modules/3.6.11-030611-generic/kernel/drivers/media/rc/keymaps/rc-dib0700-nec.ko <-- sounds good
/lib/modules/3.6.11-030611-generic/kernel/drivers/media/rc/keymaps/rc-dib0700-rc5.ko
/lib/modules/3.6.11-030611-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dib0700.ko

root@avware-K53SC:~# modprobe rc-dib0700-nec
root@avware-K53SC:~# lsmod | grep dib0700
rc_dib0700_nec 12461 0
dvb_usb_dib0700 102037 0
rc_dib0700_rc5 12461 0
dib0090 38124 1 dvb_usb_dib0700
dib7000p 34023 2 dvb_usb_dib0700
dib7000m 22995 1 dvb_usb_dib0700
dib0070 18144 2 dvb_usb_dib0700
dvb_usb 23899 1 dvb_usb_dib0700
dib8000 47911 1 dvb_usb_dib0700
dib9000 38008 1 dvb_usb_dib0700
dib3000mc 22907 1 dvb_usb_dib0700
rc_core 21295 5 rc_dib0700_nec,dvb_usb_dib0700,rc_dib0700_rc5,dvb_usb
dibx000_common 18457 6 dvb_usb_dib0700,dib7000p,dib7000m,dib8000,dib9...

[penalvch (penalvch)]

avware, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]