HVR-1600 Infrared Remote

Have a MythTV related problem? Ask for help from other MythTV users here.

Moderator: Forum Moderators

Post Reply
Krydos
Newcomer
Posts: 3
Joined: Sun Feb 04, 2018 1:38 am
United States of America

HVR-1600 Infrared Remote

Post by Krydos »

I have a Hauppauge HVR-1600 with an infrared remote. I was using windows and it was working great yesterday, but Mythbuntu is not recognizing the remote. I really don't want to have to switch back to windows. I've spent a ridiculously long time trying to get this remote working, but I've made no progress. There is a lot of conflicting and outdated info out there on how to get this remote working. Can anyone help? Let me know if you'd like to see the output of anything else. Thanks!

Some spam:

Code: Select all

# dmesg | grep cx
#
[    8.194622] cx18:  Start initialization, version 1.5.1
[    8.194670] cx18-0: Initializing card 0
[    8.194672] cx18-0: Autodetected Hauppauge card
[    8.195084] cx18-0: Unreasonably low latency timer, setting to 64 (was 32)
[    8.195117] cx18-0: cx23418 revision 01010000 (B)
[    8.459827] cx18-0: Autodetected Hauppauge HVR-1600
[    8.459828] cx18-0: Simultaneous Digital and Analog TV capture supported
[    8.748407] cs5345 12-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
[    8.885667] cx18-0: Registered device video0 for encoder MPEG (64 x 32.00 kB)
[    8.885669] dvbdev: DVB: registering new adapter (cx18)
[    9.153107] cx18 0000:02:05.0: DVB: registering adapter 0 frontend 0 (Samsung                                                                                                                                S5H1409 QAM/8VSB Frontend)...
[    9.153210] cx18-0: DVB Frontend registered
[    9.153211] cx18-0: Registered DVB adapter0 for TS (32 x 32.00 kB)
[    9.153249] cx18-0: Registered device video32 for encoder YUV (20 x 101.25 kB                                                                                                                               )
[    9.153281] cx18-0: Registered device vbi0 for encoder VBI (20 x 51984 bytes)
[    9.153314] cx18-0: Registered device video24 for encoder PCM audio (256 x 4.                                                                                                                               00 kB)
[    9.153316] cx18-0: Initialized card: Hauppauge HVR-1600
[    9.153369] cx18:  End initialization
[    9.184830] cx18-alsa: module loading...
[    9.677670] probing IR Tx on cx18 i2c driver #0-0 (i2c-12)
[    9.803276] i2c i2c-12: probe of IR Tx on cx18 i2c driver #0-0 (i2c-12) done.                                                                                                                                Waiting on IR Rx.
[    9.803279] i2c i2c-12: probe of IR Tx on cx18 i2c driver #0-0 (i2c-12) done
[    9.803308] probing IR Rx on cx18 i2c driver #0-0 (i2c-12)
[    9.803436] i2c i2c-12: IR unit on cx18 i2c driver #0-0 (i2c-12) registered a                                                                                                                               s lirc0 and ready
[    9.803437] i2c i2c-12: probe of IR Rx on cx18 i2c driver #0-0 (i2c-12) done
[   10.006390] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
[   10.205809] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 byte                                                                                                                               s)
[   10.212169] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
[   11.197828] cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
[   11.224138] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware (16382 b                                                                                                                               ytes)

Code: Select all

# /var/log/syslog:
#
Feb  3 18:21:48 MediaPC lirc[541]:  * Loading LIRC modules
Feb  3 18:21:48 MediaPC lirc[541]:    ...done.
Feb  3 18:21:48 MediaPC lirc[541]:  * Unable to load LIRC kernel modules. Verify your
Feb  3 18:21:48 MediaPC lirc[541]:  * selected kernel modules in /etc/lirc/hardware.conf
Feb  3 18:21:48 MediaPC lirc[541]: find: ‘/sys/class/rc/*/’: No such file or directory
...
Feb  3 18:21:48 MediaPC kernel: [   15.030504] lirc_dev: IR Remote Control driver registered, major 244
Feb  3 18:21:48 MediaPC kernel: [   15.030626] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
Feb  3 18:21:48 MediaPC kernel: [   15.030646] lirc_zilog: module is from the staging directory, the quality is unknown, you have been warned.
Feb  3 18:21:48 MediaPC kernel: [   15.030666] lirc_zilog: module verification failed: signature and/or required key missing - tainting kernel
Feb  3 18:21:48 MediaPC kernel: [   15.030936] Zilog/Hauppauge IR driver initializing
Feb  3 18:21:48 MediaPC kernel: [   15.033152] probing IR Tx on cx18 i2c driver #0-0 (i2c-12)
Feb  3 18:21:48 MediaPC kernel: [   15.069680] i2c i2c-12: probe of IR Tx on cx18 i2c driver #0-0 (i2c-12) done. Waiting on IR Rx.
Feb  3 18:21:48 MediaPC kernel: [   15.069682] i2c i2c-12: probe of IR Tx on cx18 i2c driver #0-0 (i2c-12) done
Feb  3 18:21:48 MediaPC kernel: [   15.069710] probing IR Rx on cx18 i2c driver #0-0 (i2c-12)
Feb  3 18:21:48 MediaPC kernel: [   15.069826] i2c i2c-12: lirc_dev: driver lirc_zilog registered at minor = 0
Feb  3 18:21:48 MediaPC kernel: [   15.069828] i2c i2c-12: IR unit on cx18 i2c driver #0-0 (i2c-12) registered as lirc0 and ready
Feb  3 18:21:48 MediaPC kernel: [   15.069829] i2c i2c-12: probe of IR Rx on cx18 i2c driver #0-0 (i2c-12) done
Feb  3 18:21:48 MediaPC kernel: [   15.069858] initialization complete
Feb  3 18:21:48 MediaPC kernel: [   15.321312] cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
Feb  3 18:21:48 MediaPC kernel: [   15.652376] cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 bytes)
Feb  3 18:21:48 MediaPC kernel: [   15.658737] cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
Feb  3 18:21:48 MediaPC kernel: [   16.727316] cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)
Feb  3 18:21:48 MediaPC kernel: [   16.754150] cx18-0 843: verified load of v4l-cx23418-dig.fw firmware (16382 bytes)

Code: Select all

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Hauppauge HVR-1600"
REMOTE_MODULES="ir_kbd_i2c lirc_dev lirc_i2c"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="hauppauge/lircd.conf.hauppauge"
REMOTE_LIRCD_ARGS=""

Code: Select all

# lircd.conf.hauppauge
#
#This configuration has been automatically generated via
#the Ubuntu LIRC package maintainer scripts.
#
#It includes the default configuration for the remote and/or
#transmitter that you have selected during package installation.
#
#Feel free to add any custom remotes to the configuration
#via additional include directives or below the existing
#Ubuntu include directives from your selected remote and/or
#transmitter.

#Configuration for the Hauppauge HVR-1300 remote:
include "/usr/share/lirc/extras/more_remotes/hauppauge/lircd.conf.hauppauge"

Code: Select all

# cat /proc/bus/input/devices|grep '^N:'
#
N: Name="Power Button"
N: Name="Power Button"
N: Name="AT Translated Set 2 keyboard"
N: Name="PS2++ Logitech Wheel Mouse"
N: Name="HDA ATI HDMI HDMI/DP,pcm=3"
N: Name="HD-Audio Generic Front Mic"
N: Name="HD-Audio Generic Rear Mic"
N: Name="HD-Audio Generic Line"
N: Name="HD-Audio Generic Line Out"
N: Name="HD-Audio Generic Front Headphone"
Krydos
Newcomer
Posts: 3
Joined: Sun Feb 04, 2018 1:38 am
United States of America

Re: HVR-1600 Infrared Remote

Post by Krydos »

While I was waiting for this post to be approved by the mods I figured it out on my own. I mainly used http://jaysdesktop.blogspot.co.uk/2012/ ... buntu.html

1) I did

Code: Select all

# find . -name *zilog*
/lib/modules/4.10.0-28-generic/kernel/drivers/staging/media/lirc/lirc_zilog.ko
so the module already existed on my system and I didn't need to download it from dubious sources like my guide.

2) Lirc was already installed. During the MythTv install I selected IR remote, and picked the HVR-1300 since that seemed to be the closest option to the HVR-1600 I have. So mythbuntu installed lirc for me. It's a rather old v0.9.0 which was released 2011-03-26, but it works.

3) Next I edited /etc/lirc/hardware.conf

Code: Select all

REMOTE="Hauppauge HVR-1600"
REMOTE_MODULES="lirc_dev lirc_zilog"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="/etc/lirc/lircd.conf"
REMOTE_LIRCD_ARGS=""

TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

START_LIRCD="true"

LOAD_MODULES="true"

LIRCMD_CONF=""

FORCE_NONINTERACTIVE_RECONFIGURATION="true"
START_LIRCMD=""
4) Then I went to http://lirc-remotes.sourceforge.net/remotes-table.html and downloaded a .conf file that seemed close to the card I'm using. I picked http://sourceforge.net/p/lirc-remotes/c ... lircd.conf and saved it as /etc/lirc/lircd.conf

5) I rebooted to make sure everything was loading the latest settings, and then ran irw on the command line. Sure enough when I pressed buttons on the remote codes were shown in irw!

Hopefully this guide helps someone. All of the information on getting this remote working is very worthless and outdated

(This forum won't let me post links so they're all broken. Just remove the spaces and add http:// to the front.) Now added. Steve Goodey.
Last edited by Steve Goodey on Sun Feb 04, 2018 2:52 pm, edited 1 time in total.
Reason: Added urls.
User avatar
Steve Goodey
Moderator
Posts: 220
Joined: Fri Feb 07, 2014 6:30 pm
Location: Colchester, England
Great Britain

Re: HVR-1600 Infrared Remote

Post by Steve Goodey »

Sorry about the long delay in getting your post approved. Wallpapering slowed me down. :roll:
Don't forget the Wiki.
Krydos
Newcomer
Posts: 3
Joined: Sun Feb 04, 2018 1:38 am
United States of America

Re: HVR-1600 Infrared Remote

Post by Krydos »

Steve Goodey wrote:
Sun Feb 04, 2018 2:25 pm
Sorry about the long delay in getting your post approved. Wallpapering slowed me down. :roll:
No problem. It got approved eventually. I like writing guides like this because if I end up breaking my remote in a few months or something I can come back and follow my own guide instead of having to try to figure it out all over again. Thanks!
Post Reply