[mythtv-users] WinTV-NOVA-TD-500 issues.

Sat May 12 23:16:39 UTC 2012

On Sat, 12 May 2012 22:01:42 +0100, Alan Chandler  
<alan at chandlerfamily.org.uk> wrote:

> I have long had a WinTV-NOVA-TD-500 operating in my Debian Stable box  
> running mythtv backend.
>
> Every so often it would lock up such that the second tuner would no  
> longer by usable by mythtv. I have just recently moved from precompiled  
> 0.24 mythtv to 0.25 which I have installed and I have failed to even  
> record the first program it scheduled in tuner 2.  This might be  
> co-incidence, but I rebooted only a couple of days ago to clear the  
> hardware.
>
> During boot, dmesg messages can be seen loading the firmware
>
> [    6.434100] Intel ICH 0000:00:10.2: setting latency timer to 64
> [    6.463257] dib0700: loaded with support for 13 different device-types
> [    6.463542] dvb-usb: found a 'Hauppauge Nova-TD-500 (84xxx)' in cold  
> state, will try to load a firmware
> [    6.463591] usb 2-1: firmware: requesting dvb-usb-dib0700-1.20.fw
> [    6.491991] dvb-usb: downloading firmware from file  
> 'dvb-usb-dib0700-1.20.fw'
> [    6.700016] dib0700: firmware started successfully.
> [    6.756033] intel8x0_measure_ac97_clock: measured 54542 usecs (2680  
> samples)
> [    6.756072] intel8x0: clocking to 46890
> [    7.204036] dvb-usb: found a 'Hauppauge Nova-TD-500 (84xxx)' in warm  
> state.
> [    7.204149] dvb-usb: will pass the complete MPEG2 transport stream to  
> the software demuxer.
> [    7.204709] DVB: registering new adapter (Hauppauge Nova-TD-500  
> (84xxx))
> [    7.432408] DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
> [    7.646950] DiB0070: successfully identified
> [    7.646993] dvb-usb: will pass the complete MPEG2 transport stream to  
> the software demuxer.
> [    7.647425] DVB: registering new adapter (Hauppauge Nova-TD-500  
> (84xxx))
> [    7.796371] DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)...
> [    8.015168] DiB0070: successfully identified
> [    8.015210] dvb-usb: Hauppauge Nova-TD-500 (84xxx) successfully  
> initialized and connected.
> [    8.015451] usbcore: registered new interface driver dvb_usb_dib0700
>
>
> Is this the latest release for this device? is there perhaps something I  
> can do to load a later release?
>
> The only indication in the log I can find that shows there might be a  
> problem is (grep'ing for DiB0070)
>
> syslog:May 12 19:34:26 owl kernel: [167590.813589] DiB0070 I2C read  
> failed
>
> syslog.1:May 12 02:43:44 owl kernel: [106947.993648] DiB0070 I2C read  
> failed
> syslog.1:May 12 04:48:09 owl kernel: [114413.241579] DiB0070 I2C read  
> failed
>
> Strangely, the first item is 14 minutes after I think the backend  
> started trying to record a program - this is the mythbackend log for  
> about that time (I already included some of this in the previous mail  
> about the database failure).
>
> 2012-05-12 19:18:41.203334 I [26047/26070] HouseKeeping  
> housekeeper.cpp:225 (RunHouseKeeping) - Running housekeeping thread
> 2012-05-12 19:19:29.555847 I [26047/26064] TVRecEvent tv_rec.cpp:1518  
> (HandlePendingRecordings) - TVRec(21): ASK_RECORDING 21 29 0 0
> 2012-05-12 19:19:29.564286 I [26047/26068] TVRecEvent tv_rec.cpp:1518  
> (HandlePendingRecordings) - TVRec(24): ASK_RECORDING 24 29 0 0
> 2012-05-12 19:19:29.899042 I [26047/26067] TVRecEvent tv_rec.cpp:1518  
> (HandlePendingRecordings) - TVRec(23): ASK_RECORDING 23 29 0 0
> 2012-05-12 19:19:29.899175 I [26047/26066] TVRecEvent tv_rec.cpp:1518  
> (HandlePendingRecordings) - TVRec(22): ASK_RECORDING 22 29 0 0
> 2012-05-12 19:19:59.759659 I [26047/26064] TVRecEvent tv_rec.cpp:1014  
> (HandleStateChange) - TVRec(21): Changing from None to RecordingOnly
> 2012-05-12 19:19:59.760574 I [26047/26064] TVRecEvent tv_rec.cpp:3456  
> (TuningCheckForHWChange) - TVRec(21): HW Tuner: 21->21
> 2012-05-12 19:20:06.344388 N [26047/26069] Scheduler autoexpire.cpp:263  
> (CalcParams) - AutoExpire: CalcParams(): Max required Free Space: 3.0 GB  
> w/freq: 7 min
> 2012-05-12 19:20:06.344451 I [26047/26069] Scheduler scheduler.cpp:2460  
> (HandleRecordingStatusChange) - Tuning recording: "Britain's Got  
> Talent":"The Final": channel 1003 on ca
> rdid 21, sourceid 1
> 2012-05-12 19:20:36.633274 E [26047/26058] EIT mythdb.cpp:192 (DBError)  
> - DB Error (change_program):
> Query was:
> UPDATE program SET starttime = ?,     endtime   = ? WHERE chanid    = ?  
> AND       starttime = ?
> Bindings were:
> :CHANID=1081, :NEWEND=2012-05-14T13:40:00, :NEWSTART=2012-05-14T13:00:00,
> :OLDSTART=2012-05-14T12:00:00
> Driver error was [2/1062]:
> QMYSQL3: Unable to execute statement
> Database error was:
> Duplicate entry '1081-2012-05-14 13:00:00-0' for key 'PRIMARY'
>
> 2012-05-12 19:21:56.285571 I [26047/26069] Scheduler scheduler.cpp:2011  
> (HandleReschedule) - Reschedule requested for id -1.
> 2012-05-12 19:21:56.823969 I [26047/26069] Scheduler scheduler.cpp:2069  
> (HandleReschedule) - Scheduled 141 items in 0.5 = 0.28 match + 0.25 place
> 2012-05-12 19:23:41.205408 I [26047/26070] HouseKeeping  
> housekeeper.cpp:225 (RunHouseKeeping) - Running housekeeping thread
> 2012-05-12 19:26:06.365838 I [26047/26069] Scheduler scheduler.cpp:2011  
> (HandleReschedule) - Reschedule requested for id -1.
> 2012-05-12 19:26:06.856468 I [26047/26069] Scheduler scheduler.cpp:2069  
> (HandleReschedule) - Scheduled 141 items in 0.5 = 0.28 match + 0.21 place
> 2012-05-12 19:28:48.208039 I [26047/26070] HouseKeeping  
> housekeeper.cpp:225 (RunHouseKeeping) - Running housekeeping thread
> 2012-05-12 19:30:33.348850 N [26047/26071] Expire autoexpire.cpp:263  
> (CalcParams) - AutoExpire: CalcParams(): Max required Free Space: 3.0 GB  
> w/freq: 7 min
> 2012-05-12 19:32:50.232700 I [26047/26069] Scheduler scheduler.cpp:2011  
> (HandleReschedule) - Reschedule requested for id -1.
> 2012-05-12 19:32:50.724655 I [26047/26069] Scheduler scheduler.cpp:2069  
> (HandleReschedule) - Scheduled 141 items in 0.5 = 0.27 match + 0.22 place
> 2012-05-12 19:33:48.210176 I [26047/26070] HouseKeeping  
> housekeeper.cpp:225 (RunHouseKeeping) - Running housekeeping thread
> 2012-05-12 19:36:08.752090 I [26047/26069] Scheduler scheduler.cpp:2011  
> (HandleReschedule) - Reschedule requested for id -1.
> 2012-05-12 19:36:09.364021 I [26047/26069] Scheduler scheduler.cpp:2069  
> (HandleReschedule) - Scheduled 141 items in 0.6 = 0.28 match + 0.33 place
> 2012-05-12 19:38:33.352323 N [26047/26071] Expire autoexpire.cpp:263  
> (CalcParams) - AutoExpire: CalcParams(): Max required Free Space: 3.0 GB  
> w/freq: 7 min
> 2012-05-12 19:38:53.212302 I [26047/26070] HouseKeeping  
> housekeeper.cpp:225 (RunHouseKeeping) - Running housekeeping thread
>
>
> Also Is it possible to force the hardware to try and reset itself  
> without rebooting?  If so maybe I could right a script to reset it  
> frequently.
>

I use a Nova TD 500 and have also experienced tuner lock-ups. Interesting  
that you finger tuner 2 - I've never noted which one fails.

It's early days but 0.25 appears to be a lot better than 0.24 for me. The  
only aborted recording I currently have shows the "I2C" error 2 mins after  
the scheduled start time. I haven't come across any other error to  
indicate tuner failure.

1.20 is the latest firmware. I believe the firmware is only loaded on cold  
start (ie. not a restart) so I don't see how a script could achieve that.

Are you sure it is a hardware issue ? I find that restarting the backend  
always clears the problem. However I do use MythWelcome/ACPI Wakeup so my  
system cold starts frequently.