Jan
15
Filed Under (Random) by mark on 15-01-2006

News

Latest: added a version that compiles with 2.6.27 kernels.
Latest: if you are packaging this, see the note at the bottom as to why I don’t provide a simple patch.
Latest: added an updated version that compiles with 2.6.24 kernels, tested against 2.6.23.12
Latest: updated `firmware` to a later revision from hauppauge (743 codesets)

HOWTO

  1. This is not for the MCE version of the PVR-150. This includes a USB unit which does not work the same way as the normal PVR-150, use standard lirc (and lirc_mceusb) for that.
  2. Use a recent kernel (note: the ivtv drivers have been part of the mainline kernel for a good number of revisions so no external drivers are required — sorry, I don’t know off hand which revision they were merged in), or for older kernels install ivtv-0.4.2+ (from this page). Earlier versions of ivtv _are not supported_.
  3. Get the pre-patched lirc 0.8.5-CVS-pvr150 tarball. There are also earlier versions that can be found here, should you want them. The previous revision may be required for kernels < 2.6.27 (as it is untested on lower revisions -- in theory it should work)
  4. You need the dialog package installed to use the lirc configuration GUI, so install that (apt-get install dialog, yum install dialog, whatever is appropriate for your distribution).
  5. Unpack the patched lirc:

    cd /usr/src
    tar xfj lirc-0.8.3-CVS-pvr150-2.tar.bz2
    cd lirc-0.8.3-CVS-pvr150-2
    ./setup.sh

    Choose:
    TV card
    i – Hauppauge PVR-150 TV card (note: _NOT_ ‘g – Hauppauge TV card’)
    Save configuration & run configure

    then:

    make && make install.

  6. IR blaster only: Now you need the ‘firmware’. This is a set of data blocks that correspond to those generated by the windows software. This goes in /usr/lib/hotplug/firmware on my debian system. Depending on your system this might also be /usr/local/lib/firmware, /lib/firmware or /lib/modules.

    Note that the entire firmware is kept in memory (currently 300K) so this makes the driver quite large. (I have no plans to sort this out, memory is cheap).

  7. Check everything is working so far:

    modprobe lirc_dev debug=1 && modprobe lirc_pvr150 debug=1

    Check the syslog output. This should report something like:

    Aug 28 02:09:11 soapbox kernel: lirc_pvr150: chip found with RX and TX
    Aug 28 02:09:11 soapbox kernel: ivtv: i2c attach [client=Hauppauge PVR150 IR RX, ok]
    Aug 28 02:09:11 soapbox kernel: ivtv: i2c attach [client=Hauppauge PVR150 IR TX, ok]
    Aug 28 02:09:11 soapbox kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
    Aug 28 02:09:11 soapbox udev[5221]: creating device node ‘/dev/lirc0′
    Aug 28 02:09:11 soapbox kernel: lirc_pvr150: firmware of size 302355 loaded
    Aug 28 02:09:11 soapbox kernel: lirc_pvr150: 743 codesets loaded
    Aug 28 02:09:11 soapbox kernel: lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0

    This means that the driver has detected and initialised the IR blaster hardware — if you don’t see that then let me know.

  8. You need to configure lircd, and find out which codeset you are going to be using. The easiest way is to start with this configuration file which contains key definitions for everything in the database. Do not use other lirc configuration files for specific STBs — these simply will not work. The IR chip is only capable of sending those codes which are in the database.
  9. Start lircd. Note: if you are using a static /dev, you may need to make a device for lirc. If unsure, once you have verified that the module has been loaded ok, run ls -l /dev/lirc*. If you don’t see a /dev/lirc0 or similar, then try mknod /dev/lirc0 c 61 0 if the steps below fail.

    modprobe lirc_dev && modprobe lirc_pvr150 debug=1
    lircd --device=/dev/lirc0

  10. You can now check if the remote is working using irw. Run this, and press buttons on the remote. You should see some output like

    0000000000001795 00 Down Hauppauge_350.

  11. Next, for the ir blaster you need to work out which codeset to use, this is the tricky bit. For this I have send_power_new, a script that just sends the power command in every single codeset. You may find your codeset number listed here if you are lucky.

    Firstly, check that you are seeing the IR blaster blink. If you don’t have blinking lights at this stage, your cable probably isn’t in the card properly (try wiggling it around), or it may be broken.

    Next you need to stick the IR blaster on the IR receiver of box that you intend to control, being quite careful to position it correctly — it has a very short range (a few cm) and took me a couple of goes to get right. The best way to do this is to find the IR demodulator on the box — easiest with a torch. Note that this is _not_ the light that comes on when you press a button on the remote, they tend to look like this.

    If you can’t get this to work, please try and check it against the Windows driver if possible. If your device will work with the windows driver but not my driver, then it’s a driver bug that I should be able to fix. If it does not work with the Windows driver either then your only options are to use a different IR blaster or bug hauppauge until they add support for the box you are trying to control. At that point, I can update my
    database too.

  12. Once you know which codeset you want you can go and delete all of the rest from lircd.conf. They are named “XXX_key” so should be pretty easy to find. I also gave the keys standard names (0-9).
  13. To get mythtv to work, configure a channel change script for your device. There’s one here that should work out of the box if you
    rename the number keys.
  14. If you’re happy, you can always send me beer money. If not, add comments at the bottom :)

That’s it, good luck!

Packaging

The lirc distribution tarball is generated using `make dist-bzip2` which uses the gnu autotools to generate a configure script, and Makefile.in, etc. The contents of these generated files depends very much on the version of autotools that is installed; this varies from distribution to distribution. I don’t have the same auto* as the lirc maintainers, so producing a patch file against a distribution tarball makes a patch bigger than the original source archive. Hence I don’t bother; I just make a new dist bzip2 and drop it here.

I maintain the code by importing a current lirc CVS into a subversion repository hosted on this server. I tag each lirc import, generate a diff from the previous lirc import and apply it to my source tree, then port any fixes from lirc_i2c.c to lirc_pvr150.c, test, and generate a new .tar.bz2. To get the source tree you can do:

svn co http://svn.blushingpenguin.com/svn/trunk/3rdparty/lirc lirc

and you can get the changes I made to the CVS revision of lirc with:

svn diff http://svn.blushingpenguin.com/svn/vendor/lirc/current http://svn.blushingpenguin.com/svn/trunk/3rdparty/lirc


366 Responses to “LIRC PVR-150 IR blaster support, version 3”

Pages: « 1 2 3 [4] 5 6 7 8 » Show All

  1. 151
    Russ Says:

    Akshat –

    I’m the guy who is having trouble getting the 4200 to respond. I created this script which continually repeats the following two lines (which I think are the correct ones – codeset 41):

    #!/bin/sh
    while :
    do
    irsend SEND_ONCE blaster 0_41_KEY_POWER
    irsend SEND_ONCE blaster 1_41_KEY_POWER
    done

    Then while the script is running I moved the emitter in front of the ir sensor, trying to find the sweet spot, with no luck.

    I’m wondering: 1) which firmware file are you using, and 2) are the above commands the right ones for codeset 41?

    Another thought – has anyone tried replacing the red LED with a true IR LED?

    Thanks,
    Russ

  2. 152
    Russ Says:

    Futher to my last post – success!

    I replaced the red LED with an IR LED scavenged from an old VCR remote I had laying around and codeset 41 works perfectly with my 4200 now.

  3. 153
    Erland Isaksson’s blog » Blog Archive » Installation of IR receiver and VFD Says:

    […] References venky.ws Mark’s Braindump […]

  4. 154
    mark Says:

    Sorry for the lack of response. I haven’t had the heart to go through the >100 spam messages until now, hopefully I’ve sorted that out by adding a captcha though.

    Chris K: if you are still interested, just send it to my email address (mark@npsl.co.uk).
    Mike: what was the command line that you ran the script with?
    Russ: cool 😉

  5. 155
    Raj Says:

    Hi Mark,
    I am setting Ir Blaster for my Hauppauge pvr 150 card using ur very good site!
    I succeeded in getting the output when I press keys of remote .
    Now I am in the Trickest part.
    I am using two DVBs
    1.HUMAX ND-1000C

    2.Zenega CD-1004S

    So,What should I have to do now?
    I haven’t found the codesets for my HUMAX or Zenega in the codesets file you included.
    And one more thing,how do I have to use those change channel script and power script for my IR remote?

    Please help me regarding!

    Thank you

    Raj

  6. 156
    Raj Says:

    Hi,
    when I tried power_send script I can’t recognize the code set for my HUMAX ND-1000C.

    irsend: command failed: SEND_ONCE blaster 0_0_KEY_POWER
    irsend: unknown remote: “blaster”

    Apart from that everything is working fine and my remote is working with myth tv also.But the chage_channekl script failing and it’s giving the following message…..

    /usr/local/bin/change_channel.sh 12
    channel changing 12
    /usr/local/bin/irsend: command failed: SEND_ONCE blaster 1
    /usr/local/bin/irsend: unknown remote: “blaster”

    So help me regarding the power_send problem?!

  7. 157
    mark Says:

    You are using the wrong lircd.conf.

  8. 158
    raj Says:

    Hi mark,
    Where can I egt correct lircd.conf file??
    Please send me if u have one working.
    Or else tell me where can I find.
    Or how can I create for myself .

    Thank you very much.

    Raj

  9. 159
    mark Says:

    step 6

  10. 160
    raj Says:

    So do I have to replace this with the existing one which i have?

  11. 161
    Raj Says:

    Hi Mark,

    One more question?

    When I try to schedule Myth TV it ‘s recording blank screen only.I tried scanning channels for Tuner,Composite 0,S-video but failed to record ?!
    I can able to watch live TV well but while scheduling my favorite programs it’s recording Blank!

    What ‘s the problem might be?
    Is that the matter with IR Blaster?Do I have to have working IR Blaster to schedule programs?
    Do I have to use any channel change script?
    In my mythbackend log it’s showing message like DVB not connected to capture card?
    How can In solve this??
    Please suggest me this !

    Thanks for your help!

    Raj

  12. 162
    aviv Says:

    Hi Mark-
    huge thanks for writing this- it helps a LOT.
    i’ve followed Hymas instructions at the beginning (http://hyams.webhop.net/mythtv/myth_ubuntu.html) to isntall lirc, but now that i need the IR Blaster, I’m trying to follow your guide-
    I configured, maked and installed, placed the haup-ir-blaster.bin in /lib/firmware, where current ivtv firmware is, but when i wroet “modprobe lirc_dev debug=1 && modprobe lirc_pvr150 debug=1″ i got nothing back.

    any idae why?

    thanks!
    aviv.

  13. 163
    George Says:

    Mark you rock! Worked like a charm. Only glitch (aside from newbie stuff which I figured out) was I had to do a cold reboot. Very strange.

    Thanks.

  14. 164
    Adolfo Says:

    In Ubuntu Dapper, haup-ir-blaster.bin must go in /lib/modules/`uname -r`, not in /lib/firmware as the ivtv stuff.

  15. 165
    KALYAN Says:

    SIR,
    I HAVE ZENEGA CD 1004S SET TOP BOX REGISTERED WITH DISH TV INDIA(OF ZEE NETWORKS). THIS WORKED FINE WITH DISH TV PACKAGES AND ALSO I HAD NO PROBLEM IN TUNNING TO OTHER LNBs MAY IT BE C BAND OR Ku BAND THROUGH DISQC SWITCH. ON 4TH OF SEPTEMBER A AUTOMATIC SOFTWARE UPGRADE HAPPENED THROUGH DISH AND A FRESH NEW MENU HAS STARTED. HOWEVER THIS IS NO LONGER BENEFICIAL FOR ME. NOW I CANNOT TUNE TO THE OTHER LNB”S
    AND WHEN I TRIED TO CHANGE THE LNB FREQUENCY FROM 10600 TO 5150 FOR C BAND , THE SET HAS BECOME LOCKED AND NOW I CANNOT EVEN ENTER MENU. IT DISPLAYS NO SERVICE INSTALLED PLEASE SEARCH
    TP BY CONNECTING TO DISH. BUT ALREADY LNB FREQUENCY IS FOR C BAND AND SINCE I CANNOT ENTER MENU SO IT IS NOT POSSIBLE TO CHANGE THE LNB FREQUENCY ANY MORE AND THE SET CANNOT SEARCH THE TP AS THE TPs FED ARE FOR Ku BAND . PLEASE TELL ME HOW CAN I RESET THE SET TO THE PREVIOUS SOFTWARE OR FACTORY RESET BY PRESSING SOME COMBINATION OF KEYS SO THAT THE SET BECOMES USEABLE ONCE MORE. MAY CONTACT ME AT dgp_kalyan@rediffmail.com
    I WILL REMAIN THANKFULL TO YOU FOR EVER IF YOU CAN PLEASE SEND ME A SOLUTION. KALYAN

  16. 166
    Todd Says:

    Hi Mark,

    Thanks for this walkthrough. I’m currently setting it up on a debian etch system with kernel 2.6.15 and ivtv 0.4.5 (installed using module-assistant in debian). I have two 150 cards installed in the system (1 MCE version and one that comes with the blaster and remote).

    So far I can get up to step 8, but irw doesn’t return anything when I point the remote at it. It comes with the newer silver remote (red green yellow and blue buttons on the bottom). Below is my output from syslog. Any help would be greatly appreciated.

    Thanks.

    Sep 10 19:09:16 localhost kernel: lirc_pvr150: probe 0x70 @ ivtv i2c driver #0: no
    Sep 10 19:09:16 localhost kernel: lirc_pvr150: probe 0x71 @ ivtv i2c driver #0: no
    Sep 10 19:09:16 localhost kernel: lirc_pvr150: ivtv i2c driver #0: no devices found
    Sep 10 19:09:16 localhost kernel: lirc_pvr150: probe 0x70 @ ivtv i2c driver #1: yes
    Sep 10 19:09:16 localhost kernel: lirc_pvr150: probe 0x71 @ ivtv i2c driver #1: yes
    Sep 10 19:09:16 localhost kernel: lirc_pvr150: chip found with RX and TX
    Sep 10 19:09:16 localhost kernel: ivtv1: i2c attach to card #1 ok [client=Hauppauge PVR150 IR RX, addr=71]
    Sep 10 19:09:16 localhost kernel: lirc_pvr150: poll thread started
    Sep 10 19:09:16 localhost kernel: ivtv1: i2c attach to card #1 ok [client=Hauppauge PVR150 IR TX, addr=70]
    Sep 10 19:09:16 localhost kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
    Sep 10 19:09:16 localhost kernel: lirc_dev: plugin lirc_pvr150 registered at minor number = 0
    Sep 10 19:09:16 localhost kernel: lirc_pvr150: firmware of size 248009 loaded
    Sep 10 19:09:16 localhost kernel: lirc_pvr150: 637 codesets loaded
    Sep 10 19:09:16 localhost kernel: lirc_pvr150: 01 60 00 01 c7lirc_pvr150: 05 02 04 9d 16lirc_pvr150: 09 6a bc 13 0flirc_pvr150: 0d ea f6 6a falirc_pvr150: 11 72 be 32 7flirc_pvr150: 15 91 9e b6 6blirc_pvr150: 19 2a 7f 06 05lirc_pvr150: 1d 78 73 00 26lirc_pvr150: 21 05 5b 90 43lirc_pvr150: 25 cf 6a 5d 2blirc_pvr150: 29 00 7c 9f 73lirc_pvr150: 2d db 2e cf 3alirc_pvr150: 31 2d 32 d4 3dlirc_pvr150: 35 4b 3b 96 40lirc_pvr150: 39 d7 5a 1a 64lirc_pvr150: 3d ec 7c 98 1elirc_pvr150: 41 5b 17 2b 6dlirc_pvr150: 45 1f 5f 06 54lirc_pvr150: 49 39 66 57 29lirc_pvr150: 4d 8b 4d 3d 48lirc_pvr150: 51 6b 52 81 74lirc_pvr150: 55 0f 7e 1b 63lirc_pvr150: 59 41 b8 91 f9lirc_pvr150: 5d dd 0a 67 50lirc_pvr150: 61 00 00 00 50lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0
    Sep 10 19:09:36 localhost kernel: lirc_dev (lirc_pvr150[0]): open called
    Sep 10 19:09:36 localhost kernel: lirc_dev (lirc_pvr150[0]): ioctl called (0x80046900)
    Sep 10 19:09:36 localhost kernel: lirc_dev (lirc_pvr150[0]): ioctl called (0x40046911)
    Sep 10 19:09:36 localhost kernel: lirc_dev (lirc_pvr150[0]): ioctl called (0x40046912)
    Sep 10 19:09:36 localhost kernel: lirc_dev (lirc_pvr150[0]): ioctl called (0x8004690f)
    Sep 10 19:09:36 localhost kernel: lirc_dev (lirc_pvr150[0]): poll called
    Sep 10 19:09:36 localhost kernel: lirc_pvr150: poll called
    Sep 10 19:09:36 localhost kernel: lirc_pvr150: poll result = 0
    Sep 10 19:09:36 localhost kernel: lirc_pvr150: key (0x00/0x00)
    Sep 10 19:10:00 localhost last message repeated 91 times
    Sep 10 19:10:00 localhost kernel: lirc_dev (lirc_pvr150[0]): poll called
    Sep 10 19:10:00 localhost kernel: lirc_pvr150: poll called
    Sep 10 19:10:00 localhost kernel: lirc_pvr150: poll result = 0
    Sep 10 19:10:00 localhost kernel: lirc_dev (lirc_pvr150[0]): close called
    Sep 10 19:10:00 localhost kernel: lirc_pvr150: key (0x00/0x00)

  17. 167
    Tony Says:

    The tuner and ir receiver work great. I’m running fc5, 2.6.17-1.2174_FC5smp #1 SMP and mythtv works fine as well. I think I followed your directions but I can’t seem to get lirc_pvr150 to control my Scientifc Atlanta 2100. I ran the send_power_new script but no joy. The codeset page indicated set 78 should work with my STB. I modified my lircd.conf to use 0_78.

    When I issue a command to change the STB to channel 5, the led blinks but does not change the channel. Here is the information from dmesg:

    On boot up:

    lirc_dev: IR Remote Control driver registered, at major 61
    lirc_pvr150: probe 0x70 @ ivtv i2c driver #0: yes
    lirc_pvr150: probe 0x71 @ ivtv i2c driver #0: yes
    lirc_pvr150: chip found with RX and TX
    lirc_pvr150: poll thread started
    lirc_dev: lirc_register_plugin: sample_rate: 0
    lirc_pvr150: firmware of size 248009 loaded
    lirc_pvr150: 637 codesets loaded
    lirc_pvr150: 01 60 00 01 c7lirc_pvr150: 05 02 04 9d 16lirc_pvr150: 09 6a bc 13 0flirc_pvr150: 0d ea f6 6a falirc_pvr150: 11 72 be
    32 7flirc_pvr150: 15 91 9e b6 6blirc_pvr150: 19 2a 7f 06 05lirc_pvr150: 1d 78 73 00 26lirc_pvr150: 21 05 5b 90 43lirc_pvr150: 2
    5 cf 6a 5d 2blirc_pvr150: 29 00 7c 9f 73lirc_pvr150: 2d db 2e cf 3alirc_pvr150: 31 2d 32 d4 3dlirc_pvr150: 35 4b 3b 96 40lirc_p
    vr150: 39 d7 5a 1a 64lirc_pvr150: 3d ec 7c 98 1elirc_pvr150: 41 5b 17 2b 6dlirc_pvr150: 45 1f 5f 06 54lirc_pvr150: 49 39 66 57 29lirc_pvr150: 4d 8b 4d 3d 48lirc_pvr150: 51 6b 52 81 74lirc_pvr150: 55 0f 7e 1b 63lirc_pvr150: 59 41 b8 91 f9lirc_pvr150: 5d dd 0
    a 67 50lirc_pvr150: 61 00 00 00 50lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version 1.3.0

    when I issue a change_channel command:

    lirc_pvr150: poll called
    lirc_pvr150: poll result = 0
    lirc_pvr150: poll called
    lirc_pvr150: poll result = 0
    lirc_pvr150: poll called
    lirc_pvr150: poll result = 0
    lirc_pvr150: 01 60 b3 9b 2blirc_pvr150: 05 fc 06 05 78lirc_pvr150: 09 73 00 26 05lirc_pvr150: 0d 5b 90 43 dflirc_pvr150: 11 7a 58 db 04lirc_pvr150: 15 0e 9e f4 9alirc_pvr150: 19 cf cf 3a 2dlirc_pvr150: 1d 32 d4 3d 4blirc_pvr150: 21 3b 14 40 c6lirc_pvr150: 25 2b 68 15 9dlirc_pvr150: 29 0e ea 6f 29lirc_pvr150: 2d 66 59 1f 6dlirc_pvr150: 31 2e 74 26 48lirc_pvr150: 35 17 25 58 f9lirc_pvr150: 39 3c 4e 88 e8lirc_pvr150: 3d ad 7e 8b f0lirc_pvr150: 41 81 49 94 d5lirc_pvr150: 45 80 f9 fa 87lirc_pvr150: 49 8c ff d9 falirc_pvr150: 4d a4 6f bc 30lirc_pvr150: 51 95 a2 d4 fflirc_pvr150: 55 83 60 8c 24lirc_pvr150: 59 d1 30 c5 d2lirc_pvr150: 5d cd 2b aa c9lirc_pvr150: 61 00 00 00 c9lirc_pvr150: NAK expected: i2c_master_send failed with -121 (try 1)
    lirc_pvr150: NAK expected: i2c_master_send failed with -121 (try 2)
    lirc_pvr150: NAK expected: i2c_master_send failed with -121 (try 3)
    lirc_pvr150: NAK expected: i2c_master_send failed with -121 (try 4)
    lirc_pvr150: sent code 78, key 5
    lirc_pvr150: poll called
    lirc_pvr150: poll result = 0
    lirc_pvr150: key (0x00/0x00)
    lirc_pvr150: poll called
    lirc_pvr150: poll result = 0
    lirc_pvr150: poll called
    lirc_pvr150: poll result = 0
    lirc_pvr150: poll called
    lirc_pvr150: poll result = 0
    lirc_pvr150: poll called
    lirc_pvr150: poll result = 0
    lirc_pvr150: key (0x00/0x00)
    lirc_pvr150: key (0x00/0x00)
    lirc_pvr150: key (0x00/0x00)
    lirc_pvr150: key (0x00/0x00)

    I do not have access to a windows box. Is there something I am missing?

  18. 168
    Eric Says:

    I am using the Hauppage PVR-150 with IR receiver/flasher included.

    I have loaded the lircd.conf, the firmware, and also the http://www.blushingpenguin.com/mark/lmilk/lirc-for-cecil.tar.bz2 since I have the 2.6.17 kernel.

    Running irw catches all of the button presses okay, but the flasher doesn’t work for the reasons below.

    The syslog doesn’t show any entries after running:

    modprobe lirc_dev debug=1 && modprobe lirc_pvr150 debug=1

    And running change_channel:

    root@mythtv:/usr/local/bin# change_channel 4
    channel changing 4
    /usr/local/bin/irsend: command failed: SEND_ONCE blaster 4
    /usr/local/bin/irsend: hardware does not support sending
    /usr/local/bin/irsend: command failed: SEND_ONCE blaster ENTER
    /usr/local/bin/irsend: hardware does not support sending

    Any help would be much appreciated, Thanks!
    –Eric

  19. 169
    mark Says:

    Todd: does it work without the 150MCE installed? I figure it might be looking at the wrong card or something like that.

    Tony: probably the wrong codeset for your box. You need to run through the script trying them until you find the right one.

    Kaylan: wtf?

    Eric: Sounds like you have lirc_i2c loaded or something along those lines?

  20. 170
    Eric Says:

    Hello,

    Everything appears to be working okay with the capturing of IR commands via irw for my remote. The issue I am running into is when I have downloaded and placed the lircd.conf file into /etc Now when I try to load the config file (lircd /etc/lircd.conf) into lircd I get:

    lircd: error in configfile line 58:
    lircd: “2147483648”: must be a valid (lirc_t) number
    lircd: reading of config file failed

    I am running lircd 0.8.1-CVS-pvr150 (Cecil version) on an Athlon 64 machine, debian 2.6.17-2-amd64.

    Any thoughts?
    Thanks!

  21. 171
    Eric Says:

    Don’t know what the issue was, but I built my on config file by hand, and everything works great!

    Cheers!

  22. 172
    Francisco Says:

    Hi Mark,

    Is there an available Mark’s lirc version for 2.6.18 Kernels (kanotix distribution).

    I got this compilation errors:

    /usr/src/lirc-0.8.1-CVS-pvr150/drivers/lirc_dev/lirc_dev.c:54:35: error: linux/devfs_fs_kernel.h: No such file or directory
    /usr/src/lirc-0.8.1-CVS-pvr150/drivers/lirc_dev/lirc_dev.c: In function ‘cleanup’:
    /usr/src/lirc-0.8.1-CVS-pvr150/drivers/lirc_dev/lirc_dev.c:132: warning: implicit declaration of function ‘devfs_remove’
    /usr/src/lirc-0.8.1-CVS-pvr150/drivers/lirc_dev/lirc_dev.c: In function ‘lirc_register_plugin’:
    /usr/src/lirc-0.8.1-CVS-pvr150/drivers/lirc_dev/lirc_dev.c:381: warning: implicit declaration of function ‘devfs_mk_cdev’
    make[5]: *** [/usr/src/lirc-0.8.1-CVS-pvr150/drivers/lirc_dev/lirc_dev.o] Error 1
    make[4]: *** [_module_/usr/src/lirc-0.8.1-CVS-pvr150/drivers/lirc_dev] Error 2

    Thanks in advance for your help.

    Francisco from Panama.

  23. 173
    nate Says:

    Thanks for your hard work. I see on the Hauppauge site that there is a new IR blaster program updated on Oct 13, 2006 that includes support for the Dish 811 receiver. Any plans to include this in your database? I got all the way through the install…light flashes and I can use remote with myth. I ran your send_power script, but none of the codes worked.

  24. 174
    Jeff Says:

    Hi Mark,

    I read through all the posts here and didn’t see anything about LIRC support for IR blasters in multiple PVR-150 (1045) cards. Is it possible? I have two of them in a Windows machine which, at the time I set it up, the win drivers would only support the blaster in the first PCI slot it found (not sure if that was ever fixed). Alternatively, could MythTV/LIRC control multiple STBs via a single blaster? I have a USB-UIRT (http://www.usbuirt.com/) which should work (http://www.mythtv.org/wiki/index.php/USB-UIRT) and multiple DishNetwork 311’s which can be configured with different “remote addresses”. Sorry if that’s a bit off topic.

    Thanks in advance,
    Jeff

    PS (sorry if I double posted – browser/captcha issues)

  25. 175
    infringer Says:

    To Mark:
    Mark if you happen to get the SDK for the Zilog based IR chip I’d very much appreciate if you upload it to rapidshare or something …

    Obviously it is poorly based firmware they should have a more dynamic firmware alls I can say is I’m fed up with hauppauges lack of support one of there biggest owners of the cards is mythtv users…

    To Everyone Reading:
    There is a lack of complaints to the company as well complain complain everyone. Even if it dont work for you pick a model they do NOT support and take a couple of seconds to help the community out and ask them to support that model.

    More and more folks fall off the track due to a lack of support we need our community to remain strong if we wish to continue advancement with myth tv.

    Do us all a favor and complain constently it dont take long eventually someone in the right place will hear us and start doing something about it!

    Email

    >> Contact Us

    Hauppauge Headquarters, NY
    Hauppauge Computer Works, Inc.
    91 Cabot Court
    Hauppauge, NY 11788
    tel: 631.434.1600
    fax: 631.434.3198
    Sales:
    sales@hauppauge.com
    Tech Support:
    tel: 631.434.3197
    techsupport@hauppauge.com
    Click here to visit our support page
    Investor Relations:
    Jerry Tucciarone
    tel: 631.434.1600 ext.306
    jtucciarone@hauppauge.com

    Thank you please take about 5 seconds of you’re free time and send them an email asking them to support more cable boxes…

    DCT2244 by motorola
    Scientific Explorer 3200

    And I’m sure there are many more…

    Please Pleas Please
    Thank You

  26. 176
    Amankhan Says:

    I second the request for an updated version of Mark’s LIRC for the 2.6.18 kernels. I’ve been able to successfully compile LIRC, but when I try to load the lirc_pvr150 module I get this error message:

    FATAL: Error inserting lirc_pvr150 (/lib/modules/2.6.18-1.2849.fc6/misc/lirc_pvr150.ko): Invalid module format

    This error message usually means that I do not have the correct kernel sources installed, but I do have the 2.6.18-1.2849.fc6 kernel-dev installed.

  27. 177
    Kurt Says:

    Mark

    Thanks a bunch for all the hard work you’ve put into this!

    I had successfully followed your directions to get the IR receiver working on my PVR 150. I was able to see IR events using irw, control my myth PVR, etc. Then I installed a pchdtv HD-5500. This took over /dev/video0 and /dev/dsp, though luckily I am still able to see the PVR 150 output on /dev/video1. My IR blaster was unaffected, so I have no problems controlling my set top box. My /dev/lirc* devices were not so lucky. Something about the installation seems to have detached them from the PVR 150. /dev/lirc0 still has 61,0 device numbers, but when I run irw I no longer see IR events from the remote control. I’m assuming the HD 5500 is the culprit, especially since it has an IR receiver which according to its documentation is “not yet supported by the driver”.

    I’m very fuzzy on how the linux internals work here; can you give some advice on how to get my PVR 150’s IR receiver working again?

    Thanks!

  28. 178
    mark Says:

    Francisco, Amankhan: I have updated the package to compile with 2.6.18 kernels, can you give it a whirl and let me know if it works?

    Jeff: it works fine AFAIK, you just run more lirc daemons with –device=/dev/lirc1 –output=/dev/lircd1, etc.

    Nate: I am unable to create new codeset dumps at present. If you have a Windows machine and are willing to do a bit of work I can provide you with instructions + tools to create one though, send me an email if you feel like giving it a whirl.

    Infringer: there is no SDK and nothing will be forthcoming from Hauppauge. Sorry :/

    Kurt: that sounds very odd indeed as the receiver and transmitter are both handled through the same lirc device. Can you compile the driver with the debug option (in the ./configure menu), then load the module with modprobe lirc_pvr150 debug=1 and post the syslog output after running lircd+irw?

  29. 179
    Amankhan Says:

    Thank you so much for the update version, Mark! Its working perfect now with 2.6.18-1.2849!

  30. 180
    Jeremy Says:

    I have a PVR-350 card. I can receive no problem, when i try sending i get
    /usr/local/bin/irsend: hardware does not support sending. I need to send to an ExpressVu 3100 receiver.

    any ideas?

  31. 181
    mark Says:

    Amankhan: cool!

    Jeremy: try reading the post title.

  32. 182
    Gary Says:

    Mark…this is awsome! I got further in an hour with your instructions than I did in a week using other articles. I am at the point where I can see the signals with irw, but I cannot seem to transmit anything. send_power_new just keeps saying “irsend: unknown remote: “blaster”
    I am a relative linux newbie, so maybe I am missing something stupid. I did notice that while I have a /dev/lirc0, I do not have a /dev/lirc1, so maybe this is why I can receive, but not send?
    I am using Debian Etch, kernel 2.6.17-2-amd64. You have already helped immeasurably, but could you shed any light on this for me? Thanks in advance!

  33. 183
    mark Says:

    You are not using the right lircd.conf, please use the one linked to in step 6.

  34. 184
    Gary Says:

    Mark, First, thank you for your quick reply! I apparently have a newer remote, so the lircd.conf file at #6 did not work, however, I finally figured out how to make my own, which I combined with the appropriate codesets from your file, so that all now works(I think, haven\’t wired it to the box yet!) Now I am working onMythtv itself. It seems it needs a lircrc file in ~/.mythtv Do you have any advice for me? (BTW, I followed your instructions to the letter except for a few hardware/system specific tweaks & now have a working lircd.conf file! Thank you very much!)

  35. 185
    Scott Says:

    Mark (or anyone else),

    Using suse 10.2 with mythtv.
    I have been able to follow the directions you gave and the remote works, although it created a new problem. After I removed the lirc that came with 10.2 I now get the message frfom mythtv:
    mythtv-setup: error while loading shared libraries: liblirc_client.so.0: cannot open shared object file: No such file or directory

    I believe i tried reinstalling mythtv, but nothing changed.
    How do I re-link to your lib?

  36. 186
    Sander Says:

    Doesnt seem to work for Suse 10.2 unfortunately: modules load properly, no luck with the remote (dont need the blaster).

    But, with the info here, I at least got the remote working with Lirc 0.8.1pre4 (while keeping the Lirc 0.8.0 package Suse provides):
    ./configure –prefix=/usr –with-driver=hauppauge –enable-debug

    then move lirc_dev.ko and lirc_i2c.ko from /lib/modules/`uname -r`/misc to
    /lib/modeles/`uname -r`/updates/lirc_dev
    and
    /lib/modeles/`uname -r`/updates/lirc_i2

    In /etc/sysconfig/lirc then set:
    LIRCD_DEVICE=”/dev/lirc”
    LIRC_MODULE=”lirc_i2c”

    lircd.conf from here, at least the remote works
    modprobe lirc_dev && modprobe lirc_i2c
    rclirc restart

  37. 187
    Scott Says:

    I ended up copying the lib to \lib and it seems fine now.

  38. 188
    Jake Says:

    Hey Mark,

    Thank you for all your hard work, by the way. I’m afraid I’ve got the same question as Jeremy above. I’ve got a PVR-350, which listed in its specs that it has an IR blaster; and I’m seeing what I can do about getting it working.

    Not trying to be annoying here, but does your comment:

    “Jeremy: try reading the post title.”

    mean that this is for the PVR-150, and that you’d rather not answer questions about the PVR-350?

    Thanks much!

  39. 189
    Steve Says:

    Mark,

    Thanks so much for all your work!

    Your patch is working great on a Mythdora 3.0 installation with a DirecTV D11 tuner. The PVR-150 is a model 1045.

    Not having much experience with this, I fumbled around until it started working. Here’s a list of the things I did, although I’m not sure everything I did was necessary:

    I installed the “dialog” package so I could build the patched lirc.

    On Mythdora after ‘make install’ I manually moved lircd and lircmd from /usr/local/sbin to /usr/sbin, I moved lirc_dev.ko and lirc_pvr150.ko from /lib/modules/2.6.18-1.2239.fc5smp/misc to /lib/modules/2.6.18-1.2239.f5csmp/updates/drivers/lirc, and I changed the file /etc/sysconfig/modules/lircd.modules to load lirc_pvr150 instead of lirc_i2c.

    I used the section from your lircd.conf file with the labels 1_125_… for the D11 tuner and combined them with the lircd.conf file supplied by Mythdora for the “new grey and black remote”. In the combined lircd.conf I renamed the ‘name’ labels from ‘1_125_KEY_0′ to just ‘0’.

    The PVR-150 IR blaster LED needs to be very close the IR Receiver on the D11, in my case, virtually touching the box.

    Thanks again!

  40. 190
    Bo Says:

    Hi Mark

    I am trying to rmmod lirc_prv150, but get: “ERROR: Module lirc_pvr150 is in use”.

    If you have a hint re how to resolve this, I would be very thankful.

    -Bo

  41. 191
    D. Jay Says:

    I am really struggling with your mythtv script. I have mythtv working with the remote. I am even able to change the channel on my cable box but only command line. So what I don\’t understand is how to line your script and mythtv together. Any help?

  42. 192
    Dan Says:

    I get the following error when I run:

    modprobe lirc_dev debug=1 && modprobe lirc_pvr150 debug=1

    It only happens with the “modprobe lirc_pvr150 debug=1″ section.

    “Jan 2 23:48:09 MythServer kernel: kobject_add failed for i2c ir driver with -EEXIST, don’t try to register things with the same name in the same directory.”

    I don’t recieve messages in the syslog like “lirc_pvr150: chip found with RX and TX”

    …but instead get messages like:

    “Jan 2 22:59:34 MythServer kernel: tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
    Jan 2 22:59:34 MythServer kernel: cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
    Jan 2 22:59:39 MythServer kernel: cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
    Jan 2 22:59:39 MythServer kernel: wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
    Jan 2 22:59:39 MythServer kernel: lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150))
    Jan 2 22:59:39 MythServer kernel: lirc_dev: lirc_register_plugin: sample_rate: 10
    Jan 2 22:59:39 MythServer kernel: tveeprom 1-0050: Hauppauge model 26132, rev F1B2, serial# 10062800″

    Any suggestions? I think that the lirc_i2c drivers are still hanging around, how can I uninstall them for good if that is the case?

  43. 193
    Chris Says:

    Mark,
    Is the lirc_pvr150 driver intended to work with the PVR-350 card as well as the PVR-150?

  44. 194
    Dan Says:

    Please disregard my previous comment. Here is where I am now.

    I can get change_channel to change the channels from a terminal. When I add /etc/change_channel to “External channel change command”, I can use the up and down arrows of the remote to change the numbers on the screen AND make the IR blaster blinks…but whatever is coming out of the IR blaster isn’t changing the changing the channel on the STB. Placement on the IR blaster is perfect for terminal manual change_channeling, but not good in MythTV.

    Any thoughts on thought?

    My other issue is that I don’t know how to get “modprobe lirc_dev && modprobe lirc_pvr150″ to load from boot. I currently have to run a script I made manually for it all to kick in.

    Ideas on that?

  45. 195
    Tom Says:

    Mark…I’d be willing to try to get the new codesets working. You can send me the instructions and tools, and I’ll give it a shot.

  46. 196
    Cristiano Says:

    I have a pvr150 controlling a skybox so I tried your package and it seems to work with a little problem.
    When I send a command like “irsend SEND_ONCE blaster 1_663_KEY_XXXX” the IR code is generated ok but the box receives two signal instead of one and this creates some problem during the OSD navigation (es: double jump on the osd entry).
    I am using gentoo with 2.6.18-gentoo-r4 kernel and here is my logs:
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): open called
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): ioctl called (0x80046900)
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): ioctl called (0x40046911)
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): ioctl called (0x40046912)
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): ioctl called (0x8004690f)
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): poll called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: poll called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: poll result = 0
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): poll called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: poll called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: poll result = 0
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): write called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: 01 60 b2 a0 2alirc_pvr150: 05 b8 07 90 79lirc_pvr150: 09 fd 00 26 05lirc_pvr150: 0d 5b 90 43 ddlirc_pvr150: 11 49 5c b5 00lirc_pvr150: 15 ac 9e d3 dblirc_pvr150: 19 f7 13 c9 2dlirc_pvr150: 1d 32 d4 3d 4blirc_pvr150: 21 3b 14 40 c6lirc_pvr150: 25 2b 68 14 cflirc_pvr150: 29 6d e9 6f 2alirc_pvr150: 2d 66 5a 1c 6elirc_pvr150: 31 2e 77 25 48lirc_pvr150: 35 54 26 3b falirc_pvr150: 39 79 fd cb 94lirc_pvr150: 3d ad 7e 8b f0lirc_pvr150: 41 81 49 94 d5lirc_pvr150: 45 80 f9 fa 87lirc_pvr150: 49 8c ff d9 falirc_pvr150: 4d a4 6f bc 30lirc_pvr150: 51 95 a2 d4 fflirc_pvr150: 55 83 60 8c 24lirc_pvr150: 59 d1 30 c5 d2lirc_pvr150: 5d cd 2b 99 c8lirc_pvr150: 61 00 00 00 c8lirc_pvr150: NAK expected: i2c_master_send failed with -121 (try 1)
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: NAK expected: i2c_master_send failed with -121 (try 2)
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: NAK expected: i2c_master_send failed with -121 (try 3)
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: NAK expected: i2c_master_send failed with -121 (try 4)
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: NAK expected: i2c_master_send failed with -121 (try 5)
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: sent code 33431, key 49
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): poll called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: poll called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: poll result = 0
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): poll called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: poll called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: poll result = 0
    Jan 16 12:30:44 LiveServer-222 lirc_dev (lirc_pvr150[0]): close called
    Jan 16 12:30:44 LiveServer-222 lirc_pvr150: key (0x00/0x00)

    any ideas?
    thanks in advance

  47. 197
    Paul Says:

    Was wondering if anyone has experience in using these instructions with Ubunty Edgy Eft? I have tried setting up the ir blaster using the lirc and external channel changer instructions at https://help.ubuntu.com/community/MythTV_Edgy_hardware and whilst at one point I got the remote working I have had zero success with getting the ir blaster to work. As my machine is a headless mythtv backend all I need is the ir blaster. I believe edgy is slightly different from some distros as it has support for some remotes built in. Thanks

  48. 198
    Byte Surfer Says:

    I have just built a fedora core 6 box with the latest kernel. Myth TV is working fine with my PVR-150 except for the blasting. I would like this to work.

    Since I already have IRC and IVTV installed and working, do I have to remove these or just reprogram them ? Can someone give me an overview of what I need to do since I already have this stuff installed and working. I can look through the instructions and posts for details. I just want to know what steps to take. I am slightly confused by all the info here.

    I have the PVR-150 with the y-cable and two heads . Also, will all this work w/the latest kernel ? (i will post version # soon) thanks.

  49. 199
    Aravind Says:

    Mark, thanks a lot for the patched lirc – I couldn’t have setup my mythtv system without it. Do you suppose it’s possible to merge it into the lirc tree somehow? It is a bit of a bother to manually recompile lirc whenever I update my kernel. Besides, it will probably save you the trouble of updating the patches here on your blog every time kernel changes break them.

  50. 200
    Amankhan Says:

    Hi again Mark,

    Looks like the 2.6.19 kernels are having the same error that we had with the 2.6.18 kernels:

    FATAL: Error inserting lirc_pvr150 (/lib/modules/2.6.18-1.2849.fc6/misc/lirc_pvr150.ko): Invalid module format

    Any chance you could update the packages again? :)

Pages: « 1 2 3 [4] 5 6 7 8 » Show All

Leave a Reply


− three = 4