Hauppauge PVR-150 IR Blaster not seen by Sage.

[pzasso]

I am trying to get a Hauppauge PVR-150 to control a STB using the IR Blaster. The card is setup under Linux and I am able to capture video/audio from my STB both from the OS and in Sage.

I followed the steps at http://www.blushingpenguin.com/mark/blog/?p=24 and I am able to run the script provided by Mark that makes my IR blaster blink. I think it's safe to say my hardware is good at this point.

The problem is that when I go into Sage and add the PVR-150 and select the option to control an STB, it does not find the blaster on any of the ports listed (0-9).

lircd is active and everything looks good from the OS.


Note: Before trying Mark's version of lirc, I used the lirc that Gentoo provided, and although I never was able to make the IR blaster blink, it did show up as Port 1 under Sage. Sage was never able to power the STB on and off even though it was in the supported list, which is why I went to Mark's site.



Thanks,

--Paul

[rz888951]

Paul,

I had to load the module i2c_dev. However, that was not enough. i2c_dev creates entries in /dev/i2c-x in Ubuntu. Sage seems to want them in /dev/i2c/x. So I had to create symlinks from /dev/i2c-x to /dev/i2c/x. Keep in mind the symlink will not stay after a reboot, so udev rules are needed to make a mapping permanent.

[pzasso]

This is what I currently see under /dev

crw-rw---- 1 root root 89, 0 Apr 5 17:57 /dev/i2c-0
crw-rw---- 1 root root 89, 1 Apr 5 17:57 /dev/i2c-1
crw-rw---- 1 root root 89, 2 Apr 5 17:57 /dev/i2c-2
crw-rw---- 1 root root 89, 3 Apr 5 17:57 /dev/i2c-3
crw-rw---- 1 root root 89, 4 Apr 5 17:57 /dev/i2c-4
crw-rw---- 1 root root 89, 5 Apr 5 17:57 /dev/i2c-5

So it sounds like udev rules might be all I need. I'll give it a shot and post the results.


Thanks,

--Paul

[pzasso]

I followed this thread and created a udev rule:

http://forums.sagetv.com/forums/show...light=i2c+udev

I now see the following:

# ls /dev/i2c

0 1 2 3 4 5


# ls -l /dev/i2c

lrwxrwxrwx 1 root root 8 Apr 6 10:05 0 -> ../i2c-0
lrwxrwxrwx 1 root root 8 Apr 6 10:05 1 -> ../i2c-1
lrwxrwxrwx 1 root root 8 Apr 6 10:05 2 -> ../i2c-2
lrwxrwxrwx 1 root root 8 Apr 6 10:05 3 -> ../i2c-3
lrwxrwxrwx 1 root root 8 Apr 6 10:05 4 -> ../i2c-4
lrwxrwxrwx 1 root root 8 Apr 6 10:05 5 -> ../i2c-5

The udev rule appears to be working, yet Sage still doesn't see the blaster on any of the ports when I try to add them.

[_Demo_]

You shouldn't need to create special rules since the PVR150Tuner module tries both /dev/i2c/x and /dev/i2c-x where x is the port you select when doing setup.

_Demo_

[pzasso]

Everything seems to be working outside of sage. As a final thought I removed all of my tuners from sage and then went in and deleted them from the Sage.properties file. I restarted sage and it detected all of my tuners, but still no luck with the PVR-150 IR blaster getting detected.

This is what i2cdetect shows:

# i2cdetect -l show
i2c-0 smbus SMBus I801 adapter at 18a0 SMBus adapter
i2c-1 i2c ivtv i2c driver #0 I2C adapter
i2c-2 smbus em28xx #0 SMBus adapter
i2c-3 smbus em28xx #1 SMBus adapter
i2c-4 smbus em28xx #2 SMBus adapter
i2c-5 smbus em28xx #3 SMBus adapter

[pzasso]

After trying a bunch of different things, I finally decided to load the PVR150Tuner.so file from a previous release of SageTV. (6.4.8.1)

After copying that file into the current irtunerplugins directory (6.5.9.1) and starting up Sage, I then had the option to select a blaster for every port that was connected to my 4 TV tuners, but the one I needed most, which was i2c-1, was not available to configure when I tried to select it.

I then went and dowloaded 6.5.9.1 again and extracted the PVR150Tuner.so file just to rule out that the one I had was not corrupt, and once again I was not able to select any ports for the PVR-150 IR blaster.

I am not sure what changed in this driver between versions, but I think my problem might be with that .so file.

Is this something I could submit to Sage tech support, or am I on my own with supporting the PVR-150 IR blaster function under Linux?

Thanks,

--Paul

[_Demo_]

Originally Posted by pzasso

After trying a bunch of different things, I finally decided to load the PVR150Tuner.so file from a previous release of SageTV. (6.4.8.1)

After copying that file into the current irtunerplugins directory (6.5.9.1) and starting up Sage, I then had the option to select a blaster for every port that was connected to my 4 TV tuners, but the one I needed most, which was i2c-1, was not available to configure when I tried to select it.

I then went and dowloaded 6.5.9.1 again and extracted the PVR150Tuner.so file just to rule out that the one I had was not corrupt, and once again I was not able to select any ports for the PVR-150 IR blaster.

I am not sure what changed in this driver between versions, but I think my problem might be with that .so file.

Is this something I could submit to Sage tech support, or am I on my own with supporting the PVR-150 IR blaster function under Linux?

Thanks,

--Paul

Do you still have that issue? If so are you using the tar.gz package or the .deb one and how are you starting the server process?

_Demo_

[pzasso]

Yes, I am still stuck and haven't had a chance to try anything else. I am using the tar.gz package and I start/stop the server process with the following script located in /etc/init.d/ on my Gentoo system.

#!/sbin/runscript

depend() {
need net localmount
after bootmisc
}

start() {
source /etc/profile.env
export PATH="/bin:/sbin:/usr/bin:/usr/sbin:${ROOTPATH}"
ebegin "Starting SageTV server"
/opt/sagetv/server/startsage
eend $?
}

stop() {
ebegin "Stopping SageTV server"
/opt/sagetv/server/stopsage
# This can't really fail unless it was not running so we force success
eend 0
}


Thanks,

--Paul