[mythtv-users] HDPVR setup irsend error

[Jarod Wilson]

On Sun, Jan 17, 2010 at 10:29 AM, steve <networks1 at cox.net> wrote:
>>>>> After John helped me find the lirc hardware conf file (thanks, John) I
>
>>>>> completed the setup for the HDPVR ir blaster.  The next step in the
>>>>> wiki
>
>>>>> http://mythtv.org/wiki/HDPVR is to find the right codeset.  The wiki
>
>>>>> suggests running a script, but since my box has only a few
>>>>> possibilities
>
>>> I
>
>>>>> decided to run the test commands manually.  When I enter
>
>>>>>
>
>>>>> irsend SEND_ONCE blaster 0_74_KEY_POWER
>
>>>>>
>
>>>>> I get
>
>>>>>
>
>>>>> irsend: command failed: SEND_ONCE blaster 0_74_KEY_POWER
>
>>>>>
>
>>>>> irsend: hardware does not support sending
>
>>>>>
>
>>>>> The only thing I'm not sure about from the setup is that step 6 in the
>
>>> wiki
>
>>>>> says I may have to adjust the device and socket values in the conf
>>>>> file.
>
>>>>> There is no lirc0 in /dev and I don't know how to determine if there
>
>>> should
>
>>>>> be a non-null socket value.
>
>>>>
>
>>>>If you have no /dev/lirc0, then you have no successfully loaded lirc
>
>>>>kernel drivers. Did you modprobe lirc_zilog?
>
>>>
>
>>>>
>
>>>
>
>>> Yes I did, and lsmod lists it.  When I ran modprobe lirc_zilog, I got a
>
>>> bunch of output I didn't know how to interpret, a line listing the module
>
>>> file followed by several saying something about the kernel and a series
>>> of
>
>>> hex numbers.  I don't use modprobe enough to know if that's normal.
>>>  Nothing
>
>>> clearly looked like an error tho.
>
>>
>
>>That doesn't sound normal. Please send that output along and I'll take
>
>>a look at it.
>
>
>
> I guess there was an error after all…
>
>
>
> [root at mythtv mythtv]# modprobe lirc_zilog
>
> Killed
>
> [root at mythtv mythtv]# Message from syslogd at localhost at Jan 17 08:20:54 ...
>
>  kernel:Oops: 0000 [#1] SMP
>
>
>
> Message from syslogd at localhost at Jan 17 08:20:54 ...
>
>  kernel:last sysfs file:
> /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-6/i2c-adapter/i2c-1/1-0071/firmware/1-0071/loading
>
>
>
> Message from syslogd at localhost at Jan 17 08:20:54 ...
>
>  kernel:Stack:
>
>
>
> Message from syslogd at localhost at Jan 17 08:20:54 ...
>
>  kernel:Call Trace:
>
>
>
> Message from syslogd at localhost at Jan 17 08:20:54 ...
>
>  kernel:Code: cd f4 90 e0 b8 c8 ff ff ff e9 35 01 00 00 48 63 c7 48 c7 c7 d0
> f3 b0 a0 89 75 d8 48 8b 1c c5 20 fa b0 a0 e8 fd 07 91 e0 8b 75 d8 <44> 8b 63
> 28 41 39 f4 74 24 48 c7 c7 24 cf b0 a0 31 c0 e8 8f f4
>
>
>
> Message from syslogd at localhost at Jan 17 08:20:54 ...
>
>  kernel:CR2: 0000000000000028

Yep, that's bad. What that looks like is not having the blaster
firmware downloaded into the right place on your system...


-- 
Jarod Wilson
jarod at wilsonet.com