Hauppauge PCI-e Tuner with IR Receiver ?

gujal · October 28, 2016 at 11:21 PM

Hello
I have been trying to setup libreelec on my HTPC
The HTPC runs fine under Kodi 16.1 + windows 10 but I would like to run the JeOS concept, with TVHeadend PVR
Hadware configuration :
Intel Skylake Core i5 CPU
8 GB RAM
Atheros Wifi Adapter
Hauppauge HVR-2205 DVB-T/T2 Dual tuner card with IR receiver and Hauppauge remote (not MCE)
Panasonic 4K TV

Libreelec itself runs fine at 3840x2160 resolution with hardware hevc (8 bit, no 10 bit), but no matter what I try, I am unable to get the Hauppauge IR receiver recognized, which is the final hurdle before I ditch my Kodi 16.1 on Windows10+Mediaportal backend (running fine on the same machine)

I have tried the following versions and same result in all three
1. LibreELEC-Generic.x86_64-7.0.2
2. LibreELEC-Generic.x86_64-7.90.007
3. LibreELEC-Generic.x86_64-8.0-Milhouse-20161027210429-#1027

Hauppauge card gets recognised as below from the dmesg ouput

Code

[    3.770557] Linux video capture interface: v2.00
[    3.772612] saa7164 driver loaded
[    3.772644] saa7164 0000:04:00.0: enabling device (0000 -> 0002)
[    3.772716] CORE saa7164[0]: subsystem: 0070:f123, board: Hauppauge WinTV-HVR2205 [card=13,autodetected]
[    3.772718] saa7164[0]/0: found at 0000:04:00.0, rev: 129, irq: 18, latency: 0, mmio: 0xdf400000
[    3.941629] saa7164_downloadfirmware() no first image
[    3.941655] saa7164_downloadfirmware() Waiting for firmware upload (NXP7164-2010-03-10.1.fw)
[    3.948081] saa7164_downloadfirmware() firmware read 4019072 bytes.
[    3.948082] saa7164_downloadfirmware() firmware loaded.
[    3.948083] Firmware file header part 1:
[    3.948083]  .FirmwareSize = 0x0
[    3.948084]  .BSLSize = 0x0
[    3.948084]  .Reserved = 0x3d538
[    3.948084]  .Version = 0x3
[    3.948085] saa7164_downloadfirmware() SecBootLoader.FileSize = 4019072
[    3.948089] saa7164_downloadfirmware() FirmwareSize = 0x1fd6
[    3.948090] saa7164_downloadfirmware() BSLSize = 0x0
[    3.948090] saa7164_downloadfirmware() Reserved = 0x0
[    3.948090] saa7164_downloadfirmware() Version = 0x1661c00
[   10.758495] saa7164_downloadimage() Image downloaded, booting...
[   10.865109] saa7164_downloadimage() Image booted successfully.
[   10.865123] starting firmware download(2)
[   13.668314] saa7164_downloadimage() Image downloaded, booting...
[   15.481651] saa7164_downloadimage() Image booted successfully.
[   15.481665] firmware download complete.
[   15.532766] tveeprom 5-0000: Hauppauge model 151009, rev B2I6, serial# 4035638696
[   15.532770] tveeprom 5-0000: MAC address is 00:0d:fe:8a:f5:a8
[   15.532773] tveeprom 5-0000: tuner model is SiLabs Si2157 (idx 186, type 4)
[   15.532776] tveeprom 5-0000: TV standards PAL(B/G) NTSC(M) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xfc)
[   15.532778] tveeprom 5-0000: audio processor is SAA7164 (idx 43)
[   15.532780] tveeprom 5-0000: decoder processor is SAA7164 (idx 40)
[   15.532782] tveeprom 5-0000: has radio, has IR receiver, has no IR transmitter
[   15.532784] saa7164[0]: Hauppauge eeprom: model=151009
[   15.585005] i2c i2c-7: Added multiplexed i2c bus 8
[   15.585007] si2168 7-0064: Silicon Labs Si2168-B40 successfully identified
[   15.585008] si2168 7-0064: firmware version: B 4.0.2
[   15.588976] si2157 5-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[   15.589316] DVB: registering new adapter (saa7164)
[   15.589318] saa7164 0000:04:00.0: DVB: registering adapter 0 frontend 0 (Silicon Labs Si2168)...
[   15.610394] i2c i2c-7: Added multiplexed i2c bus 9
[   15.610396] si2168 7-0066: Silicon Labs Si2168-B40 successfully identified
[   15.610397] si2168 7-0066: firmware version: B 4.0.2
[   15.613748] si2157 6-0060: Silicon Labs Si2147/2148/2157/2158 successfully attached
[   15.614088] DVB: registering new adapter (saa7164)
[   15.614090] saa7164 0000:04:00.0: DVB: registering adapter 1 frontend 0 (Silicon Labs Si2168)...
[   15.651058] saa7164[0]: registered device video0 [mpeg]
[   15.882682] saa7164[0]: registered device video1 [mpeg]
[   16.097552] saa7164[0]: registered device vbi0 [vbi]
[   16.097722] saa7164[0]: registered device vbi1 [vbi]

Display More

So the tveeprom section sees that there is a IR receiver but that never shows up in input devices as below
The HVR-2205 card has an IR transmitter as well, but that is not recognised (I don't use it, so don't mind)

Code

cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0003 Version=0000
N: Name="Sleep Button"
P: Phys=PNP0C0E/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=4000 0 0


I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0


I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2
B: PROP=0
B: EV=3
B: KEY=10000000000000 0


I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0


I: Bus=0003 Vendor=413c Product=2106 Version=0110
N: Name="DELL Dell QuietKey Keyboard"
P: Phys=usb-0000:00:14.0-12/input0
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/0003:413C:2106.0001/input/input7
U: Uniq=
H: Handlers=sysrq kbd leds event4
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Front Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input9
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=10


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Rear Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input10
U: Uniq=
H: Handlers=event6
B: PROP=0
B: EV=21
B: SW=10


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Line"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input11
U: Uniq=
H: Handlers=event7
B: PROP=0
B: EV=21
B: SW=2000


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Line Out"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input12
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=40


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Front Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input13
U: Uniq=
H: Handlers=event9
B: PROP=0
B: EV=21
B: SW=4


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input14
U: Uniq=
H: Handlers=event10
B: PROP=0
B: EV=21
B: SW=140


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input15
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=140


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input16
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=140

Display More

Can someone please advise how I get my Hauppauge IR Receiver recognised under libreelec
Thanks very much

donbrew · October 30, 2016 at 8:11 PM

You need the hauppauge ir drivers from the install disk. I don't know if there is a driver for Linux.

You might try hauppauge support Support: WinTV-HVR-2250 and WinTV-HVR-2255

You could just get a cheap VRC-1100 Vista MCE remote with a USB dongle, just plug n' play. That works on RPi anyway.

gujal · October 30, 2016 at 9:30 PM

Quote from donbrew
You need the hauppauge ir drivers from the install disk. I don't know if there is a driver for Linux.

You might try hauppauge support
Code
http://www.hauppauge.com/site/support/support_hvr2250.html

As per Hauppauge, support is built in since kernel 4.2 (OpenElec 6.0.1 onwards)

Code

http://www.hauppauge.com/site/support/linux.html

dmesg shows that the card is recognised correctly, so the driver is compiled in the kernel, may be ir receiver needs a kernel module or something.
Any help appreciated

**lrusak** · October 30, 2016 at 10:27 PM Official Post

Most likely you just need to drop in a lircd.conf into /storage/.config/lircd.conf for your remote, then reboot.

donbrew · October 30, 2016 at 10:39 PM

The TV card is recognized, the ir receiver is not. The eeprom on the TV card is reporting that there is a ir receiver attached to it because it was programmed with that information.

At least that is my limited understanding. I don't recall trying my hvr-1250 on linux. I can't find the ir receiver.

Maybe a lircd.conf would do it, I don't know if it uses lirc.

You are reading the WinTV Support for Linux differently from me.

Quote

Installing the WinTV TV tuner on Ubuntu version 14.04.02 For the WinTV-HVR-955, WinTV-HVR-2255, WinTV-HVR-2205 and WinTV-HVR-1955/1975 Notes: - Ubuntu 14.04.2 already includes the 955Q firmware v4l-cx231xx-avcore-01.fw in /lib/firmware - These directions are based on a clean retail version of Ubuntu 14.04.2 Desktop LTS with Kernel 3.16-30.

gujal · October 31, 2016 at 12:31 AM

The firmware and driver have been included as part of the linux kernel since 4.2 as per Hauppauge.
The instruction are specifically for the 3.x kernel

This is also confirmed on the LinuxTV page

Code

https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2205

I did check if the firmware was available on the default 7.0.2 install and found them, and I also added the demod firmware from openelec as per the instructions on the LinuxTV page

Following advice from Kodi forum I created a /storage/.config/autostart.sh file with these two lines

Code

modprobe rc_hauppauge
modprobe ir-kbd-i2c

so lsmod now shows this

Code

Module                  Size  Used by
si2157                  4461  2
si2168                  6196  2
i2c_mux                 2422  1 si2168
drbg                   12823  1
ctr                     3519  3
ccm                     7087  3
ir_kbd_i2c              4931  0
rc_hauppauge            2358  0
rc_core                14638  2 rc_hauppauge,ir_kbd_i2c
ath9k                  71896  0
ath9k_common           19308  1 ath9k
ath9k_hw              377393  2 ath9k_common,ath9k
ath                    16471  3 ath9k_common,ath9k,ath9k_hw
mac80211              276017  1 ath9k
fuse                   65074  7
wl                   6356280  0
snd_hda_codec_hdmi     31862  1
intel_powerclamp        6919  0
intel_rapl              8800  0
iosf_mbi                2778  1 intel_rapl
snd_hda_codec_realtek    51436  1
snd_hda_codec_generic    43541  1 snd_hda_codec_realtek
btusb                  25197  0
btrtl                   3488  1 btusb
btbcm                   5471  1 btusb
btintel                 5560  1 btusb
bluetooth             237339  5 btbcm,btrtl,btusb,btintel
saa7164                92989  0
snd_hda_intel          20100  0
tveeprom               13177  1 saa7164
snd_hda_codec          70076  4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
dvb_core               72343  1 saa7164
snd_hda_core           28290  5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep               4819  1 snd_hda_codec
videodev              100149  1 saa7164
cfg80211              208985  5 wl,ath,ath9k_common,ath9k,mac80211

Display More

But still there is no response to the remote. I tried running irw and pressed the buttons but no response on screen.
I also tried running the ir-keytable command but I keep getting

Code

Couldn't find any node at /sys/class/rc/rc*.

I did put lircd.conf for hauppauge from

Code

[http://lirc-remotes.sourceforge.net/remotes-table.html

Did try a few of the different ones available there

Please advise what steps I am missing.
Thanks for your support.

donbrew · October 31, 2016 at 1:50 AM

Is lirc installed? How current are the directions you are following, I don't think modprobe is used anymore, maybe systemctl now?

The new lirc is less than a year old and the internet is full of 20 year old tutorials that no longer work. And the tuts at lirc.org are not totally correct.

that node error sounds familiar, I can't recall what fixed it. I was fighting with making the GPIO receiver work with Kodi in Raspbian. Gave up.

I think " systemctl start lircd" is the command, or something like that..

**lrusak** · October 31, 2016 at 2:23 AM Official Post

Quote from donbrew

Is lirc installed? How current are the directions you are following, I don't think modprobe is used anymore, maybe systemctl now?

The new lirc is less than a year old and the internet is full of 20 year old tutorials that no longer work. And the tuts at lirc.org are not totally correct.

that node error sounds familiar, I can't recall what fixed it. I was fighting with making the GPIO receiver work with Kodi in Raspbian. Gave up.

I think " systemctl start lircd" is the command, or something like that..

I'm sorry but there is a lot of miss information here.

Yes, lirc comes with LibreELEC.
Modprobe is still used however I would put the module name in a file called
/storage/.config/modules-load.d/nuvoton-ir.conf
Instead of using autostart.sh

Systemctl start lircd won't work. We activate lircd via udev.

gujal · October 31, 2016 at 3:30 AM

Thanks, I have now put the module names in the /storage/.config/modules-load.d/nuvoton-ir.conf as suggested and removed autostart.sh
lsmod shows them loaded
I have lircd.conf in the /storage/.config/ directory
However the lircd shows as if it is still using the blank lircd.conf file in /run/lirc as per the following

Code

# ps -ef |grep lirc
  259 root       0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd --release=_UP
  640 root       0:00 {kodi.sh} /bin/sh /usr/lib/kodi/kodi.sh --standalone -fs --lircdev /run/lirc/lircd
  645 root       0:10 /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd
  772 root       0:00 grep lirc

**lrusak** · October 31, 2016 at 3:46 AM Official Post

I don't see lirc running there at all.

I'll do some more digging and get you to run some commands for me

gujal · October 31, 2016 at 4:32 AM

You are right, lirc is not running, I mistook eventlircd for lircd.
Will await further instructions. Also there is conflicting information about the IR receiver on the HVR-xxx5 cards, some sites indicate as if there is no driver available for these newer cards.

**lrusak** · October 31, 2016 at 4:42 AM Official Post

Can you post the output of the following commands

Code

lsmod | pastebinit

Code

dmesg | pastebinit

Code

udevadm info -q all -a /dev/lirc0 | pastebinit

The last one might not output anything

gujal · October 31, 2016 at 7:12 AM

lrusak

Here is the output as per your specification above. As you mentioned, the last file is empty. Thanks for your time.

Code

# lsmod | pastebinit
http://sprunge.us/ANNd


# dmesg | pastebinit
http://sprunge.us/RHVG


# udevadm info -q all -a /dev/lirc0 | pastebinit
Unknown device, absolute path in /dev/ or /sys expected.
http://sprunge.us/ELcY

Display More

**lrusak** · October 31, 2016 at 7:45 AM Official Post

so after some digging it looks like you may actually want to use the lirc_zilog kernel module, however, we do not include this right now. I can make you a test build with this kernel module included and hopefully we can continue.

gujal · October 31, 2016 at 8:03 AM

Thanks for that, let me know when you have a build, and I will report back with the results.
I am currently using LibreELEC-Generic.x86_64-7.0.2.img.gz

donbrew · October 31, 2016 at 1:29 PM

I don't know if this bit from lirc.org helps anything, but it might.
LIRC - Linux Infrared Remote Control

Quote

TV cards
To use any remote control receivers connected directly to a bttv based TV card you will need a working bttv setup in your kernel. For most TV cards we rely on bttv autodetection. That way you don't have to give any parameters to the module as they are selected internally depending on the information the bttv module gives us. This means that you should pay attention that your TV card is detected correctly by bttv, as can be checked using dmesg(1).

**lrusak** · October 31, 2016 at 5:57 PM Official Post

Quote from gujal

Thanks for that, let me know when you have a build, and I will report back with the results.
I am currently using LibreELEC-Generic.x86_64-7.0.2.img.gz

I only build against master, sorry.

Here is a test build
LibreELEC-Generic.x86_64-8.0-devel-20161031094040-r24348-g560ee96.tar

Remove that file you created earlier in /storage/.config/modules-load.d

Then update to this build.

Then try loading the lirc_dev and lirc_zilog modules.

Then post another dmesg

Code

dmesg | pastebinit

gujal · October 31, 2016 at 8:44 PM

Thanks for the new build. Here is the output for the three commands as before
# lsmod | pastebinit
QaiW

# dmesg | pastebinit
HIWA

# udevadm info -q all -a /dev/lirc0 | pastebinit
Unknown device, absolute path in /dev/ or /sys expected.
IOAI