I let it rest unplugged for 12 hours or so, redownloaded the firmware, and the only change is now it records black with static for audio.
Also, when I look into the /sys/ interface the only thing that looks strange to me is that ctl_channel/cur_val is "0" and echoing to it doesn't change it. (Shouldn't it?) Any suggestions? --- On Tue, 9/15/09, Nicholas Robbins <[email protected]> wrote: > From: Nicholas Robbins <[email protected]> > Subject: [pvrusb2] HVR-1950 stopped working. > To: [email protected] > Date: Tuesday, September 15, 2009, 10:05 AM > 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.) > > 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 > 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. > 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. > > 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. > > I unplugged the device and I'm giving it a vacation for the > day. Any thoughts about what might be going wrong? > > -Nick > > > > > _______________________________________________ > pvrusb2 mailing list > [email protected] > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 > _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
