[pvrusb2] Brand new HVR-1950 - no IR device!

[Michael Krufky]

I normally post my replies below the quote, but this isn't my list to police, so I will keep to the quoting style of the thread. 

Anyhow, Nat:

You are attempting to utilize a device at i2c address 0x1a as an IR receiver, but this will not work for you, since the device at 0x1a is in fact NOT an IR receiver.

The device at 0x1a is the atsc/qam demodulator.  This particular ic has 16-bit registers, so when you address it using only 8 bits, results are unpredictable.  This might be related to "[ 8780.549011] pvrusb2: Timed out control-write" message, which later rendered the device inoperable.

The above has nothing to do with the issue at hand, but I mention it now so that it will be known for the future.

What you *should* do instead, is deal with the zilog ir blaster / receiver.  This ic is located at i2c address 0x71, iirc.  If not 0x71, then 0x72 or something in that neighborhood.  (The zilog is actually addressable at multiple locations on the same unit, but that is a discussion beyond the scope of this thread)

In the end, the issue is that you are using the wrong LIRC configuration.  I can't blame you for this, since the pvrusb2 24xxx models did use the fx2-style IR located at pseudo i2c address 0x1a ( or was that 0x18 ? -- I forget ) , and that IR solution emulated the previous IR solution provided by the 29xxx units.

What you actually need to do is configure this IR receiver device as if it was a zilog commonly found on a Hauppauge PVR150.  I believe that lirc has a predefined configuration for this, called "lirc_pvr150" or something.

I hope this helps.

Regards,

Mike Krufky

Nat Tellin wrote:
> Well...turns out I'm not crazy.
> 
> When I thought it had started working, I had only stumbled on to a bigger issue.
> 
> Usually, by just plugging in the device, no IR device is created.
> dmesg | grep lirc is blank.
> If instead the module is unloaded and then reloaded without unplugging
> the device, lirc related messages show up in dmesg. It's very strange
> that the IR device is only detected some portion of the time...
> From a test just now it seems that unloading and reloading lirc_i2c
> can also trigger lirc0 showing up.
> 
> The appearance of lirc0 (apparently by me poking around modules just
> right by accident) made me think it was working. At that point I
> thought the remote would work as soon as I configured lirc correctly
> (which it still doesn't). But then I noticed dmesg:
> 
> [ 8774.740210] lirc_dev: IR Remote Control driver registered, at major 61
> [ 8774.986600] lirc_i2c: chip 0x10005 found @ 0x1a (Hauppauge IR)
> [ 8774.986656] lirc_dev: lirc_register_plugin: sample_rate: 10
> [ 8780.549011] pvrusb2: Timed out control-write
> [ 8780.549025] pvrusb2: Device being rendered inoperable
> [ 8780.549626] pvrusb2: Attempted to execute control transfer when device not ok
> [ 8780.549635] pvrusb2: Attempted to execute control transfer when device not ok
> [ 8780.549641] pvrusb2: Attempted to execute control transfer when device not ok
> [ 8780.549646] pvrusb2: Attempted to execute control transfer when device not ok
> [ 8780.549651] pvrusb2: Attempted to execute control transfer when device not ok
> [ 8780.549656] pvrusb2: Attempted to execute control transfer when device not ok
> 
> That sample is from reloading lirc_i2c. The same thing occurs no
> matter how I get the IR device detected (though the errors may start
> showing up at some other point).
> 
> I'm not sure what has to happen exactly to trigger the error, but I do
> know that checking dmesg after playing with lirc stuff for a bit
> (including trying to echo button presses to a terminal), that same
> message filled pages...
> 
> Perhaps this will help to compare to other models?
> [ 9663.139266] tveeprom 1-00a2: Hauppauge model 75111, rev C3E9, <snip>
> 
> On Thu, Jul 17, 2008 at 6:36 PM, Nat Tellin <nat.tellin at gmail.com> wrote:
>> It's workingnnow. I really can't speculate as to why. Tuner gremlins?
>>
>> If it starts occuring again and I can determine a repeatable cause,
>> I'll be sure to let you know.
>>
>> On Thu, Jul 17, 2008 at 6:06 PM, Nat Tellin <nat.tellin at gmail.com> wrote:
>>> HVR-1950 support seems to be a bit new. I had to compile from a
>>> snapshot to get a working module.
>>>
>>> The meat of the device seems to be detected ok. Still getting MythTV
>>> set up though.
>>>
>>> My issue is that no IR device gets created.
>>>  tveeprom 1-00a2: has radio, has IR receiver, has IR transmitter
>>> from dmesg looks promising, but there are no i2c or lirc related
>>> messages after that, and nothing shows up in /dev.
>>>
>>> This unit just arrived today. Maybe they're playing revision games
>>> again or maybe I'm missing something obvious.
>>>
>>> What info would you like or what should I try?
>>>
>>> Thanks.
>>>
> _______________________________________________
> pvrusb2 mailing list
> pvrusb2 at isely.net
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2