Page 3 of 9 FirstFirst 12345 ... LastLast
Results 21 to 30 of 84

Thread: Using PVR150 IR Blaster In Mythbuntu 9.10b

  1. #21
    Join Date
    Oct 2007
    Beans
    13

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    The lirc I have installed is 0.8.6 (0.8.6-0ubuntu2)

  2. #22
    Join Date
    Nov 2006
    Beans
    137

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    I try this sudo patch -p0 < ~/Downloads/zilog.diff . it works on the version 0.8.6.

    What are the next step?

    Can you provide your lircd.conf and hardware.conf

    Thanks
    Last edited by Kheops_74; November 2nd, 2009 at 01:04 AM.

  3. #23
    Join Date
    Oct 2007
    Beans
    13

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    Try :

    sudo dkms remove -m lirc -v 0.8.6 --all
    sudo dkms add -m lirc -v 0.8.6
    sudo dkms build -m lirc -v 0.8.6

    sudo depmod -a
    sudo modprobe lirc_zilog

    That should be it. Make sure f/w is in right place.

  4. #24
    Join Date
    Nov 2006
    Beans
    17

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    Ah yes, my mistake, I was on the wrong machine! I have successfully built lirc_zilog with the patch from yfaykya:

    Code:
    sudo apt-get install lirc-modules-source
    cd /usr/src/lirc-0.8.6
    sudo patch -p0 < ~/Downloads/zilog.diff
    sudo dpkg-reconfigure lirc-modules-source
    That did a reconfigure and I verified that it is loaded with dmsg:
    Code:
    $ dmesg | grep lirc_zilog
    [   29.816772] lirc_zilog: Zilog/Hauppauge IR driver initializing
    [   29.819735] lirc_zilog: chip found with RX and TX
    [   29.905432] lirc_zilog: Zilog/Hauppauge IR blaster firmware version 1.3.0 loaded
    [   29.905505] lirc_zilog: initialization complete
    I fixed the config files to use lirc_zilog but it seems now I have a configuration problem with lirc:
    Code:
    $ irsend SEND_ONCE DCT700 power
    irsend: command failed: SEND_ONCE DCT700 power
    irsend: hardware does not support sending
    I will keep working on it, but any help is appreciated!
    Jim

  5. #25
    Join Date
    Feb 2008
    Beans
    5

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    Thanks... I have it working now too... Be sure to place the firmware in /lib/firmware

    There is an issue though.. I had to patch the daemons/config_file.c to allow the longer id's for the dishnetwork remotes... I used the file my .85 patched lirc source. It compiled in just fine in the newer one's place
    Last edited by dherman; November 2nd, 2009 at 01:35 AM.

  6. #26
    Join Date
    Nov 2006
    Beans
    17

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    Quote Originally Posted by dherman View Post
    Thanks... I have it working now too... Be sure to place the firmware in /lib/firmware
    You mean putting http://www.blushingpenguin.com/mark/...ir-blaster.bin in /lib/firmware? I did that, but still no luck.
    Jim

  7. #27
    Join Date
    Feb 2008
    Beans
    5

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    check you /var/log/syslog and /var/log/messages

    anything interesting??

  8. #28
    Join Date
    Nov 2006
    Beans
    17

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    I got it working! The problem was that my hardware.conf was pointing to /dev/lirc1 and not /dev/lirc0.

    So to recap the steps I took to get everything working:

    Code:
    sudo apt-get install lirc-modules-source
    cd /usr/src/lirc-0.8.6
    sudo patch -p0 < ~/Downloads/zilog.diff
    sudo dpkg-reconfigure lirc-modules-source
    then open /etc/lirc/hardware.conf and modify TRANSMITTER_MODULES to this:
    Code:
    TRANSMITTER_MODULES="lirc_dev lirc_zilog"
    Then I followed http://www.blushingpenguin.com/mark/blog/?p=24, steps 6, 8-13

    Now everything is great and my life is sane.
    Thanks everyone!
    Jim

  9. #29
    Join Date
    Nov 2006
    Beans
    137

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    Can you provide your lircd.conf and hardware.conf. I still have the "irsend: hardware does not support sending" message. I think, i'm not far away.

    Thanks

  10. #30
    Join Date
    Nov 2006
    Beans
    17

    Re: Using PVR150 IR Blaster In Mythbuntu 9.10b

    Quote Originally Posted by Kheops_74 View Post
    Can you provide your lircd.conf and hardware.conf. I still have the "irsend: hardware does not support sending" message. I think, i'm not far away.

    Thanks
    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=""
    lircd.conf:
    Code:
    begin remote
    
      name          blaster
      bits          32
      flags         RAW_CODES
      eps           0
      aeps          0
      plead         0
      gap           333333
      repeat_bit    0
      begin raw_codes
        name 0_82_KEY_0
        5373952
        name 0_82_KEY_1
        5373953
        name 0_82_KEY_2
        5373954
        name 0_82_KEY_3
        5373955
        name 0_82_KEY_4
        5373956
        name 0_82_KEY_5
        5373957
        name 0_82_KEY_6
        5373958
        name 0_82_KEY_7
        5373959
        name 0_82_KEY_8
        5373960
        name 0_82_KEY_9
        5373961
        name 0_82_KEY_POWER
        5373962
        name 0_82_KEY_CH_UP
        5373967
        name 0_82_KEY_CH_DOWN
        5373968
        name 0_82_KEY_MUTE
        5373969
        name 0_82_KEY_VOL_DOWN
        5373970
        name 0_82_KEY_VOL_UP
        5373972
        name 0_82_KEY_MNSELECT
        5373975
        name 0_82_KEY_ENTER
        5373995
        name 0_82_KEY_MENU
        5373999
        name 0_82_KEY_MUP
        5374000
        name 0_82_KEY_MDOWN
        5374001
        name 0_82_KEY_MLEFT
        5374002
        name 0_82_KEY_MRIGHT
        5374003
      end raw_codes
    end remote
    look at syslog if you run into problems:
    Code:
    tail /var/log/syslog

Page 3 of 9 FirstFirst 12345 ... 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
  •