[pvrusb2] hvr-1900, mythtv and remote

[Mike Isely]

On Sat, 21 Mar 2009, Mike Isely wrote:

> On Sat, 21 Mar 2009, Aljaž Prusnik wrote:
> 
> > Hi!
> > 
> > I have searched all possible sources on this but still can't get the
> > device to work with mythtv or somehow activate the remote. All I can get
> > is to get it played with mplayer.

Forgot to comment on the IR side of this.

Please try the device without attempting to set up IR first.  The IR 
setup on the HVR-1900/1950 is something I'm not very clear about.  There 
have been multiple posts in the past about people having trouble with 
this, and some anecdotal bits that suggest LIRC might have some issues 
here.  And it is theoretically possible that a misbehaving IR chip could 
interfere with other I2C transfers, potentially causing errors like you 
report further down.  Note: I'm just guessing here, I have *NOT* seen 
any hard evidence to confirm this sort of scenario, but testing without 
any IR driver installed should eliminate that as a possible cause of 
trouble.

  -Mike

> > 
> > This model as I gather is the European brother of the 1950. Based on the
> > log messages I presume I'm dealing with the same hardware.
> > 
> > Now, what do these messages mean that I get them after selecting the
> > option Watch TV on mythtv (mythbuntu jaunty and was the same in
> > intrepid):
> > 
> > tda18271_read_regs: ERROR: i2c_transfer returned: -5
> > tda18271_ir_cal_init: error -5 on line 786
> > tda18271_init: error -5 on line 810
> 
> The error code suggests problems performing I2C transfers on the local 
> bus within the device.  If there were actual I2C problems then I'd 
> expect communication with all chips there to be fail (should also see 
> cx25840 errors as well).
> 
> 
> > 
> > I have not found a single source on google about this.
> 
> First I've heard of this particular set of symptoms.
> 
> 
> > 
> > Additionally I get also these messages:
> 
> > cx25840' 1-0044: firmware: requesting v4l-cx25840.fw
> > cx25840' 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> 
> That's normal.  This will happen upon device initialization and also 
> IIRC any time the device switches to analog mode.
> 
> 
> > tda10048_readreg: readreg error (ret == -5)
> > tda10048_writereg: writereg error (ret == -5)
> > tda10048_readreg: readreg error (ret == -5)
> > tda10048_writereg: writereg error (ret == -5)
> 
> This isn't normal.
> 
> 
> > 
> > It doesn't really matter if I choose mpeg2 or analog encoder device in mythtv. 
> > 
> > If I run mplayer /dev/video0 then I only get the first two lines when cx25840 gets loaded.
> > 
> > So, is this a driver problem or mythtv problem?
> 
> Probably a driver or hardware problem.  It should not be possible for an 
> app to play a part in I2C errors deep down in the driver.  However, it's 
> not clear from your message whether or not mplayer /dev/vide0 actually 
> worked for you.  That would be useful to know.
> 
> Other items that would be useful to know include:
> 
> 1. Kernel version.
> 
> 2. Which pvrusb2 driver you are using (in-kernel, using a v4l-dvb 
> snapshot, or which standalone driver snapshot you are using).
> 
> The process for running the device in analog mode is somewhat easier to 
> test, even though the hardware in that case is more complex.  Test the 
> composite or s-video input (use mplayer).  If that works, try an RF 
> channel in analog mode (which uses everything that composite or s-video 
> uses plus the RF tuner).  If that works then the issue is narrowed to 
> something DVB-specific, which is also useful to know.
> 
>   -Mike
> 
> 

-- 

Mike Isely
isely @ pobox (dot) com
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8