[pvrusb2] HVR-1950 stopped working.

[Nicholas Robbins]

Inline

> See below...
> 
> On Tue, 15 Sep 2009, Nicholas Robbins wrote:
> 
> > So, in an attempt to get my remote working with my
> HVR-1950, I 
> > upgraded my kernel from 2.6.26 ro 2.6.30. This broke
> another capture 
> > device, so I decided to go back. (I have another
> remote what works 
> > mostly fine.)
> 
> There's a number of diagnostic steps you can take to figure
> out what's 
> going on.  Actually I've described this numerous times
> but strangely 
> enough it's not in the documentation (just random posts on
> this list).  
> I think I need to formally write this up...
> 
> Read on...
> 
> > 
> > However, on going back, my HVR-1950 doesn't work
> anymore. As far as I 
> > can tell, I've reverted everything, rebuilt the kernel
> (using 
> > in-kernel driver for the HVR) with the same .config I
> was using 
> > before, rebuilt all external modules, etc. Here is the
> current 
> > behavior:
> > 
> > 1) The HVR only captures solid black. But does so at a
> fairly high 
> > bitrate of black.
> > 
> > 2) I looked through my dmesg and /var/log/messages and
> I noticed this:
> > 
> > Sep 14 20:18:12 babel usbcore: registered new
> interface driver pvrusb2
> > Sep 14 20:18:12 babel pvrusb2: Hauppauge
> WinTV-PVR-USB2 MPEG2 Encoder/Tuner : V4L in-tree version
> > Sep 14 20:18:12 babel pvrusb2: Debug mask is 31
> (0x1f)
> > Sep 14 20:18:13 babel firmware: requesting
> v4l-pvrusb2-73xxx-01.fw
> > Sep 14 20:18:13 babel pvrusb2: Device microcontroller
> firmware (re)loaded; it should now reset and reconnect.
> > Sep 14 20:18:13 babel usb 2-3: USB disconnect, address
> 3
> > Sep 14 20:18:13 babel pvrusb2: Device being rendered
> inoperable
> > Sep 14 20:18:15 babel usb 2-3: new high speed USB
> device using ehci_hcd and address 4
> > Sep 14 20:18:15 babel usb 2-3: configuration #1 chosen
> from 1 choice
> > Sep 14 20:18:15 babel usb 2-3: reset high speed USB
> device using ehci_hcd and address 4
> > Sep 14 20:18:16 babel tuner' 3-0042: chip found @ 0x84
> (pvrusb2_a)
> > Sep 14 20:18:16 babel cx25840' 3-0044: cx25843-24
> found @ 0x88 (pvrusb2_a)
> > Sep 14 20:18:16 babel tveeprom 3-00a2: Hauppauge model
> 75111, rev C3E9, serial# 5371452
> > Sep 14 20:18:16 babel tveeprom 3-00a2: MAC address is
> 00-0D-FE-51-F6-3C
> > Sep 14 20:18:16 babel tveeprom 3-00a2: tuner model is
> Philips 18271_8295 (idx 149, type 54)
> > Sep 14 20:18:16 babel tveeprom 3-00a2: TV standards
> NTSC(M) ATSC/DVB Digital (eeprom 0x88)
> > Sep 14 20:18:16 babel tveeprom 3-00a2: audio processor
> is CX25843 (idx 37)
> > Sep 14 20:18:16 babel tveeprom 3-00a2: decoder
> processor is CX25843 (idx 30)
> > Sep 14 20:18:16 babel tveeprom 3-00a2: has radio, has
> IR receiver, has IR transmitter
> > Sep 14 20:18:16 babel pvrusb2: Supported video
> standard(s) reported available in hardware:
> PAL-M/N/Nc;NTSC-M/Mj/Mk;ATSC-8VSB/16VSB
> > Sep 14 20:18:16 babel pvrusb2: Mapping standards
> mask=0x300b700 (PAL-M/N/Nc;NTSC-M/Mj/Mk;ATSC-8VSB/16VSB)
> > Sep 14 20:18:16 babel pvrusb2: Setting up 6 unique
> standard(s)
> > Sep 14 20:18:16 babel pvrusb2: Set up standard idx=0
> name=PAL-M
> > Sep 14 20:18:16 babel pvrusb2: Set up standard idx=1
> name=PAL-N
> > Sep 14 20:18:16 babel pvrusb2: Set up standard idx=2
> name=PAL-Nc
> > Sep 14 20:18:16 babel pvrusb2: Set up standard idx=3
> name=NTSC-M
> > Sep 14 20:18:16 babel pvrusb2: Set up standard idx=4
> name=NTSC-Mj
> > Sep 14 20:18:16 babel pvrusb2: Set up standard idx=5
> name=NTSC-Mk
> > Sep 14 20:18:16 babel pvrusb2: Initial video standard
> (determined by device type): NTSC-M
> > Sep 14 20:18:16 babel pvrusb2: Device initialization
> completed successfully.
> > Sep 14 20:18:16 babel pvrusb2: registered device
> video2 [mpeg]
> > Sep 14 20:18:16 babel firmware: requesting
> v4l-cx25840.fw
> > Sep 14 20:18:17 babel cx25840' 3-0044: loaded
> v4l-cx25840.fw firmware (12559 bytes)
> > Sep 14 20:18:18 babel tda829x 3-0042: setting tuner
> address to 60
> 
> 
> > Sep 14 20:18:18 babel tda18271_attach: driver disabled
> by Kconfig
> 
> This is a problem.  Seems like you're missing the
> tuner module you need.  
> That would be a .config problem.  Are you *sure* you
> used the same 
> .config?  Is it possible that maybe you had added that
> module somehow 
> later?

I don't know. All I can tell you is that I copied the .config from where I had put it before. I looked around in menuconfig, and found the driver for tda18271 under "Device Drivers -> Multimedia Devices -> Customize analog and Hybrid tuners to build"  I enabled this option and just to be safe I  then selected all the tuners. Perhaps whichever logic in the kernel build code decides which of these to build automagically wasn't doing its magic?

So far this seems to have worked.  Catting /dev/video now produces a picture. However, the ctl_channel interface still doesn't work.  I'm at work now, and I don't have the time to check to see if MythTV can get it to work, I may have time this afternoon, but not for extensive debug. I'll let you know if this fixed all the behavior, otherwise I can put more time in on Sunday.

> Without a working tuner module that the driver can talk to,
> your RF 
> section won't function at all.  This is going to
> prevent the television 
> and the dtv inputs from functioning.  However if you
> try the composite 
> or s-video input, I'll bet that it works.
> 
> 
> > Sep 14 20:18:18 babel tda829x 3-0042: type set to
> tda8295+18271
> > Sep 14 20:18:18 babel cx25840' 3-0044: Video
> signal:              not
> present
> > Sep 14 20:18:18 babel cx25840' 3-0044: Detected
> format:           NTSC-M
> > Sep 14 20:18:18 babel cx25840' 3-0044: Specified
> standard:        NTSC-M
> > Sep 14 20:18:18 babel cx25840' 3-0044: Specified video
> input:     Composite 7
> > Sep 14 20:18:18 babel cx25840' 3-0044: Specified
> audioclock freq: 48000 Hz
> > Sep 14 20:18:18 babel cx25840' 3-0044: Detected audio
> mode:       forced mode
> > Sep 14 20:18:18 babel cx25840' 3-0044: Detected audio
> standard:   no detected audio standard
> > Sep 14 20:18:18 babel cx25840' 3-0044: Audio
> muted:           
>    no
> > Sep 14 20:18:18 babel cx25840' 3-0044: Audio
> microcontroller:     detecting
> > Sep 14 20:18:18 babel cx25840' 3-0044: Configured
> audio standard: automatic detection
> > Sep 14 20:18:18 babel cx25840' 3-0044: Configured
> audio system:   BTSC
> > Sep 14 20:18:18 babel cx25840' 3-0044: Specified audio
> input:     Tuner (In8)
> > Sep 14 20:18:18 babel cx25840' 3-0044: Preferred audio
> mode:      stereo
> > Sep 14 20:18:18 babel firmware: requesting
> v4l-cx25840.fw
> > Sep 14 20:18:20 babel cx25840' 3-0044: loaded
> v4l-cx25840.fw firmware (12559 bytes)
> > Sep 14 20:18:20 babel firmware: requesting
> v4l-cx2341x-enc.fw
> > Sep 14 20:18:23 babel go7007: unsupported ioctl
> -1069263306
> > Sep 14 20:18:23 babel wis-sony-tuner: tuning to
> frequency 61.2500 (VHF_L)
> > Sep 14 20:18:35 babel go7007: unsupported ioctl
> -1069263306
> > Sep 14 20:18:35 babel wis-sony-tuner: tuning to
> frequency 61.2500 (VHF_L)
> > Sep 14 20:18:35 babel firmware: requesting
> go7007tv.bin
> 
> > Sep 14 20:19:15 babel pvrusb2: ***WARNING*** device's
> encoder appears to be stuck (status=0x00000003)
> > Sep 14 20:19:15 babel pvrusb2: Encoder command: 0x81
> > Sep 14 20:19:15 babel pvrusb2: Giving up on
> command.  This is normally recovered by the driver.
> 
> This sequence is "normal" (for certain definitions of
> "normal").  The 
> encoder chip every once in a while crashes upon attempt to
> start 
> streaming.  It's a mystery I've never been able to
> solve, but the 
> behavior is consistent across all the different devices
> which use this 
> chip, it's fairly low probability and it only happens at
> the moment when 
> streaming is started.  The pvrusb2 driver is able to
> detect this 
> situation and it recovers it by automatically reloading the
> encoder 
> firmware and reinitializing the chip.  The entire
> recovery sequence 
> takes on the order of a second and most of the time
> probably wouldn't 
> even be noticed were it not for the dmesg output. 
> This is really only 
> worthy of note if it happens repeatedly in quick succession
> or if it 
> simply never recovers - I've personally never witnessed
> that but a few 
> others have seen it in situations where the hardware might
> actually 
> really be flakey.  I should probably change that
> message.  In any case 
> this is not likely related to the problem you are having.
 
Good to know. Sometimes dmesg says things that sound serious but aren't, guess this is one of those times.

 
> > Sep 14 20:19:15 babel firmware: requesting
> v4l-cx2341x-enc.fw
> > 
> > There is never a response to that firmware request, at
> least not one matching the cs25840 response.
> 
> That's ok.  The firmware is being loaded.  If the
> firmware load failed 
> you would actually see an error message reporting
> that.  If the firmware 
> could not be found there will be an error message
> suggesting that as a 
> cause.  But that's not the case here.

I looked around and I noticed that some other drivers were also not saying anything after they asked for firmware.

 
> > Also, I don't know if this is normal because usual my
> HVR is hidden 
> > away, but the red light on the IR reciever comes on
> when its recording 
> > its blackness.
> 
> That's actually good.  The pvrusb2 driver will turn on
> the LED whenever 
> it is trying to stream from the device, which is what you
> want.  (Note: 
> The Windows driver does something else - it seems to just
> leave that LED 
> on forever which is kind of useless.)

Good to know. I never had to mess with it before. I followed your directions and it "just worked" so it's been hidden out of sight the whole time.

> > 
> > I unplugged the device and I'm giving it a vacation
> for the day. Any 
> > thoughts about what might be going wrong?
 
> I think your problem is that the tuner module is
> missing.  The error you 
> got suggests a .config problem.  Check your .config
> and see if it is 
> actually enabled.

Looks like that was it. The /sys/.../ctl_channel control doesn't seem to work, I'll see if MythTV works this afternoon.
 
> As for more general testing, there are a number of things
> that can be 
> tried, in order of increasing complexity.  I will try
> to write this up 
> in a web page.  In your case it looks like the pvrusb2
> driver is working 
> fine and probably the hardware is OK too.  But you are
> missing the 
> v4l/dvb tuner module that the pvrusb2 driver requires in
> order to 
> operate the RF tuner in the device.  Without that you
> won't be able to 
> stream anything from the F-connector input (television,
> dtv).  I expect 
> however that the composite and s-video inputs probably
> still work fine.  
> If you can confirm that, say, composite input works, then
> you've 
> successfully verified all of the hardware except the RF
> tuner.  And I 
> think your problem is in fact the RF tuner, due to the
> missing module.

This may not be necessary, I'll let you know.

> 
>   -Mike
> 
>