Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

mythdora lirc problems, remote+serial blaster

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


wstotz at toad

Sep 5, 2010, 7:39 AM

Post #1 of 8 (649 views)
Permalink
mythdora lirc problems, remote+serial blaster

I'm running Mythdora 12.23 with a Hauppauge 250 and am having trouble with
both the Hauppauge remote and a serial blaster. The reciever is the one
that plugs into the back of the Hauppauge card and the blaster is a
homebuilt LED+resistor+diode from the Lirc page.

When I first installed the system, and used the Mythdora IR devices
configuration tool to set up just the remote, it worked fine. Later when I
used the configuration tool to add the blaster, the remote stopped working
and the blaster never worked. I chose the option that said
"serial/IguannaWorks IR Blaster(COM1)". Since I didn't make any manual
changes outside of the config tool I'm assuming that the tool messed up
the settings.

I've followed the various troubleshooting sources that I can find, but
many of them are old or are for MythBuntu, which seems to have a different
configuration. I'm hoping someone can see the problem from what I've
posted here or can walk me through the correct troubleshooting steps.

I know the light is flashing on the Hauppauge remote but I can't get any
output from irw. When I add the channel change script to Myth I get error
messages in the backend log that say:

irsend: command failed: SEND_ONCE Pace_RC-30 6
irsend: hardware does not support sending
irsend: command failed: SEND_ONCE Pace_RC-30 6
irsend: hardware does not support sending
irsend: command failed: SEND_ONCE Pace_RC-30 OK
irsend: hardware does not support sending

Note that my remote is actually the Pace DC50X but that's not listed in
the configuration tool. I figured I would worry about the actual remote
type later after I got the blaster light to flash.

Here are the results of some of the troubleshooting commands I have found.
Let me know what other info I can provide.


$ dmesg | grep lirc
lirc_dev: IR Remote Control driver registered, major 248
lirc_serial: auto-detected active high receiver
lirc_serial lirc_serial.0: lirc_dev: driver lirc_serial registered at
minor = 0
lirc_i2c: chip 0x0 found @ 0x18 (Hauppauge IR)
i2c ir driver 0-0018: lirc_dev: driver lirc_i2c registered at minor = 1

$ ls -l /dev/lirc*
crw-rw---- 1 root root 248, 0 2010-09-04 18:39 /dev/lirc0
crw-rw---- 1 root root 248, 1 2010-09-04 18:39 /dev/lirc1
srw-rw-rw- 1 root root 0 2010-09-04 18:39 /dev/lircd1

$ dmesg /var/log | grep 16550A
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

$ irsend list "" ""
irsend: Hauppauge_350

/etc/modprobe.d/lirc.conf
#lirc_module_configuration
alias char-major-61 lirc_i2c

/etc/modprobe.d/lirc-blaster.conf
options lirc_serial irq=4 io=0x3f8
install lirc_serial /bin/setserial /dev/ttyS0 uart none;/sbin/modprobe
--ignore-install lirc_serial

/etc/rc.d/rc.local
#!/bin/bash
# This file allows you to execute things at the end of boot
touch /var/lock/subsys/local

#lircd startup check for irblasters
/usr/share/mythdora/mdconfigroot/scripts/irblaster-lircd.sh

Thanks,

Jamie


_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


jarod at wilsonet

Sep 5, 2010, 9:37 AM

Post #2 of 8 (593 views)
Permalink
Re: mythdora lirc problems, remote+serial blaster [In reply to]

On Sun, Sep 5, 2010 at 10:39 AM, Jamie Stotz <wstotz [at] toad> wrote:
> I'm running Mythdora 12.23 with a Hauppauge 250 and am having trouble with
> both the Hauppauge remote and a serial blaster. The reciever is the one
> that plugs into the back of the Hauppauge card and the blaster is a
> homebuilt LED+resistor+diode from the Lirc page.
>
> When I first installed the system, and used the Mythdora IR devices
> configuration tool to set up just the remote, it worked fine. Later when I
> used the configuration tool to add the blaster, the remote stopped working
> and the blaster never worked. I chose the option that said
> "serial/IguannaWorks IR Blaster(COM1)". Since I didn't make any manual
> changes outside of the config tool I'm assuming that the tool messed up
> the settings.

The IguanaWorks IR Blaster is a different device from a homebrew
serial device, so that's likely at least one reason why its not
working. lircd is trying to talk to an IguanaWorks device, which uses
a userspace driver, instead of using the "default" driver (connect to
a /dev/lircX device that has a kernelspace driver).

> I've followed the various troubleshooting sources that I can find, but
> many of them are old or are for MythBuntu, which seems to have a different
> configuration. I'm hoping someone can see the problem from what I've
> posted here or can walk me through the correct troubleshooting steps.
>
> I know the light is flashing on the Hauppauge remote but I can't get any
> output from irw. When I add the channel change script to Myth I get error
> messages in the backend log that say:
>
> irsend: command failed: SEND_ONCE Pace_RC-30 6
> irsend: hardware does not support sending
> irsend: command failed: SEND_ONCE Pace_RC-30 6
> irsend: hardware does not support sending
> irsend: command failed: SEND_ONCE Pace_RC-30 OK
> irsend: hardware does not support sending

Yep, that's not unexpected, given the device type mismatch.


--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


wstotz at toad

Sep 5, 2010, 10:35 AM

Post #3 of 8 (589 views)
Permalink
mythdora lirc problems, remote+serial blaster [In reply to]

In the IR Devices config tool my only choices are:

No IR Blaster
Serial/IguanaWorks IR Blaster (COM1)
Serial/IguanaWorks IR Blaster (COM2)
PVR-150 IR Reciever/Blaster
MCE-USB IR Blaster
CommandIR Mini
CommandIR II
USB-UIRT IR Blaster

Jamie

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


wstotz at toad

Sep 5, 2010, 10:38 AM

Post #4 of 8 (578 views)
Permalink
mythdora lirc problems, remote+serial blaster [In reply to]

By the way, running the config tool the remove the blaster and go back to
only the Hauppauge remote doesn't make the remote work again.

Jamie

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


jarod at wilsonet

Sep 5, 2010, 1:12 PM

Post #5 of 8 (585 views)
Permalink
Re: mythdora lirc problems, remote+serial blaster [In reply to]

On Sun, Sep 5, 2010 at 1:35 PM, Jamie Stotz <wstotz [at] toad> wrote:
> In the IR Devices config tool my only choices are:
>
> No IR Blaster
> Serial/IguanaWorks IR Blaster (COM1)
> Serial/IguanaWorks IR Blaster (COM2)
> PVR-150 IR Reciever/Blaster
> MCE-USB IR Blaster
> CommandIR Mini
> CommandIR II
> USB-UIRT IR Blaster

Hrm. Perhaps I'm wrong, and the IguanaWorks serial blasters use
lirc_serial. Its certainly not any of the other options there. What
does /etc/sysconfig/lirc look like? And /etc/lirc/lircd.conf?

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


jarod at wilsonet

Sep 5, 2010, 1:15 PM

Post #6 of 8 (586 views)
Permalink
Re: mythdora lirc problems, remote+serial blaster [In reply to]

On Sun, Sep 5, 2010 at 1:38 PM, Jamie Stotz <wstotz [at] toad> wrote:
> By the way, running the config tool the remove the blaster and go back to
> only the Hauppauge remote doesn't make the remote work again.

Based on your dmesg output, its at /dev/lirc1, and lircd by default
expects it at /dev/lirc0 (which is the device lirc_serial is bound
to). Multi-device is... messy, even if you fully understand how all
the parts are wired together. Point lircd at /dev/lirc1 instead, and
the remote should work again (look for the device setting in
/etc/sysconfig/lirc), but beware that if you change module load order
between lirc_i2c and lirc_serial, they'll flip-flop.

--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


wstotz at toad

Sep 5, 2010, 3:30 PM

Post #7 of 8 (584 views)
Permalink
mythdora lirc problems, remote+serial blaster [In reply to]

/etc/sysconfig/lirc is empty

/etc/lirc/lircd.conf looks like this:
#
# this config file was automatically generated
# using lirc-0.7.0(any) on Sun Nov 28 20:25:09 2004
#
# contributed by
#
# brand: Hauppauge 350
# Created: G.J. Werler (The Netherlands)
# Project: Mythtv Fedora Pundit-R www.mythtvportal.com
# Date: 2004/11/28
# model no. of remote control: Hauppauge A415-HPG
# devices being controlled by this remote: PVR-350
#

begin remote

name Hauppauge_350
bits 13
flags RC5|CONST_LENGTH
eps 30
aeps 100

one 969 811
zero 969 811
plead 1097
gap 114605
toggle_bit 2


begin codes
Go 0x00000000000017BB
Power 0x00000000000017BD
TV 0x000000000000179C
Videos 0x0000000000001798
Music 0x0000000000001799
Pictures 0x000000000000179A
Guide 0x000000000000179B
Radio 0x000000000000178C
Up 0x0000000000001794
Left 0x0000000000001796
Right 0x0000000000001797
Down 0x0000000000001795
OK 0x00000000000017A5
Back/Exit 0x000000000000179F
Menu/i 0x000000000000178D
Vol+ 0x0000000000001790
Vol- 0x0000000000001791
Prev.Ch 0x0000000000001792
Mute 0x000000000000178F
Ch+ 0x00000000000017A0
Ch- 0x00000000000017A1
Record 0x00000000000017B7
Stop 0x00000000000017B6
Rewind 0x00000000000017B2
Play 0x00000000000017B5
Forward 0x00000000000017B4
Replay/SkipBackward 0x00000000000017A4
Pause 0x00000000000017B0
SkipForward 0x000000000000179E
1 0x0000000000001781
2 0x0000000000001782
3 0x0000000000001783
4 0x0000000000001784
5 0x0000000000001785
6 0x0000000000001786
7 0x0000000000001787
8 0x0000000000001788
9 0x0000000000001789
Asterix 0x000000000000178A
0 0x0000000000001780
# 0x000000000000178E
Red 0x000000000000178B
Green 0x00000000000017AE
Yellow 0x00000000000017B8
Blue 0x00000000000017A9
end codes

end remote

/etc/lircd.conf is the same plus a similar section labeled Pace RC30

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


jarod at wilsonet

Sep 5, 2010, 4:52 PM

Post #8 of 8 (584 views)
Permalink
Re: mythdora lirc problems, remote+serial blaster [In reply to]

On Sun, Sep 5, 2010 at 6:30 PM, Jamie Stotz <wstotz [at] toad> wrote:
> /etc/sysconfig/lirc is empty

Completely empty? Or just nothing added to any of the config options
in there? Empty in either case means lircd using /dev/lirc0 and the
"default" driver (i.e., attach to a kernel device), which given that
you've got lirc_serial loading first, means lircd is trying to talk to
your transmitter. However, if I'm remembering clearly (btw, while
trimming replies is appreciated, its also possible to trim too much
from a reply...), you were getting a message about the device not
supporting transmit. Not quite sure what to suggest right now. I'd
probably reverse the load order though, so lirc_i2c loads first, then
the remote should at least work. I'm really not all that familiar with
the auto-config stuff in mythdora myself, not sure how the blaster
setup is supposed to have come out.

> /etc/lirc/lircd.conf looks like this:
> #
> # this config file was automatically generated
> # using lirc-0.7.0(any) on Sun Nov 28 20:25:09 2004
> #
> # contributed by
> #
> # brand:   Hauppauge 350
...
> /etc/lircd.conf is the same plus a similar section labeled Pace RC30

Should only have one or the other, not both. Not sure which one takes
precedence.


--
Jarod Wilson
jarod [at] wilsonet
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.