[mythtv-users] Only one of two IR receivers are configured during boot

[Stephen Worthington]

On Thu, 2 Jan 2020 23:02:41 +0100, you wrote:

>On Thu, Jan 02, 2020 at 03:12:36PM +1300, Stephen Worthington wrote:
>> On Thu, 2 Jan 2020 12:45:42 +1100, you wrote:
>> 
>> >On Thu, Jan 02, 2020 at 01:48:43AM +0100, Peter Carlsson wrote:
>> >
>> >> Thanks for the help! But will this take me all the way?
>> >
>> >Nope. What I sent would only set up the symlink.
>> >
>> >> Maybe I misunderstand something but this will only ensure that I always
>> >> have the same symlink names? What I also think is needed is for the
>> >> Hauppauge card to also load the correct IR driver.
>> >
>> >In dmesg after a reboot do you see complaints about missing firmware?
>> >The Hauppage cards seem to want some firmware blobs that may not be
>> >available in Debian.
>> >
>> >If you know what module is needed you may need to give the kernel
>> >a prod with a file in /etc/modprobe.d
>> >This may help:
>> >https://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500
>> >
>> >It may be possible to tell udev to load the module but I don't
>> >know how at the moment.
>> 
>> Yes, a Nova-T (or TD) 500 card will definitely need the
>> dvb-usb-dib0700-1.20.fw file.  It does not come in any of the standard
>> packages - you need to install it yourself.  There is no need to do
>> anything other than just put the file in /lib/firmware and reboot.  I
>> am surprised that much at all works on those tuners without it.
>
>The same hardware setup worked without problems on Debian Stretch and
>MythTV 29, but when I upgraded to Debian Buster and MythTV 30 I started
>to get this problem (and some other that I have resolved).
>
>What I see in dmesg is:
>[    6.117142] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware
>[    6.118199] usb 13-1: firmware: direct-loading firmware dvb-usb-dib0700-1.20.fw
>...
>[    6.396173] dib0700: firmware started successfully.
>
>> I have two of these cards in two different PCs.  Mine are the Nova-TD
>> 500 variant.  What I have for configuring them is this in my
>> /etc/modprobe.d/options-dvb.conf file:
>> 
>> #Set adapter numbers for Nova-TD 500 DVB-T card (dual tuners).
>> options dvb_usb_dib0700 adapter_nr=0,1
>
>My /etc/modprobe.d/dvb_usb_dib0700 have this in it:
>  options dvb_usb_dib0700 force_lna_activation=1
>
>> which just sets them to be tuners 1 and 2.  And in my
>> /etc/udev/rules.d/10-local-rules.conf file:
>> 
>> # Hauppauge Nova TD-500 remote control IR receiver
>> SUBSYSTEM=="input", KERNEL=="event*", ATTRS{idVendor}=="2040",
>> ATTRS{idProduct}=="8400", SYMLINK+="lirc0"
>> 
>> which makes the IR receiver /dev/lirc0.
>
>Would MythTV expect the used IR receiver to be called lirc0 even if I
>use ir-keytable and not lirc? I don't see any traces of the name lirc0
>in my logs. But I do see that my IR receivers are named lirc0 and lirc1
>the other way round.

No, that was just an example of a working setup to symlink the IR
receiver.  I have mine on /dev/lirc0.  You need to set the symlink to
whatever your lirc setup needs.  But I believe the default location
that lirc reads inputs from is /dev/lirc0, and your ir-keytable output
shows that the wrong IR device is currently on /dev/lirc0.

>> I am running Ubuntu 18.04, but the Debian setup should be very
>> similar, if not identical.
>
>Could you please give me your output of 'ir-keytable'. For me it is:
>Found /sys/class/rc/rc1/ (/dev/input/event21) with:
>        Name: Hauppauge Nova-T 500 Dual DVB-T
>        Driver: (null), table: rc-dib0700-rc5
>        LIRC device: /dev/lirc1
>        Supported kernel protocols: rc-5 nec rc-6
>        Enabled kernel protocols: rc-5
>        bus: 3, vendor/product: 2040:9950, version: 0x0100
>        Repeat delay = 500 ms, repeat period = 125 ms
>Found /sys/class/rc/rc0/ (/dev/input/event20) with:
>        Name: 9-4:1.0 IR
>        Driver: em28xx, table: rc-pinnacle-pctv-hd
>        LIRC device: /dev/lirc0
>        Supported kernel protocols: rc-5 nec rc-6
>        Enabled kernel protocols: rc-5
>        bus: 3, vendor/product: 2013:025f, version: 0x0001
>        Repeat delay = 500 ms, repeat period = 125 ms
>
>/Peter

Here is the ir-keytable output from the box with the Nova TD-500 card:

Found /sys/class/rc/rc0/ (/dev/input/event5) with:
        Driver dib0700, table rc-dib0700-rc5
        Supported protocols: rc-5 nec rc-6
        Enabled protocols: rc-5
        Name: IR-receiver inside an USB DVB re
        bus: 3, vendor/product: 2304:0237, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms
Found /sys/class/rc/rc1/ (/dev/input/event6) with:
        Driver dib0700, table rc-dib0700-rc5
        Supported protocols: rc-5 nec rc-6
        Enabled protocols: rc-5
        Name: IR-receiver inside an USB DVB re
        bus: 3, vendor/product: 2040:8400, version: 0x0100
        Repeat delay = 500 ms, repeat period = 125 ms

Not that it has "Driver dib0700", instead of "(null)".  Until you can
fix that, I do not think the IR input is going to work.  But the rest
of the ir-keytable output matches mine, except for the "LIRC device"
and that yours seems to be the older Nova T-500 variant, so its USB
"vendor/product" is different.

Also, what version of lirc are you using now?  There has been a big
update to lirc not long ago, that required completely new
configuration.  If that has just happened to you, it will all be
broken for you until you make the correct changes.  So what is the
output of a "lircd -v" command?  Ubuntu 18.04 has "lircd 0.10.0".  The
box I have the Nova TD-500 card in is still running Ubuntu 16.04 and
has "lircd 0.9.0", which is before the big lirc changes.