Page 6 of 9 FirstFirst ... 45678 ... LastLast
Results 51 to 60 of 84

Thread: Using PVR150 IR Blaster In Mythbuntu 9.10b

  1. #51
    Join Date
    Jul 2008
    Beans
    7

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    There is something I don't understand about the lirc_zilog drivers. I have HVR-1950 and I have been successful compiling the patched drivers. However, the drivers cannot find my device. Please find an output of dmesg:

    root@mythtv:~# dmesg | grep lirc
    [ 13.825455] lirc_dev: IR Remote Control driver registered, major 61
    [ 14.001912] lirc_i2c: chip 0x0 found @ 0x71 (Hauppauge HVR1300)
    [ 14.001916] lirc_dev: lirc_register_driver: sample_rate: 10
    [ 14.041084] lirc_zilog: Zilog/Hauppauge IR driver initializing
    [ 14.042631] lirc_zilog: initialization complete
    [ 86.451222] lirc_zilog: Zilog/Hauppauge IR driver unloaded
    [ 107.214681] lirc_dev: IR Remote Control driver registered, major 61
    [ 107.219376] lirc_zilog: Zilog/Hauppauge IR driver initializing
    [ 107.221957] lirc_zilog: ir_probe: adapter id=0x0, client addr=0x71
    [ 107.221963] lirc_zilog: no device found
    [ 107.222016] lirc_zilog: initialization complete
    [ 118.292653] lirc_zilog: Zilog/Hauppauge IR driver unloaded
    [ 136.504779] lirc_dev: IR Remote Control driver registered, major 61
    [ 136.509413] lirc_zilog: Zilog/Hauppauge IR driver initializing
    [ 136.511777] lirc_zilog: ir_probe: adapter id=0x0, client addr=0x71
    [ 136.511782] lirc_zilog: no device found
    [ 136.511836] lirc_zilog: initialization complete

    Could someone suggest why the driver fail to see the device?
    BTW, I am using the latest pvrusb2 drivers.
    OS is Mythbuntu 9.10 kernel 2.6.31-16-generic

    Thanks,
    Ale99

  2. #52
    Join Date
    Sep 2007
    Location
    Montreal
    Beans
    21
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    Quote Originally Posted by sentinel23 View Post
    Thanks!

    Interesting...

    If it helps at all, I was able to determine that "lirc_pvr150" was re-released as "lirc_zilog", and Jarod Wilson created a kernel patch for .31 that apparently gets it working. (Sorry, don't have the links handy ATM.)

    I haven't tried it, but it might be something to look at.
    can you please find that link?
    i'm trying to do this too and it would help me or someone else to have that link you mention

  3. #53
    Join Date
    Nov 2006
    Beans
    11

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    Quote Originally Posted by TheHilikus View Post
    can you please find that link?
    i'm trying to do this too and it would help me or someone else to have that link you mention
    See if these help:

    http://old.nabble.com/PVR-150-IR-blaster-with-2.6.31-Karmic-Koala-kernel-td26144394.html

    http://wilsonet.com/jarod/junk/hdpvr-ir/
    http://www.gossamer-threads.com/list...t_reply;so=ASC
    http://www.gossamer-threads.com/list...ost_time&mh=50

  4. #54
    Join Date
    Sep 2007
    Location
    Montreal
    Beans
    21
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    ok, i got it working! both RC and IR Blaster work
    i really don't understand why though. There's nothing in my hardware.conf that says that my RC is what it is, it only says what the IR Blaster should map to, so i don't know where the RC mapping is coming from. I don't know if it's a luck bug where lirc just remembers the last mapping that worked but if it is that, i am thinking it won't survive an update

    this is my hardware.conf. notice everything about the RC is commented out, only the IR Blaster section is active

    Code:
    # /etc/lirc/hardware.conf
    #
    #Chosen Remote Control
    #REMOTE="Hauppauge TV card"
    #REMOTE_MODULES="lirc_dev lirc_i2c"
    #REMOTE_DRIVER=""
    #REMOTE_DEVICE="/dev/lirc0"
    #REMOTE_SOCKET=""
    #REMOTE_LIRCD_CONF="hauppauge/lircd.conf.hauppauge"
    #REMOTE_LIRCD_ARGS=""
    
    #Chosen IR Transmitter
    TRANSMITTER="Command IR : Scientific Atlanta Cable box"
    TRANSMITTER_MODULES="lirc_dev lirc_zilog"
    TRANSMITTER_DRIVER=""
    TRANSMITTER_DEVICE="/dev/lirc0"
    TRANSMITTER_SOCKET=""
    TRANSMITTER_LIRCD_CONF="scientificatlanta/general.conf"
    TRANSMITTER_LIRCD_ARGS=""
    
    #Enable lircd
    START_LIRCD="true"
    
    #Don't start lircmd even if there seems to be a good config file
    #START_LIRCMD="false"
    
    #Try to load appropriate kernel modules
    LOAD_MODULES="true"
    
    # Default configuration files for your hardware if any
    LIRCMD_CONF=""
    
    #Forcing noninteractive reconfiguration
    #If lirc is to be reconfigured by an external application
    #that doesn't have a debconf frontend available, the noninteractive
    #frontend can be invoked and set to parse REMOTE and TRANSMITTER
    #It will then populate all other variables without any user input
    #If you would like to configure lirc via standard methods, be sure
    #to leave this set to "false"
    FORCE_NONINTERACTIVE_RECONFIGURATION="false"
    START_LIRCMD=""
    also, in case someone is trying to do this. The only modules i have loaded are lirc_dev and lirc_zilog. so it seems that lirc_zilog works not only for the Blaster but for the RC as well

  5. #55
    Join Date
    Mar 2008
    Beans
    23

    Question Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    I followed the steps listed by jimmybondo in post #28 of this thread, but I still get the "hardware does not support sending" error.

    From the comments here, it sounds like this technique does not work for 64-bit kernels. I am using Mythbuntu 9.10 64-bit, so I guess that explains the problems I'm having.

    Has anybody been able to make this work using a 64-bit kernel? If so, a brief howto would be very much appreciated.

    tail /var/log/syslog:
    Code:
    Dec 26 17:02:06 Reggie ntpd[1468]: synchronized to 91.189.94.4, stratum 2
    Dec 26 17:03:38 Reggie lircd-0.8.6[2613]: caught signal
    Dec 26 17:03:38 Reggie lircd-0.8.6[2653]: lircd(default) ready, using /var/run/lirc/lircd
    Dec 26 17:03:41 Reggie lircd-0.8.6[2653]: accepted new client on /var/run/lirc/lircd
    Dec 26 17:03:41 Reggie lircd-0.8.6[2653]: could not get file information for /dev/lirc0
    Dec 26 17:03:41 Reggie lircd-0.8.6[2653]: default_init(): No such file or directory
    Dec 26 17:03:41 Reggie lircd-0.8.6[2653]: Failed to initialize hardware
    Dec 26 17:03:41 Reggie lircd-0.8.6[2653]: error processing command: SEND_ONCE DCT2000 1
    Dec 26 17:03:41 Reggie lircd-0.8.6[2653]: hardware does not support sending
    Dec 26 17:03:41 Reggie lircd-0.8.6[2653]: removed client
    dmesg | grep lirc:
    Code:
    [    8.302861] lirc_dev: IR Remote Control driver registered, major 61 
    [    8.328943] lirc_zilog: Zilog/Hauppauge IR driver initializing
    [    8.330292] lirc_zilog: initialization complete
    hardware.conf:
    Code:
    # /etc/lirc/hardware.conf
    #
    #Chosen Remote Control
    REMOTE="None"
    REMOTE_MODULES=""
    REMOTE_DRIVER=""
    REMOTE_DEVICE=""
    REMOTE_SOCKET=""
    REMOTE_LIRCD_CONF=""
    REMOTE_LIRCD_ARGS=""
    
    #Chosen IR Transmitter
    TRANSMITTER="Command IR : Motorola Cable box"
    TRANSMITTER_MODULES="lirc_dev lirc_zilog"
    TRANSMITTER_DRIVER=""
    TRANSMITTER_DEVICE="/dev/lirc0"
    TRANSMITTER_SOCKET=""
    TRANSMITTER_LIRCD_CONF="motorola/dctxxxx.conf"
    TRANSMITTER_LIRCD_ARGS=""
    
    #Enable lircd
    START_LIRCD="true"
    
    #Don't start lircmd even if there seems to be a good config file
    #START_LIRCMD="false"
    
    #Try to load appropriate kernel modules
    LOAD_MODULES="true"
    
    # Default configuration files for your hardware if any
    LIRCMD_CONF=""
    
    #Forcing noninteractive reconfiguration
    #If lirc is to be reconfigured by an external application
    #that doesn't have a debconf frontend available, the noninteractive
    #frontend can be invoked and set to parse REMOTE and TRANSMITTER
    #It will then populate all other variables without any user input
    #If you would like to configure lirc via standard methods, be sure
    #to leave this set to "false"
    FORCE_NONINTERACTIVE_RECONFIGURATION="false"
    START_LIRCMD=""
    Last edited by aseriesoftubes; December 27th, 2009 at 02:07 AM. Reason: formatting, error messages

  6. #56
    Join Date
    Feb 2008
    Location
    Chicago, IL
    Beans
    112
    Distro
    Ubuntu 12.10 Quantal Quetzal

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    Does your remote work? Because when I upgraded from 9.04 to 9.10, my remote stopped working. My hardware.conf is exactly the same, but I get nothing out of irw.

  7. #57
    Join Date
    Apr 2007
    Beans
    4
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    I don't know if someone already made a PPA for it, but if not, I made one: https://launchpad.net/~brunoqc/+archive/lirc-pvr-150

    Here's how I made it, using the patch from yfaykya.

    Get the deb sources
    Code:
    apt-get source lirc-modules-source
    cd lirc-0.8.6
    Since the deb already use Quilt to manage patches we can use that.

    (note, lines beginning with # are comments, no need to type that)
    Code:
    # set Quilt's path
    export QUILT_PATCHES=debian/patches
    
    # apply every existing patches
    quilt push -a
    
    # create a new patch
    quilt new zilog.diff
    Code:
    # add every files that will be created or modified so Quilt will be able to create a patch by tracking the changes (note that some files are not the exact same name from the diff since the patch was made to apply on the installed files).
    quilt add debian/modules-source/lirc-modules-source.conf debian/dkms.conf.in debian/modules-source/Makefile drivers/Makefile.in drivers/lirc_zilog/.deps/lirc_zilog.Po drivers/lirc_zilog/Makefile drivers/lirc_zilog/lirc_zilog.c
    The patch we got from yfaykya is supposed to be applied on installed files from the installed deb. The patch will apply cleanly but we will need to give the path of each file.

    Code:
    patch -p0 < /home/bruno/zilog.diff
    Here's the paths for the files(in the same order) :
    Code:
    debian/modules-source/lirc-modules-source.conf
    debian/dkms.conf.in
    debian/modules-source/Makefile
    drivers/Makefile.in
    Code:
    #update the patch
    quilt refresh
    The last command complain about trailing whitespaces, we could ignore that but while we are at it :

    Code:
    #destroy the trailin whitespaces
    sed -i 's/ *$//' drivers/lirc_zilog/Makefile
    #update the patch
    quilt refresh
    everything's fine now.

    Code:
    #removes all the applied patches
    quilt pop -a

    Create an updated deb
    Code:
    # set my personnal info
    export DEBFULLNAME='My name'
    export DEBEMAIL='my@email'
    
    # update the version number (I also added a ~ppa0 at the end of '0.8.6-0ubuntu3' since I'm planning to upload it to my ppa)
    dch -i
    Upload the package source to my ppa
    Code:
    # build the needed file for the upload
    debuild -S
    
    # upload to my ppa
    dput ppa:brunoqc/lirc-pvr-150 ../lirc_0.8.6-0ubuntu3~ppa0_source.changes

    I could also build the package locally
    Code:
    # Install the required dependencies
    sudo apt-get build-dep lirc-modules-source
    
    # build the package
    dpkg-buildpackage -us -uc
    
    # install
    sudo dpkg -i ../lirc-modules-source_0.8.6-0ubuntu3~ppa0_all.deb
    Now we have a nice deb using a quilt patch so it's easier to maintain.

    We could also send a diff to the package maintainers using :
    Code:
    debdiff lirc_0.8.6-0ubuntu2.dsc lirc_0.8.6-0ubuntu3~ppa0.dsc > difftosend.diff
    I'm not sure if it would be accepted since the patch name (zilog.diff) may not follow a naming convention and also I guess "new feature" may only go in the lucid.

    PackagingGuide/Howtos/Quilt
    Last edited by bloodqc; February 21st, 2010 at 10:15 PM.

  8. #58
    Join Date
    Apr 2007
    Beans
    4
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    I got a WinTV-HVR 1600 and I don't see any chip found or that the firmware is getting loaded. I only have 'lircd' in /dev. Any ideas?

    I have haup-ir-blaster.bin in /lib/firmware. I'm using mythbuntu 9.10 (32 bits).

    Code:
    [  822.169377] lirc_zilog: Zilog/Hauppauge IR driver initializing
    [  822.174097] lirc_zilog: initialization complete

  9. #59
    Join Date
    Dec 2007
    Beans
    51

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    I came upon this thread after getting stuck doing research. Apparently I'm not the only frustrated user with an PVR-150.

    I've been using lirc_zilog successfully with ubuntu for since October 2009. I got an version from Jarod Wilson that seemed to work great. I still had to go through a dozen hoops every time I upgraded my kernel, but it was at least do-able.

    Today I came to my system and noticed that it was no longer able to change channels. I hadn't rebooted the machine with a kernel upgrade, but I was suddenly getting the error:

    irsend: command failed: SEND_ONCE blaster DISPLAY
    irsend: hardware does not support sending

    Digging deeper into syslog I found:

    Mar 27 00:32:33 pergamon lircd-0.8.6[7464]: accepted new client on /var/run/lirc/lircd
    Mar 27 00:32:33 pergamon lircd-0.8.6[7464]: could not get file information for /dev/lirc0
    Mar 27 00:32:33 pergamon lircd-0.8.6[7464]: default_init(): No such file or directory
    Mar 27 00:32:33 pergamon lircd-0.8.6[7464]: Failed to initialize hardware
    Mar 27 00:32:33 pergamon lircd-0.8.6[7464]: error processing command: SEND_ONCE blaster DISPLAY
    Mar 27 00:32:33 pergamon lircd-0.8.6[7464]: hardware does not support sending
    Mar 27 00:32:33 pergamon lircd-0.8.6[7464]: removed client

    And lo an behold /dev/lirc0 was completely missing.

    I reinstalled the drivers, lirc_dev and lirc_zilog were starting up without error:

    $ sudo rmmod lirc_zilog lirc_dev
    $ sudo modprobe lirc_dev
    $ sudo modprobe lirc_zilog
    $ sudo pkill lircd
    $ sudo /usr/local/sbin/lircd --device=/dev/lirc0

    Generated a syslog of:

    Mar 27 00:42:36 pergamon kernel: [ 2309.926826] lirc_zilog: Zilog/Hauppauge IR driver unloaded
    Mar 27 00:42:36 pergamon kernel: [ 2309.926826] lirc_zilog: Zilog/Hauppauge IR driver unloaded
    Mar 27 00:42:46 pergamon kernel: [ 2319.945691] lirc_dev: IR Remote Control driver registered, major 61
    Mar 27 00:42:46 pergamon kernel: [ 2319.945691] lirc_dev: IR Remote Control driver registered, major 61
    Mar 27 00:42:51 pergamon kernel: [ 2325.274382] lirc_zilog: Zilog/Hauppauge IR driver initializing
    Mar 27 00:42:51 pergamon kernel: [ 2325.275654] lirc_zilog: initialization complete
    Mar 27 00:42:51 pergamon kernel: [ 2325.274382] lirc_zilog: Zilog/Hauppauge IR driver initializing
    Mar 27 00:42:51 pergamon kernel: [ 2325.275654] lirc_zilog: initialization complete

    I don't see a single error in the logs (double and triple checked, I promise!) and lircd seems to start up perfectly, and yet /dev/lirc* doesn't exist.

    I have no idea why the system spontaneously decided it couldn't change channels. I'm wondering if the card has gotten too old, or if something changed in a latest non-kernal ubuntu update.

    I know I'm missing something, I'm out of ideas on where to look.

    Help!

    EDIT: Just to clarify, I'm using a PVR-150 in Ubuntu 9.10 and an externally mounted IR blaster. I've got a DCT terminal and this really has been working great for months. No clue why it's stopped.

    Trevor Bradley
    Last edited by TrevorBradley; March 27th, 2010 at 09:09 AM.

  10. #60
    Join Date
    Dec 2007
    Beans
    51

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    OK, that last post was just too vague for me not to dig deeper.

    If the system spontaneously stopped working, the logs would show it if I dug back far enough.

    Low and behold at 7pm this evening (about 6 hours ago) my syslog started spitting out this:

    Mar 26 16:59:56 pergamon lircd-0.8.6[3691]: accepted new client on /var/run/lirc/lircd
    Mar 26 16:59:58 pergamon kernel: [6057235.488118] lirc_zilog: IR TX chip never got ready: last i2c_master_send failed with -121
    Mar 26 16:59:58 pergamon kernel: [6057235.488122] lirc_zilog: sending to the IR transmitter chip failed, trying reset
    Mar 26 16:59:58 pergamon kernel: [6057235.600855] lirc_zilog: i2c_master_send failed with -121
    Mar 26 16:59:58 pergamon kernel: [6057235.600859] lirc_zilog: sending to the IR transmitter chip failed, trying reset
    Mar 26 16:59:58 pergamon kernel: [6057235.716540] lirc_zilog: i2c_master_send failed with -121
    Mar 26 16:59:58 pergamon kernel: [6057235.716544] lirc_zilog: sending to the IR transmitter chip failed, trying reset
    Mar 26 16:59:58 pergamon kernel: [6057235.823289] lirc_zilog: i2c_master_send failed with -121
    Mar 26 16:59:58 pergamon lircd-0.8.6[3691]: write failed
    Mar 26 16:59:58 pergamon kernel: [6057235.823293] lirc_zilog: sending to the IR transmitter chip failed, trying reset
    Mar 26 16:59:58 pergamon kernel: [6057235.823294] lirc_zilog: unable to send to the IR chip after 3 resets, giving up
    Mar 26 16:59:56 pergamon lircd-0.8.6[3691]: accepted new client on /var/run/lirc/lircd
    Mar 26 16:59:58 pergamon kernel: [6057235.488118] lirc_zilog: IR TX chip never got ready: last i2c_master_send failed with -121
    Mar 26 16:59:58 pergamon kernel: [6057235.488122] lirc_zilog: sending to the IR transmitter chip failed, trying reset
    Mar 26 16:59:58 pergamon kernel: [6057235.600855] lirc_zilog: i2c_master_send failed with -121
    Mar 26 16:59:58 pergamon kernel: [6057235.600859] lirc_zilog: sending to the IR transmitter chip failed, trying reset
    Mar 26 16:59:58 pergamon kernel: [6057235.716540] lirc_zilog: i2c_master_send failed with -121
    Mar 26 16:59:58 pergamon kernel: [6057235.716544] lirc_zilog: sending to the IR transmitter chip failed, trying reset
    Mar 26 16:59:58 pergamon kernel: [6057235.823289] lirc_zilog: i2c_master_send failed with -121
    Mar 26 16:59:58 pergamon lircd-0.8.6[3691]: write failed
    Mar 26 16:59:58 pergamon kernel: [6057235.823293] lirc_zilog: sending to the IR transmitter chip failed, trying reset
    Mar 26 16:59:58 pergamon kernel: [6057235.823294] lirc_zilog: unable to send to the IR chip after 3 resets, giving up

    Before this time there were no errors of this type. Afterward they repeat for a while, and then stop when I try to reinstall my drivers.

    I checked my symantec logs, I updated about 8 hours before this, and had recordings with proper lirc channel changes an hour before. The update wasn't the source of the fault.

    I'm starting to seriously wonder if the transmitter is burned out on the PVR card... "i2c_master_send failed with -121" sounds suspicious to me...

Page 6 of 9 FirstFirst ... 45678 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •