Mailing List Archive

HDPVR intermittent failure
Hi all. Hope you are surviving the apocalypse OK.

I have a HDPVR as one of my recorders. Recently, and with increasing
frequency, recordings on it fail. This is not the normal issue with the
wall-wart failing as I am powering it from USB these days (thanks to the
helpful advice of some people on this list).

Rebooting the system fixes the problem and the HDPVR records like a champ
for a x days, then develops the same problem and needs a reboot. As noted,
the mean of x seems to be decreasing.

An example log entry from when this happens is below. Any advice on how to
troubleshoot this?

May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: E Scheduler
recordingprofile.cpp:162 (addSelection) SampleRate: Attempted to add a rate
32000 Hz, which is not in the x
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I TVRecEvent
tv_rec.cpp:1073 (HandleStateChange) TVRec[1]: Changing from None to
RecordingOnly x
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I TVRecEvent
mythdbcon.cpp:422 (PurgeIdleConnections) New DB connection, total: 11
x
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I TVRecEvent
tv_rec.cpp:3563 (TuningCheckForHWChange) TVRec[1]: HW Tuner: 1->1
x
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I TVRecEvent
tv_rec.cpp:3685 (TuningFrequency) TVRec[1]: TuningFrequency
x
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: C
CoreContext programinfo.cpp:351 (ProgramInfo) ProgramInfo(): Failed to find
recorded entry for 0. x
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
scheduler.cpp:2819 (HandleRecordingStatusChange) Tuning recording: "PBS
NewsHour Weekend": channel 2008 onx
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
scheduler.cpp:2267 (HandleReschedule) Reschedule requested for PLACE
PrepareToRecord x
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
scheduler.cpp:2380 (HandleReschedule) Scheduled 176 items in 0.1 = 0.00
match + 0.00 check + 0.06 place x
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: E
ProcessRequest programinfo.cpp:2594 (GetPlaybackURL)
ProgramInfo(2008_20200511003000.ts): GetPlaybackURL: '2008_2020x
May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: E
ProcessRequest programinfo.cpp:2594 (GetPlaybackURL)
ProgramInfo(2008_20200511003000.ts): GetPlaybackURL: '2008_2020x
May 10 17:30:05 steve-EP45-UD3P mythbackend: mythbackend[889]: N Update
autoexpire.cpp:264 (CalcParams) AutoExpire: CalcParams(): Max required Free
Space: 3.0 GB w/freq: 15 min x
May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: W TVRecEvent
tv_rec.cpp:4004 (TuningSignalCheck) TVRec[1]: TuningSignalCheck: taking
more than 15000 ms to get a lock.x
May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: W TVRecEvent
tv_rec.cpp:4006 (TuningSignalCheck) TVRec[1]: See 'Tuning timeout' in
mythtv-setup for this input x
May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: I
CoreContext scheduler.cpp:725 (UpdateRecStatus) Updating status for "PBS
NewsHour Weekend" on cardid 1 (Tuning => Fax
May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
scheduler.cpp:2267 (HandleReschedule) Reschedule requested for CHECK -14
208 0 UpdateRecStatus2 | PBS Newsx
May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
scheduler.cpp:2380 (HandleReschedule) Scheduled 176 items in 0.1 = 0.00
match + 0.00 check + 0.06 place x
May 10 17:33:36 steve-EP45-UD3P mythbackend: mythbackend[889]: N Expire
autoexpire.cpp:264 (CalcParams) AutoExpire: CalcParams(): Max required Free
Space: 3.0 GB w/freq: 15 min x
May 10 17:37:32 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
May 10 17:37:32 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
May 10 17:37:36 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
May 10 17:37:36 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
May 10 17:37:39 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
May 10 17:37:39 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
May 10 17:37:45 steve-EP45-UD3P mythbackend: mythbackend[889]: E
ProcessRequest programinfo.cpp:2594 (GetPlaybackURL)
ProgramInfo(2008_20200511003000.ts): GetPlaybackURL: '2008_2020x
May 10 17:37:46 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
PlaybackBoxHelper: CHECK_AVAILABILITY 'myth:/x
May 10 17:37:46 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: I
PreviewGenerator mythcorecontext.cpp:1343 (SendReceiveStringList)
MythCoreContext::SendReceiveStringList(): x
May 10 17:37:46 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
PreviewGenerator previewgenerator.cpp:387 (RemotePreviewRun) Preview:
Remote Preview failed due to communicax
Re: HDPVR intermittent failure [ In reply to ]
On 5/10/20 10:37 PM, DryHeat122 . wrote:
> Hi all.  Hope you are surviving the apocalypse OK.
>
> I have a HDPVR as one of my recorders.  Recently, and with increasing
> frequency, recordings on it fail.  This is not the normal issue with
> the wall-wart failing as I am powering it from USB these days (thanks
> to the helpful advice of some people on this list).
>
> Rebooting the system fixes the problem and the HDPVR records like a
> champ for a x days, then develops the same problem and needs a
> reboot.  As noted, the mean of x seems to be decreasing.
>
> An example log entry from when this happens is below.  Any advice on
> how to troubleshoot this?
>
> May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: E
> Scheduler recordingprofile.cpp:162 (addSelection) SampleRate:
> Attempted to add a rate 32000 Hz, which is not in the x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> TVRecEvent tv_rec.cpp:1073 (HandleStateChange) TVRec[1]: Changing from
> None to RecordingOnly                        x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> TVRecEvent mythdbcon.cpp:422 (PurgeIdleConnections) New DB connection,
> total: 11                            x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> TVRecEvent tv_rec.cpp:3563 (TuningCheckForHWChange) TVRec[1]: HW
> Tuner: 1->1                                x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[1]: TuningFrequency
>                              x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: C
> CoreContext programinfo.cpp:351 (ProgramInfo) ProgramInfo(): Failed to
> find recorded entry for 0.                   x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> Scheduler scheduler.cpp:2819 (HandleRecordingStatusChange) Tuning
> recording: "PBS NewsHour Weekend": channel 2008 onx
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> Scheduler scheduler.cpp:2267 (HandleReschedule) Reschedule requested
> for PLACE PrepareToRecord                      x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> Scheduler scheduler.cpp:2380 (HandleReschedule) Scheduled 176 items in
> 0.1 = 0.00 match + 0.00 check + 0.06 place   x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: E
> ProcessRequest programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL: '2008_2020x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: E
> ProcessRequest programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL: '2008_2020x
> May 10 17:30:05 steve-EP45-UD3P mythbackend: mythbackend[889]: N
> Update autoexpire.cpp:264 (CalcParams) AutoExpire: CalcParams(): Max
> required Free Space: 3.0 GB w/freq: 15 min     x
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: W
> TVRecEvent tv_rec.cpp:4004 (TuningSignalCheck) TVRec[1]:
> TuningSignalCheck: taking more than 15000 ms to get a lock.x
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: W
> TVRecEvent tv_rec.cpp:4006 (TuningSignalCheck) TVRec[1]: See 'Tuning
> timeout' in mythtv-setup for this input        x
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> CoreContext scheduler.cpp:725 (UpdateRecStatus) Updating status for
> "PBS NewsHour Weekend" on cardid 1 (Tuning => Fax
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> Scheduler scheduler.cpp:2267 (HandleReschedule) Reschedule requested
> for CHECK -14 208 0 UpdateRecStatus2 | PBS Newsx
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> Scheduler scheduler.cpp:2380 (HandleReschedule) Scheduled 176 items in
> 0.1 = 0.00 match + 0.00 check + 0.06 place   x
> May 10 17:33:36 steve-EP45-UD3P mythbackend: mythbackend[889]: N
> Expire autoexpire.cpp:264 (CalcParams) AutoExpire: CalcParams(): Max
> required Free Space: 3.0 GB w/freq: 15 min     x
> May 10 17:37:32 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:37:32 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:37:36 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:37:36 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:37:39 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:37:39 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:37:45 steve-EP45-UD3P mythbackend: mythbackend[889]: E
> ProcessRequest programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL: '2008_2020x
> May 10 17:37:46 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'myth:/x
> May 10 17:37:46 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> I PreviewGenerator mythcorecontext.cpp:1343 (SendReceiveStringList)
> MythCoreContext::SendReceiveStringList(): x
> May 10 17:37:46 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]:
> E PreviewGenerator previewgenerator.cpp:387 (RemotePreviewRun)
> Preview: Remote Preview failed due to communicax
>
I looked up the amperage of a usb port and from what I see they only
provide 0.5 amps. The original HDPVR needed I think, 2.0 amps.. I really
think you should look there first. I put a moldex connector in my PC,
and run it off the main power supply.
https://www.mythtv.org/wiki/Mounting_the_HD-PVR_Internally I've run it
like this for well over 10 years..


> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
Re: HDPVR intermittent failure [ In reply to ]
On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com> wrote:

>
> On 5/10/20 10:37 PM, DryHeat122 . wrote:
>
> Hi all. Hope you are surviving the apocalypse OK.
>
> I have a HDPVR as one of my recorders. Recently, and with increasing
> frequency, recordings on it fail. This is not the normal issue with the
> wall-wart failing as I am powering it from USB these days (thanks to the
> helpful advice of some people on this list).
>
> Rebooting the system fixes the problem and the HDPVR records like a champ
> for a x days, then develops the same problem and needs a reboot. As noted,
> the mean of x seems to be decreasing.
>
> An example log entry from when this happens is below. Any advice on how
> to troubleshoot this?
>
> May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:30:00 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: E Scheduler
> recordingprofile.cpp:162 (addSelection) SampleRate: Attempted to add a rate
> 32000 Hz, which is not in the x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> TVRecEvent tv_rec.cpp:1073 (HandleStateChange) TVRec[1]: Changing from None
> to RecordingOnly x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> TVRecEvent mythdbcon.cpp:422 (PurgeIdleConnections) New DB connection,
> total: 11 x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> TVRecEvent tv_rec.cpp:3563 (TuningCheckForHWChange) TVRec[1]: HW Tuner:
> 1->1 x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> TVRecEvent tv_rec.cpp:3685 (TuningFrequency) TVRec[1]: TuningFrequency
> x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: C
> CoreContext programinfo.cpp:351 (ProgramInfo) ProgramInfo(): Failed to find
> recorded entry for 0. x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
> scheduler.cpp:2819 (HandleRecordingStatusChange) Tuning recording: "PBS
> NewsHour Weekend": channel 2008 onx
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
> scheduler.cpp:2267 (HandleReschedule) Reschedule requested for PLACE
> PrepareToRecord x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
> scheduler.cpp:2380 (HandleReschedule) Scheduled 176 items in 0.1 = 0.00
> match + 0.00 check + 0.06 place x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: E
> ProcessRequest programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL: '2008_2020x
> May 10 17:30:00 steve-EP45-UD3P mythbackend: mythbackend[889]: E
> ProcessRequest programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL: '2008_2020x
> May 10 17:30:05 steve-EP45-UD3P mythbackend: mythbackend[889]: N Update
> autoexpire.cpp:264 (CalcParams) AutoExpire: CalcParams(): Max required Free
> Space: 3.0 GB w/freq: 15 min x
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: W
> TVRecEvent tv_rec.cpp:4004 (TuningSignalCheck) TVRec[1]: TuningSignalCheck:
> taking more than 15000 ms to get a lock.x
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: W
> TVRecEvent tv_rec.cpp:4006 (TuningSignalCheck) TVRec[1]: See 'Tuning
> timeout' in mythtv-setup for this input x
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: I
> CoreContext scheduler.cpp:725 (UpdateRecStatus) Updating status for "PBS
> NewsHour Weekend" on cardid 1 (Tuning => Fax
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
> scheduler.cpp:2267 (HandleReschedule) Reschedule requested for CHECK -14
> 208 0 UpdateRecStatus2 | PBS Newsx
> May 10 17:30:15 steve-EP45-UD3P mythbackend: mythbackend[889]: I Scheduler
> scheduler.cpp:2380 (HandleReschedule) Scheduled 176 items in 0.1 = 0.00
> match + 0.00 check + 0.06 place x
> May 10 17:33:36 steve-EP45-UD3P mythbackend: mythbackend[889]: N Expire
> autoexpire.cpp:264 (CalcParams) AutoExpire: CalcParams(): Max required Free
> Space: 3.0 GB w/freq: 15 min x
> May 10 17:37:32 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:37:32 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:37:36 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:37:36 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:37:39 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL:x
> May 10 17:37:39 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'GetPlax
> May 10 17:37:45 steve-EP45-UD3P mythbackend: mythbackend[889]: E
> ProcessRequest programinfo.cpp:2594 (GetPlaybackURL)
> ProgramInfo(2008_20200511003000.ts): GetPlaybackURL: '2008_2020x
> May 10 17:37:46 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PlaybackBoxHelper playbackboxhelper.cpp:88 (CheckAvailability)
> PlaybackBoxHelper: CHECK_AVAILABILITY 'myth:/x
> May 10 17:37:46 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: I
> PreviewGenerator mythcorecontext.cpp:1343 (SendReceiveStringList)
> MythCoreContext::SendReceiveStringList(): x
> May 10 17:37:46 steve-EP45-UD3P mythfrontend.real: mythfrontend[2065]: E
> PreviewGenerator previewgenerator.cpp:387 (RemotePreviewRun) Preview:
> Remote Preview failed due to communicax
>
> I looked up the amperage of a usb port and from what I see they only
> provide 0.5 amps. The original HDPVR needed I think, 2.0 amps.. I really
> think you should look there first. I put a moldex connector in my PC, and
> run it off the main power supply.
> https://www.mythtv.org/wiki/Mounting_the_HD-PVR_Internally I've run it
> like this for well over 10 years..
>
>
> _______________________________________________
> mythtv-users mailing listmythtv-users@mythtv.orghttp://lists.mythtv.org/mailman/listinfo/mythtv-usershttp://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.or <https://forum.mythtv.org>
>
>
>
Ok thanks I will investigate that. But it's been working fine with the
current power source for like a year now, and others on this list use it
too. Is there anything else it could be?
Re: HDPVR intermittent failure [ In reply to ]
On Sun, 10 May 2020 20:20:30 -0700, you wrote:

>On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com> wrote:

>Ok thanks I will investigate that. But it's been working fine with the
>current power source for like a year now, and others on this list use it
>too.

USB cables often fit badly into the sockets. If so, the connection
generally gets worse over time as you get dirt or oxidisation on the
contacts. So badly fitting cables will degrade with time. The result
is that the voltage drop across the cable will increase markedly. And
they can be too thin - the amount of copper in the wires is too little
and that causes high resistance and a big voltage drop across the
length of the cable. Some (most?) USB cables are designed only for
data transmission, or to run very low power devices. For a high power
device, you need a better (thicker) cable. The high power devices do
a negotiation with device supplying the power and request high power
mode. If the cable is not capable of high power, that negotiation is
not supposed to work and the device should either only work in low
power mode or it should turn itself off. But USB cable makers often
make cables not capable of high power transmission that will allow the
high power mode negotiation to succeed. So even though the device
supplying the power is sending high current, the voltage drop in the
cable means that at the other end, the voltage can be below the level
required for proper operation or to fully charge the device's battery.

I have had two notably bad experiences with USB cables. One was a USB
DVB-T tuner, and it was very like your experience - it would go for a
number of days just fine, then suddenly stop. If I unplugged it and
plugged it in again, it would usually work again. When I finally
investigated properly, I found the cable was just a little loose in
the PC's socket. I replaced the cable with one that fit more tightly
and the tuner was much more reliable. It still occasionally caused
trouble, but only when I had bumped the cables (or in one case, after
we had a small earthquake). So because of that and because I needed
more DVB-T tuners, I finally replaced all my DVB-T tuners with an 8
tuner PCIe card.

The second bad experience was my Samsung Galaxy Tab S2 tablet. Its
USB charging cable was supplied with it by Samsung, so I assumed it
was a good one. But right from the start, the tablet took a long time
to charge, and the time gradually got longer and longer and the
battery life on one charge was getting less and less. And then I
started to have to jiggle the cable in the socket to get it to charge
at all. I actually called the Samsung help line about this, and they
said it sounds like a bad cable. So I bought a expensive (NZ$30)
Pudney & Lee charging cable, which was a fair bit longer than the old
Samsung cable, but fit very tightly at both ends and was significantly
thicker - it has more copper in the wires in the cable. Then suddenly
the battery charging times were what was specified for the tablet,
rather than three times as long. And over a number of charging
cycles, the battery life came back again. So the original Samsung
supplied cable was clearly bad from the start - it is probably less
than the specification required to charge the tablet properly as it is
too thin and has too much voltage drop even when the plugs fit
properly. So definitely NZ$30 well spent. But I am surprised that a
reputable company like Samsung would supply a bad cable with an
expensive top-of-the-line product like my tablet. But they did - so
now I always suspect any USB cable I get and keep an eye on how well
it is working.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: HDPVR intermittent failure [ In reply to ]
On Mon, May 11, 2020 at 2:41 AM Stephen Worthington <
stephen_agent@jsw.gen.nz> wrote:

> On Sun, 10 May 2020 20:20:30 -0700, you wrote:
>
> >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com> wrote:
>
> >Ok thanks I will investigate that. But it's been working fine with the
> >current power source for like a year now, and others on this list use it
> >too.
>
> USB cables often fit badly into the sockets. If so, the connection
> generally gets worse over time as you get dirt or oxidisation on the
> contacts. So badly fitting cables will degrade with time. The result
> is that the voltage drop across the cable will increase markedly. And
> they can be too thin - the amount of copper in the wires is too little
> and that causes high resistance and a big voltage drop across the
> length of the cable. Some (most?) USB cables are designed only for
> data transmission, or to run very low power devices. For a high power
> device, you need a better (thicker) cable. The high power devices do
> a negotiation with device supplying the power and request high power
> mode. If the cable is not capable of high power, that negotiation is
> not supposed to work and the device should either only work in low
> power mode or it should turn itself off. But USB cable makers often
> make cables not capable of high power transmission that will allow the
> high power mode negotiation to succeed. So even though the device
> supplying the power is sending high current, the voltage drop in the
> cable means that at the other end, the voltage can be below the level
> required for proper operation or to fully charge the device's battery.
>
> I have had two notably bad experiences with USB cables. One was a USB
> DVB-T tuner, and it was very like your experience - it would go for a
> number of days just fine, then suddenly stop. If I unplugged it and
> plugged it in again, it would usually work again. When I finally
> investigated properly, I found the cable was just a little loose in
> the PC's socket. I replaced the cable with one that fit more tightly
> and the tuner was much more reliable. It still occasionally caused
> trouble, but only when I had bumped the cables (or in one case, after
> we had a small earthquake). So because of that and because I needed
> more DVB-T tuners, I finally replaced all my DVB-T tuners with an 8
> tuner PCIe card.
>
> The second bad experience was my Samsung Galaxy Tab S2 tablet. Its
> USB charging cable was supplied with it by Samsung, so I assumed it
> was a good one. But right from the start, the tablet took a long time
> to charge, and the time gradually got longer and longer and the
> battery life on one charge was getting less and less. And then I
> started to have to jiggle the cable in the socket to get it to charge
> at all. I actually called the Samsung help line about this, and they
> said it sounds like a bad cable. So I bought a expensive (NZ$30)
> Pudney & Lee charging cable, which was a fair bit longer than the old
> Samsung cable, but fit very tightly at both ends and was significantly
> thicker - it has more copper in the wires in the cable. Then suddenly
> the battery charging times were what was specified for the tablet,
> rather than three times as long. And over a number of charging
> cycles, the battery life came back again. So the original Samsung
> supplied cable was clearly bad from the start - it is probably less
> than the specification required to charge the tablet properly as it is
> too thin and has too much voltage drop even when the plugs fit
> properly. So definitely NZ$30 well spent. But I am surprised that a
> reputable company like Samsung would supply a bad cable with an
> expensive top-of-the-line product like my tablet. But they did - so
> now I always suspect any USB cable I get and keep an eye on how well
> it is working.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


Thanks for all the suggestions. I will investigate all of them. Something
I do not see in here is an opinion that some software problem could have
evolved. I was kind of thinking of that as a possibility given that it
worked fine for so long then seems to be degrading. OTOH I never thought
of the possibility that the USB connection could be degrading. I'm going
to try Greg's connector, assuming I can get parts during the Apocalypse.
Also, his link specifies Radio Shack parts. What's Radio Shack?!? ;-)
Re: HDPVR intermittent failure [ In reply to ]
On Mon, May 11, 2020 at 12:59 PM DryHeat122 . <dryheat122@gmail.com> wrote:

> On Mon, May 11, 2020 at 2:41 AM Stephen Worthington <
> stephen_agent@jsw.gen.nz> wrote:
>
>> On Sun, 10 May 2020 20:20:30 -0700, you wrote:
>>
>> >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com> wrote:
>>
>> >Ok thanks I will investigate that. But it's been working fine with the
>> >current power source for like a year now, and others on this list use it
>> >too.
>>
>> USB cables often fit badly into the sockets. If so, the connection
>> generally gets worse over time as you get dirt or oxidisation on the
>> contacts. So badly fitting cables will degrade with time. The result
>> is that the voltage drop across the cable will increase markedly. And
>> they can be too thin - the amount of copper in the wires is too little
>> and that causes high resistance and a big voltage drop across the
>> length of the cable. Some (most?) USB cables are designed only for
>> data transmission, or to run very low power devices. For a high power
>> device, you need a better (thicker) cable. The high power devices do
>> a negotiation with device supplying the power and request high power
>> mode. If the cable is not capable of high power, that negotiation is
>> not supposed to work and the device should either only work in low
>> power mode or it should turn itself off. But USB cable makers often
>> make cables not capable of high power transmission that will allow the
>> high power mode negotiation to succeed. So even though the device
>> supplying the power is sending high current, the voltage drop in the
>> cable means that at the other end, the voltage can be below the level
>> required for proper operation or to fully charge the device's battery.
>>
>> I have had two notably bad experiences with USB cables. One was a USB
>> DVB-T tuner, and it was very like your experience - it would go for a
>> number of days just fine, then suddenly stop. If I unplugged it and
>> plugged it in again, it would usually work again. When I finally
>> investigated properly, I found the cable was just a little loose in
>> the PC's socket. I replaced the cable with one that fit more tightly
>> and the tuner was much more reliable. It still occasionally caused
>> trouble, but only when I had bumped the cables (or in one case, after
>> we had a small earthquake). So because of that and because I needed
>> more DVB-T tuners, I finally replaced all my DVB-T tuners with an 8
>> tuner PCIe card.
>>
>> The second bad experience was my Samsung Galaxy Tab S2 tablet. Its
>> USB charging cable was supplied with it by Samsung, so I assumed it
>> was a good one. But right from the start, the tablet took a long time
>> to charge, and the time gradually got longer and longer and the
>> battery life on one charge was getting less and less. And then I
>> started to have to jiggle the cable in the socket to get it to charge
>> at all. I actually called the Samsung help line about this, and they
>> said it sounds like a bad cable. So I bought a expensive (NZ$30)
>> Pudney & Lee charging cable, which was a fair bit longer than the old
>> Samsung cable, but fit very tightly at both ends and was significantly
>> thicker - it has more copper in the wires in the cable. Then suddenly
>> the battery charging times were what was specified for the tablet,
>> rather than three times as long. And over a number of charging
>> cycles, the battery life came back again. So the original Samsung
>> supplied cable was clearly bad from the start - it is probably less
>> than the specification required to charge the tablet properly as it is
>> too thin and has too much voltage drop even when the plugs fit
>> properly. So definitely NZ$30 well spent. But I am surprised that a
>> reputable company like Samsung would supply a bad cable with an
>> expensive top-of-the-line product like my tablet. But they did - so
>> now I always suspect any USB cable I get and keep an eye on how well
>> it is working.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users@mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
>
> Thanks for all the suggestions. I will investigate all of them.
> Something I do not see in here is an opinion that some software problem
> could have evolved. I was kind of thinking of that as a possibility given
> that it worked fine for so long then seems to be degrading. OTOH I never
> thought of the possibility that the USB connection could be degrading. I'm
> going to try Greg's connector, assuming I can get parts during the
> Apocalypse. Also, his link specifies Radio Shack parts. What's Radio
> Shack?!? ;-)
>

Well folks this is getting frustrating. I addressed a possible ventilation
issue. I also unplugged the power cord I had from the Myth box USB and
connected it to an old iPad charger rated at 5V/2A. No help. It wouldn't
record anything, no matter how much rebooting and power-cycling. So I
concluded the HDPVR was hosed and got a new one (more accurately, a
replacement circuit board for it). Powered it with the same wall wart.
Recorded great for a day. Just turned it on and I have failed recordings
and it won't respond when I try to manually play a channel. Reboot, and it
works fine, same pattern as before.

I finally got a molex connector and am still going to try what Greg
suggested, but I really don't think it's a power issue. Apply makes good
electronics and that wart has the same specs as the power supply that comes
with the HDPVR. The HDPCR isn't overheating. It's not the HDPVR itself.
That only leaves the software on the myth box. Anyone have ideas how to
troubleshoot that?
Re: HDPVR intermittent failure [ In reply to ]
On Sat, 2020-06-27 at 18:46 -0700, DryHeat122 . wrote:
> On Mon, May 11, 2020 at 12:59 PM DryHeat122 . <dryheat122@gmail.com>
> wrote:
> > On Mon, May 11, 2020 at 2:41 AM Stephen Worthington <
> > stephen_agent@jsw.gen.nz> wrote:
> > > On Sun, 10 May 2020 20:20:30 -0700, you wrote:
> > >
> > >
> > >
> > > >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com> wrote:
> > >
> > >
> > >
> > > >Ok thanks I will investigate that. But it's been working fine
> > > with the
> > >
> > > >current power source for like a year now, and others on this
> > > list use it
> > >
> > > >too.
> > >
> > >
> > >
> > > USB cables often fit badly into the sockets. If so, the
> > > connection
> > >
> > > generally gets worse over time as you get dirt or oxidisation on
> > > the
> > >
> > > contacts. So badly fitting cables will degrade with time. The
> > > result
> > >
> > > is that the voltage drop across the cable will increase
> > > markedly. And
> > >
> > > they can be too thin - the amount of copper in the wires is too
> > > little
> > >
> > > and that causes high resistance and a big voltage drop across the
> > >
> > > length of the cable. Some (most?) USB cables are designed only
> > > for
> > >
> > > data transmission, or to run very low power devices. For a high
> > > power
> > >
> > > device, you need a better (thicker) cable. The high power
> > > devices do
> > >
> > > a negotiation with device supplying the power and request high
> > > power
> > >
> > > mode. If the cable is not capable of high power, that
> > > negotiation is
> > >
> > > not supposed to work and the device should either only work in
> > > low
> > >
> > > power mode or it should turn itself off. But USB cable makers
> > > often
> > >
> > > make cables not capable of high power transmission that will
> > > allow the
> > >
> > > high power mode negotiation to succeed. So even though the
> > > device
> > >
> > > supplying the power is sending high current, the voltage drop in
> > > the
> > >
> > > cable means that at the other end, the voltage can be below the
> > > level
> > >
> > > required for proper operation or to fully charge the device's
> > > battery.
> > >
> > >
> > >
> > > I have had two notably bad experiences with USB cables. One was
> > > a USB
> > >
> > > DVB-T tuner, and it was very like your experience - it would go
> > > for a
> > >
> > > number of days just fine, then suddenly stop. If I unplugged it
> > > and
> > >
> > > plugged it in again, it would usually work again. When I finally
> > >
> > > investigated properly, I found the cable was just a little loose
> > > in
> > >
> > > the PC's socket. I replaced the cable with one that fit more
> > > tightly
> > >
> > > and the tuner was much more reliable. It still occasionally
> > > caused
> > >
> > > trouble, but only when I had bumped the cables (or in one case,
> > > after
> > >
> > > we had a small earthquake). So because of that and because I
> > > needed
> > >
> > > more DVB-T tuners, I finally replaced all my DVB-T tuners with an
> > > 8
> > >
> > > tuner PCIe card.
> > >
> > >
> > >
> > > The second bad experience was my Samsung Galaxy Tab S2 tablet.
> > > Its
> > >
> > > USB charging cable was supplied with it by Samsung, so I assumed
> > > it
> > >
> > > was a good one. But right from the start, the tablet took a long
> > > time
> > >
> > > to charge, and the time gradually got longer and longer and the
> > >
> > > battery life on one charge was getting less and less. And then I
> > >
> > > started to have to jiggle the cable in the socket to get it to
> > > charge
> > >
> > > at all. I actually called the Samsung help line about this, and
> > > they
> > >
> > > said it sounds like a bad cable. So I bought a expensive (NZ$30)
> > >
> > > Pudney & Lee charging cable, which was a fair bit longer than the
> > > old
> > >
> > > Samsung cable, but fit very tightly at both ends and was
> > > significantly
> > >
> > > thicker - it has more copper in the wires in the cable. Then
> > > suddenly
> > >
> > > the battery charging times were what was specified for the
> > > tablet,
> > >
> > > rather than three times as long. And over a number of charging
> > >
> > > cycles, the battery life came back again. So the original
> > > Samsung
> > >
> > > supplied cable was clearly bad from the start - it is probably
> > > less
> > >
> > > than the specification required to charge the tablet properly as
> > > it is
> > >
> > > too thin and has too much voltage drop even when the plugs fit
> > >
> > > properly. So definitely NZ$30 well spent. But I am surprised
> > > that a
> > >
> > > reputable company like Samsung would supply a bad cable with an
> > >
> > > expensive top-of-the-line product like my tablet. But they did -
> > > so
> > >
> > > now I always suspect any USB cable I get and keep an eye on how
> > > well
> > >
> > > it is working.
> > >
> > > _______________________________________________
> > >
> > > mythtv-users mailing list
> > >
> > > mythtv-users@mythtv.org
> > >
> > > http://email.mg.glenb.net/c/eJxNTksKwyAUPE3cVUz8xYWLbnoP9fkSQW2JttDb15ZCC8PA_GDABnQgBUkW_BwAdHCDvDcoEA3AEkAtqJjUUQkZGTIaXIl5EmzLsXpaYye7ZU4aBdzgvJqVz2vEgCYGoYFr7g0j2e693yZ-npbLQE6tN1qefe8Pej22YRWXcnH1G6aK17f5aZzuLR6NHPZfjge__QuyVkHw
> > >
> > > http://email.mg.glenb.net/c/eJxFjTsOwjAQRE8Td1h2_AkpXNBQwRki27tOLJwAyQbE7bFEgTR6xeiNBlxMHoxm2UGQEaCLviKEPumUeoA2gm2TFaZDqw2KJHj0M5ZGi7HgEviCxCZnlfe9DTrFVKVOGZQymADyCMIogay4iejRqFPTnmve-Zb5_KGJXvy-jrW5-lzyMg6XvNGAlJ87EiFb3c867BuuW339j77f2j4X
> > >
> > > MythTV Forums: http://email.mg.glenb.net/c/eJxFjMsKwyAUBb8m7ipGrzFZuOim_6H3kRTyKMYU-vcVuigMB4YDQxElkQf1jJR7JAqY2uQ8CYhMRBZpsDIYH3gAz0aMxrTx2oGZV96z3rmqJbKMoycnCMxICV2eOEBolm0PTtQal1pfZ-funX005CjXprdPXepbH2VWJf7kdp1czpb_f1_9hDZF
> >
> > Thanks for all the suggestions. I will investigate all of them.
> > Something I do not see in here is an opinion that some software
> > problem could have evolved. I was kind of thinking of that as a
> > possibility given that it worked fine for so long then seems to be
> > degrading. OTOH I never thought of the possibility that the USB
> > connection could be degrading. I'm going to try Greg's connector,
> > assuming I can get parts during the Apocalypse. Also, his link
> > specifies Radio Shack parts. What's Radio Shack?!? ;-)
>
> Well folks this is getting frustrating. I addressed a possible
> ventilation issue. I also unplugged the power cord I had from the
> Myth box USB and connected it to an old iPad charger rated at 5V/2A.
> No help. It wouldn't record anything, no matter how much rebooting
> and power-cycling. So I concluded the HDPVR was hosed and got a new
> one (more accurately, a replacement circuit board for it). Powered
> it with the same wall wart. Recorded great for a day. Just turned
> it on and I have failed recordings and it won't respond when I try to
> manually play a channel. Reboot, and it works fine, same pattern as
> before.
>
> I finally got a molex connector and am still going to try what Greg
> suggested, but I really don't think it's a power issue. Apply makes
> good electronics and that wart has the same specs as the power supply
> that comes with the HDPVR. The HDPCR isn't overheating. It's not
> the HDPVR itself. That only leaves the software on the myth box.
> Anyone have ideas how to troubleshoot that?
>
>
> _______________________________________________mythtv-users mailing
> listmythtv-users@mythtv.org
> http://email.mg.glenb.net/c/eJxNTksKwyAUPE3cVUz8xYWLbnoP9fkSQW2JttDb15ZCC8PA_GDABnQgBUkW_BwAdHCDvDcoEA3AEkAtqJjUUQkZGTIaXIl5EmzLsXpaYye7ZU4aBdzgvJqVz2vEgCYGoYFr7g0j2e693yZ-npbLQE6tN1qefe8Pej22YRWXcnH1G6aK17f5aZzuLR6NHPZfjge__QuyVkHw
> http://email.mg.glenb.net/c/eJxFjTsOwjAQRE8Td1h2_AkpXNBQwRki27tOLJwAyQbE7bFEgTR6xeiNBlxMHoxm2UGQEaCLviKEPumUeoA2gm2TFaZDqw2KJHj0M5ZGi7HgEviCxCZnlfe9DTrFVKVOGZQymADyCMIogay4iejRqFPTnmve-Zb5_KGJXvy-jrW5-lzyMg6XvNGAlJ87EiFb3c867BuuW339j77f2j4X
> MythTV Forums: http://email.mg.glenb.net/c/eJxFjMsKwyAUBb8m7ipGrzFZuOim_6H3kRTyKMYU-vcVuigMB4YDQxElkQf1jJR7JAqY2uQ8CYhMRBZpsDIYH3gAz0aMxrTx2oGZV96z3rmqJbKMoycnCMxICV2eOEBolm0PTtQal1pfZ-funX005CjXprdPXepbH2VWJf7kdp1czpb_f1_9hDZF

have you tried a conf file in /etc/modprobe.d setting this option:
options ir-kbd-i2c enable_hdpvr=1
Re: HDPVR intermittent failure [ In reply to ]
On 6/27/20 9:46 PM, DryHeat122 . wrote:
> On Mon, May 11, 2020 at 12:59 PM DryHeat122 . <dryheat122@gmail.com
> <mailto:dryheat122@gmail.com>> wrote:
>
> On Mon, May 11, 2020 at 2:41 AM Stephen Worthington
> <stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>> wrote:
>
> On Sun, 10 May 2020 20:20:30 -0700, you wrote:
>
> >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com
> <mailto:gregl@nycap.rr.com>> wrote:
>
> >Ok thanks I will investigate that.  But it's been working
> fine with the
> >current power source for like a year now, and others on this
> list use it
> >too.
>
> USB cables often fit badly into the sockets.  If so, the
> connection
> generally gets worse over time as you get dirt or oxidisation
> on the
> contacts.  So badly fitting cables will degrade with time. 
> The result
> is that the voltage drop across the cable will increase
> markedly.  And
> they can be too thin - the amount of copper in the wires is
> too little
> and that causes high resistance and a big voltage drop across the
> length of the cable.  Some (most?) USB cables are designed
> only for
> data transmission, or to run very low power devices. For a
> high power
> device, you need a better (thicker) cable.  The high power
> devices do
> a negotiation with device supplying the power and request high
> power
> mode.  If the cable is not capable of high power, that
> negotiation is
> not supposed to work and the device should either only work in low
> power mode or it should turn itself off.  But USB cable makers
> often
> make cables not capable of high power transmission that will
> allow the
> high power mode negotiation to succeed.  So even though the device
> supplying the power is sending high current, the voltage drop
> in the
> cable means that at the other end, the voltage can be below
> the level
> required for proper operation or to fully charge the device's
> battery.
>
> I have had two notably bad experiences with USB cables.  One
> was a USB
> DVB-T tuner, and it was very like your experience - it would
> go for a
> number of days just fine, then suddenly stop.  If I unplugged
> it and
> plugged it in again, it would usually work again. When I finally
> investigated properly, I found the cable was just a little
> loose in
> the PC's socket.  I replaced the cable with one that fit more
> tightly
> and the tuner was much more reliable.  It still occasionally
> caused
> trouble, but only when I had bumped the cables (or in one
> case, after
> we had a small earthquake).  So because of that and because I
> needed
> more DVB-T tuners, I finally replaced all my DVB-T tuners with
> an 8
> tuner PCIe card.
>
> The second bad experience was my Samsung Galaxy Tab S2
> tablet.  Its
> USB charging cable was supplied with it by Samsung, so I
> assumed it
> was a good one.  But right from the start, the tablet took a
> long time
> to charge, and the time gradually got longer and longer and the
> battery life on one charge was getting less and less. And then I
> started to have to jiggle the cable in the socket to get it to
> charge
> at all.  I actually called the Samsung help line about this,
> and they
> said it sounds like a bad cable.  So I bought a expensive (NZ$30)
> Pudney & Lee charging cable, which was a fair bit longer than
> the old
> Samsung cable, but fit very tightly at both ends and was
> significantly
> thicker - it has more copper in the wires in the cable.  Then
> suddenly
> the battery charging times were what was specified for the tablet,
> rather than three times as long.  And over a number of charging
> cycles, the battery life came back again.  So the original Samsung
> supplied cable was clearly bad from the start - it is probably
> less
> than the specification required to charge the tablet properly
> as it is
> too thin and has too much voltage drop even when the plugs fit
> properly.  So definitely NZ$30 well spent.  But I am surprised
> that a
> reputable company like Samsung would supply a bad cable with an
> expensive top-of-the-line product like my tablet.  But they
> did - so
> now I always suspect any USB cable I get and keep an eye on
> how well
> it is working.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org <mailto:mythtv-users@mythtv.org>
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
>
> Thanks for all the suggestions.  I will investigate all of them. 
> Something I do not see in here is an opinion that some software
> problem could have evolved.  I was kind of thinking of that as a
> possibility given that it worked fine for so long then seems to be
> degrading.  OTOH I never thought of the possibility that the USB
> connection could be degrading.  I'm going to try Greg's connector,
> assuming I can get parts during the Apocalypse.  Also, his link
> specifies Radio Shack parts.  What's Radio Shack?!? ;-)
>
>
> Well folks this is getting frustrating.  I addressed a possible
> ventilation issue.  I also unplugged the power cord I had from the
> Myth box USB and connected it to an old iPad charger rated at 5V/2A. 
> No help.  It wouldn't record anything, no matter how much rebooting
> and power-cycling. So I concluded the HDPVR was hosed and got a new
> one (more accurately, a replacement circuit board for it).  Powered it
> with the same wall wart.  Recorded great for a day.  Just turned it on
> and I have failed recordings and it won't respond when I try to
> manually play a channel.  Reboot, and it works fine, same pattern as
> before.
>
> I finally got a molex connector and am still going to try what Greg
> suggested, but I really don't think it's a power issue.  Apply makes
> good electronics and that wart has the same specs as the power supply
> that comes with the HDPVR. The HDPCR isn't overheating.  It's not the
> HDPVR itself. That only leaves the software on the myth box.  Anyone
> have ideas how to troubleshoot that?
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

 The next time it won't record,try to cat it and see if it responds. 
This is the command I use,  cat /dev/video0 > test .. dmesg for the
proper port it's connected to. This may help too see if it is the
software or not..

I am curious were you got the motherboard? There used to be a place in
Ohio (I believe) ,but they have gone out of business.
Re: HDPVR intermittent failure [ In reply to ]
On Sat, Jun 27, 2020 at 7:51 PM glen <glenb@glenb.net> wrote:

> On Sat, 2020-06-27 at 18:46 -0700, DryHeat122 . wrote:
>
> On Mon, May 11, 2020 at 12:59 PM DryHeat122 . <dryheat122@gmail.com>
> wrote:
>
> On Mon, May 11, 2020 at 2:41 AM Stephen Worthington <
> stephen_agent@jsw.gen.nz> wrote:
>
> On Sun, 10 May 2020 20:20:30 -0700, you wrote:
>
> >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com> wrote:
>
> >Ok thanks I will investigate that. But it's been working fine with the
> >current power source for like a year now, and others on this list use it
> >too.
>
> USB cables often fit badly into the sockets. If so, the connection
> generally gets worse over time as you get dirt or oxidisation on the
> contacts. So badly fitting cables will degrade with time. The result
> is that the voltage drop across the cable will increase markedly. And
> they can be too thin - the amount of copper in the wires is too little
> and that causes high resistance and a big voltage drop across the
> length of the cable. Some (most?) USB cables are designed only for
> data transmission, or to run very low power devices. For a high power
> device, you need a better (thicker) cable. The high power devices do
> a negotiation with device supplying the power and request high power
> mode. If the cable is not capable of high power, that negotiation is
> not supposed to work and the device should either only work in low
> power mode or it should turn itself off. But USB cable makers often
> make cables not capable of high power transmission that will allow the
> high power mode negotiation to succeed. So even though the device
> supplying the power is sending high current, the voltage drop in the
> cable means that at the other end, the voltage can be below the level
> required for proper operation or to fully charge the device's battery.
>
> I have had two notably bad experiences with USB cables. One was a USB
> DVB-T tuner, and it was very like your experience - it would go for a
> number of days just fine, then suddenly stop. If I unplugged it and
> plugged it in again, it would usually work again. When I finally
> investigated properly, I found the cable was just a little loose in
> the PC's socket. I replaced the cable with one that fit more tightly
> and the tuner was much more reliable. It still occasionally caused
> trouble, but only when I had bumped the cables (or in one case, after
> we had a small earthquake). So because of that and because I needed
> more DVB-T tuners, I finally replaced all my DVB-T tuners with an 8
> tuner PCIe card.
>
> The second bad experience was my Samsung Galaxy Tab S2 tablet. Its
> USB charging cable was supplied with it by Samsung, so I assumed it
> was a good one. But right from the start, the tablet took a long time
> to charge, and the time gradually got longer and longer and the
> battery life on one charge was getting less and less. And then I
> started to have to jiggle the cable in the socket to get it to charge
> at all. I actually called the Samsung help line about this, and they
> said it sounds like a bad cable. So I bought a expensive (NZ$30)
> Pudney & Lee charging cable, which was a fair bit longer than the old
> Samsung cable, but fit very tightly at both ends and was significantly
> thicker - it has more copper in the wires in the cable. Then suddenly
> the battery charging times were what was specified for the tablet,
> rather than three times as long. And over a number of charging
> cycles, the battery life came back again. So the original Samsung
> supplied cable was clearly bad from the start - it is probably less
> than the specification required to charge the tablet properly as it is
> too thin and has too much voltage drop even when the plugs fit
> properly. So definitely NZ$30 well spent. But I am surprised that a
> reputable company like Samsung would supply a bad cable with an
> expensive top-of-the-line product like my tablet. But they did - so
> now I always suspect any USB cable I get and keep an eye on how well
> it is working.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> <http://email.mg.glenb.net/c/eJxNTksKwyAUPE3cVUz8xYWLbnoP9fkSQW2JttDb15ZCC8PA_GDABnQgBUkW_BwAdHCDvDcoEA3AEkAtqJjUUQkZGTIaXIl5EmzLsXpaYye7ZU4aBdzgvJqVz2vEgCYGoYFr7g0j2e693yZ-npbLQE6tN1qefe8Pej22YRWXcnH1G6aK17f5aZzuLR6NHPZfjge__QuyVkHw>
> http://wiki.mythtv.org/Mailing_List_etiquette
> <http://email.mg.glenb.net/c/eJxFjTsOwjAQRE8Td1h2_AkpXNBQwRki27tOLJwAyQbE7bFEgTR6xeiNBlxMHoxm2UGQEaCLviKEPumUeoA2gm2TFaZDqw2KJHj0M5ZGi7HgEviCxCZnlfe9DTrFVKVOGZQymADyCMIogay4iejRqFPTnmve-Zb5_KGJXvy-jrW5-lzyMg6XvNGAlJ87EiFb3c867BuuW339j77f2j4X>
> MythTV Forums: https://forum.mythtv.org
> <http://email.mg.glenb.net/c/eJxFjMsKwyAUBb8m7ipGrzFZuOim_6H3kRTyKMYU-vcVuigMB4YDQxElkQf1jJR7JAqY2uQ8CYhMRBZpsDIYH3gAz0aMxrTx2oGZV96z3rmqJbKMoycnCMxICV2eOEBolm0PTtQal1pfZ-funX005CjXprdPXepbH2VWJf7kdp1czpb_f1_9hDZF>
>
>
> Thanks for all the suggestions. I will investigate all of them.
> Something I do not see in here is an opinion that some software problem
> could have evolved. I was kind of thinking of that as a possibility given
> that it worked fine for so long then seems to be degrading. OTOH I never
> thought of the possibility that the USB connection could be degrading. I'm
> going to try Greg's connector, assuming I can get parts during the
> Apocalypse. Also, his link specifies Radio Shack parts. What's Radio
> Shack?!? ;-)
>
>
> Well folks this is getting frustrating. I addressed a possible
> ventilation issue. I also unplugged the power cord I had from the Myth box
> USB and connected it to an old iPad charger rated at 5V/2A. No help. It
> wouldn't record anything, no matter how much rebooting and power-cycling.
> So I concluded the HDPVR was hosed and got a new one (more accurately, a
> replacement circuit board for it). Powered it with the same wall wart.
> Recorded great for a day. Just turned it on and I have failed recordings
> and it won't respond when I try to manually play a channel. Reboot, and it
> works fine, same pattern as before.
>
> I finally got a molex connector and am still going to try what Greg
> suggested, but I really don't think it's a power issue. Apply makes good
> electronics and that wart has the same specs as the power supply that comes
> with the HDPVR. The HDPCR isn't overheating. It's not the HDPVR itself.
> That only leaves the software on the myth box. Anyone have ideas how to
> troubleshoot that?
>
> _______________________________________________
>
> mythtv-users mailing list
>
> mythtv-users@mythtv.org
>
>
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>
>
> <http://email.mg.glenb.net/c/eJxNTksKwyAUPE3cVUz8xYWLbnoP9fkSQW2JttDb15ZCC8PA_GDABnQgBUkW_BwAdHCDvDcoEA3AEkAtqJjUUQkZGTIaXIl5EmzLsXpaYye7ZU4aBdzgvJqVz2vEgCYGoYFr7g0j2e693yZ-npbLQE6tN1qefe8Pej22YRWXcnH1G6aK17f5aZzuLR6NHPZfjge__QuyVkHw>
>
>
> http://wiki.mythtv.org/Mailing_List_etiquette
>
>
> <http://email.mg.glenb.net/c/eJxFjTsOwjAQRE8Td1h2_AkpXNBQwRki27tOLJwAyQbE7bFEgTR6xeiNBlxMHoxm2UGQEaCLviKEPumUeoA2gm2TFaZDqw2KJHj0M5ZGi7HgEviCxCZnlfe9DTrFVKVOGZQymADyCMIogay4iejRqFPTnmve-Zb5_KGJXvy-jrW5-lzyMg6XvNGAlJ87EiFb3c867BuuW339j77f2j4X>
>
>
> MythTV Forums:
>
> https://forum.mythtv.org
>
>
> <http://email.mg.glenb.net/c/eJxFjMsKwyAUBb8m7ipGrzFZuOim_6H3kRTyKMYU-vcVuigMB4YDQxElkQf1jJR7JAqY2uQ8CYhMRBZpsDIYH3gAz0aMxrTx2oGZV96z3rmqJbKMoycnCMxICV2eOEBolm0PTtQal1pfZ-funX005CjXprdPXepbH2VWJf7kdp1czpb_f1_9hDZF>
>
>
> have you tried a conf file in /etc/modprobe.d setting this option:
>
>
> options ir-kbd-i2c enable_hdpvr=1
>
>
> No. does ir-kbd stand for infrared keyboard? I don't have one of those.
Re: HDPVR intermittent failure [ In reply to ]
On Sun, Jun 28, 2020 at 9:32 AM Greg <gregl@nycap.rr.com> wrote:

>
> On 6/27/20 9:46 PM, DryHeat122 . wrote:
>
> On Mon, May 11, 2020 at 12:59 PM DryHeat122 . <dryheat122@gmail.com>
> wrote:
>
>> On Mon, May 11, 2020 at 2:41 AM Stephen Worthington <
>> stephen_agent@jsw.gen.nz> wrote:
>>
>>> On Sun, 10 May 2020 20:20:30 -0700, you wrote:
>>>
>>> >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com> wrote:
>>>
>>> >Ok thanks I will investigate that. But it's been working fine with the
>>> >current power source for like a year now, and others on this list use it
>>> >too.
>>>
>>> USB cables often fit badly into the sockets. If so, the connection
>>> generally gets worse over time as you get dirt or oxidisation on the
>>> contacts. So badly fitting cables will degrade with time. The result
>>> is that the voltage drop across the cable will increase markedly. And
>>> they can be too thin - the amount of copper in the wires is too little
>>> and that causes high resistance and a big voltage drop across the
>>> length of the cable. Some (most?) USB cables are designed only for
>>> data transmission, or to run very low power devices. For a high power
>>> device, you need a better (thicker) cable. The high power devices do
>>> a negotiation with device supplying the power and request high power
>>> mode. If the cable is not capable of high power, that negotiation is
>>> not supposed to work and the device should either only work in low
>>> power mode or it should turn itself off. But USB cable makers often
>>> make cables not capable of high power transmission that will allow the
>>> high power mode negotiation to succeed. So even though the device
>>> supplying the power is sending high current, the voltage drop in the
>>> cable means that at the other end, the voltage can be below the level
>>> required for proper operation or to fully charge the device's battery.
>>>
>>> I have had two notably bad experiences with USB cables. One was a USB
>>> DVB-T tuner, and it was very like your experience - it would go for a
>>> number of days just fine, then suddenly stop. If I unplugged it and
>>> plugged it in again, it would usually work again. When I finally
>>> investigated properly, I found the cable was just a little loose in
>>> the PC's socket. I replaced the cable with one that fit more tightly
>>> and the tuner was much more reliable. It still occasionally caused
>>> trouble, but only when I had bumped the cables (or in one case, after
>>> we had a small earthquake). So because of that and because I needed
>>> more DVB-T tuners, I finally replaced all my DVB-T tuners with an 8
>>> tuner PCIe card.
>>>
>>> The second bad experience was my Samsung Galaxy Tab S2 tablet. Its
>>> USB charging cable was supplied with it by Samsung, so I assumed it
>>> was a good one. But right from the start, the tablet took a long time
>>> to charge, and the time gradually got longer and longer and the
>>> battery life on one charge was getting less and less. And then I
>>> started to have to jiggle the cable in the socket to get it to charge
>>> at all. I actually called the Samsung help line about this, and they
>>> said it sounds like a bad cable. So I bought a expensive (NZ$30)
>>> Pudney & Lee charging cable, which was a fair bit longer than the old
>>> Samsung cable, but fit very tightly at both ends and was significantly
>>> thicker - it has more copper in the wires in the cable. Then suddenly
>>> the battery charging times were what was specified for the tablet,
>>> rather than three times as long. And over a number of charging
>>> cycles, the battery life came back again. So the original Samsung
>>> supplied cable was clearly bad from the start - it is probably less
>>> than the specification required to charge the tablet properly as it is
>>> too thin and has too much voltage drop even when the plugs fit
>>> properly. So definitely NZ$30 well spent. But I am surprised that a
>>> reputable company like Samsung would supply a bad cable with an
>>> expensive top-of-the-line product like my tablet. But they did - so
>>> now I always suspect any USB cable I get and keep an eye on how well
>>> it is working.
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users@mythtv.org
>>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>>> http://wiki.mythtv.org/Mailing_List_etiquette
>>> MythTV Forums: https://forum.mythtv.org
>>
>>
>> Thanks for all the suggestions. I will investigate all of them.
>> Something I do not see in here is an opinion that some software problem
>> could have evolved. I was kind of thinking of that as a possibility given
>> that it worked fine for so long then seems to be degrading. OTOH I never
>> thought of the possibility that the USB connection could be degrading. I'm
>> going to try Greg's connector, assuming I can get parts during the
>> Apocalypse. Also, his link specifies Radio Shack parts. What's Radio
>> Shack?!? ;-)
>>
>
> Well folks this is getting frustrating. I addressed a possible
> ventilation issue. I also unplugged the power cord I had from the Myth box
> USB and connected it to an old iPad charger rated at 5V/2A. No help. It
> wouldn't record anything, no matter how much rebooting and power-cycling.
> So I concluded the HDPVR was hosed and got a new one (more accurately, a
> replacement circuit board for it). Powered it with the same wall wart.
> Recorded great for a day. Just turned it on and I have failed recordings
> and it won't respond when I try to manually play a channel. Reboot, and it
> works fine, same pattern as before.
>
> I finally got a molex connector and am still going to try what Greg
> suggested, but I really don't think it's a power issue. Apply makes good
> electronics and that wart has the same specs as the power supply that comes
> with the HDPVR. The HDPCR isn't overheating. It's not the HDPVR itself.
> That only leaves the software on the myth box. Anyone have ideas how to
> troubleshoot that?
>
> _______________________________________________
> mythtv-users mailing listmythtv-users@mythtv.orghttp://lists.mythtv.org/mailman/listinfo/mythtv-usershttp://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
> The next time it won't record,try to cat it and see if it responds. This
> is the command I use, cat /dev/video0 > test .. dmesg for the proper port
> it's connected to. This may help too see if it is the software or not..
>
> I am curious were you got the motherboard? There used to be a place in
> Ohio (I believe) ,but they have gone out of business.
>
I will give that a try. The circuit board I got some time ago and I think
it was on ebay.
Re: HDPVR intermittent failure [ In reply to ]
On Sun, 2020-06-28 at 09:45 -0700, DryHeat122 . wrote:
> On Sat, Jun 27, 2020 at 7:51 PM glen <glenb@glenb.net> wrote:
> > On Sat, 2020-06-27 at 18:46 -0700, DryHeat122 . wrote:
> > > On Mon, May 11, 2020 at 12:59 PM DryHeat122 . <
> > > dryheat122@gmail.com> wrote:
> > > > On Mon, May 11, 2020 at 2:41 AM Stephen Worthington <
> > > > stephen_agent@jsw.gen.nz> wrote:
> > > > > On Sun, 10 May 2020 20:20:30 -0700, you wrote:
> > > > >
> > > > >
> > > > >
> > > > > >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com>
> > > > > wrote:
> > > > >
> > > > >
> > > > >
> > > > > >Ok thanks I will investigate that. But it's been working
> > > > > fine with the
> > > > >
> > > > > >current power source for like a year now, and others on this
> > > > > list use it
> > > > >
> > > > > >too.
> > > > >
> > > > >
> > > > >
> > > > > USB cables often fit badly into the sockets. If so, the
> > > > > connection
> > > > >
> > > > > generally gets worse over time as you get dirt or oxidisation
> > > > > on the
> > > > >
> > > > > contacts. So badly fitting cables will degrade with time.
> > > > > The result
> > > > >
> > > > > is that the voltage drop across the cable will increase
> > > > > markedly. And
> > > > >
> > > > > they can be too thin - the amount of copper in the wires is
> > > > > too little
> > > > >
> > > > > and that causes high resistance and a big voltage drop across
> > > > > the
> > > > >
> > > > > length of the cable. Some (most?) USB cables are designed
> > > > > only for
> > > > >
> > > > > data transmission, or to run very low power devices. For a
> > > > > high power
> > > > >
> > > > > device, you need a better (thicker) cable. The high power
> > > > > devices do
> > > > >
> > > > > a negotiation with device supplying the power and request
> > > > > high power
> > > > >
> > > > > mode. If the cable is not capable of high power, that
> > > > > negotiation is
> > > > >
> > > > > not supposed to work and the device should either only work
> > > > > in low
> > > > >
> > > > > power mode or it should turn itself off. But USB cable
> > > > > makers often
> > > > >
> > > > > make cables not capable of high power transmission that will
> > > > > allow the
> > > > >
> > > > > high power mode negotiation to succeed. So even though the
> > > > > device
> > > > >
> > > > > supplying the power is sending high current, the voltage drop
> > > > > in the
> > > > >
> > > > > cable means that at the other end, the voltage can be below
> > > > > the level
> > > > >
> > > > > required for proper operation or to fully charge the device's
> > > > > battery.
> > > > >
> > > > >
> > > > >
> > > > > I have had two notably bad experiences with USB cables. One
> > > > > was a USB
> > > > >
> > > > > DVB-T tuner, and it was very like your experience - it would
> > > > > go for a
> > > > >
> > > > > number of days just fine, then suddenly stop. If I unplugged
> > > > > it and
> > > > >
> > > > > plugged it in again, it would usually work again. When I
> > > > > finally
> > > > >
> > > > > investigated properly, I found the cable was just a little
> > > > > loose in
> > > > >
> > > > > the PC's socket. I replaced the cable with one that fit more
> > > > > tightly
> > > > >
> > > > > and the tuner was much more reliable. It still occasionally
> > > > > caused
> > > > >
> > > > > trouble, but only when I had bumped the cables (or in one
> > > > > case, after
> > > > >
> > > > > we had a small earthquake). So because of that and because I
> > > > > needed
> > > > >
> > > > > more DVB-T tuners, I finally replaced all my DVB-T tuners
> > > > > with an 8
> > > > >
> > > > > tuner PCIe card.
> > > > >
> > > > >
> > > > >
> > > > > The second bad experience was my Samsung Galaxy Tab S2
> > > > > tablet. Its
> > > > >
> > > > > USB charging cable was supplied with it by Samsung, so I
> > > > > assumed it
> > > > >
> > > > > was a good one. But right from the start, the tablet took a
> > > > > long time
> > > > >
> > > > > to charge, and the time gradually got longer and longer and
> > > > > the
> > > > >
> > > > > battery life on one charge was getting less and less. And
> > > > > then I
> > > > >
> > > > > started to have to jiggle the cable in the socket to get it
> > > > > to charge
> > > > >
> > > > > at all. I actually called the Samsung help line about this,
> > > > > and they
> > > > >
> > > > > said it sounds like a bad cable. So I bought a expensive
> > > > > (NZ$30)
> > > > >
> > > > > Pudney & Lee charging cable, which was a fair bit longer than
> > > > > the old
> > > > >
> > > > > Samsung cable, but fit very tightly at both ends and was
> > > > > significantly
> > > > >
> > > > > thicker - it has more copper in the wires in the cable. Then
> > > > > suddenly
> > > > >
> > > > > the battery charging times were what was specified for the
> > > > > tablet,
> > > > >
> > > > > rather than three times as long. And over a number of
> > > > > charging
> > > > >
> > > > > cycles, the battery life came back again. So the original
> > > > > Samsung
> > > > >
> > > > > supplied cable was clearly bad from the start - it is
> > > > > probably less
> > > > >
> > > > > than the specification required to charge the tablet properly
> > > > > as it is
> > > > >
> > > > > too thin and has too much voltage drop even when the plugs
> > > > > fit
> > > > >
> > > > > properly. So definitely NZ$30 well spent. But I am
> > > > > surprised that a
> > > > >
> > > > > reputable company like Samsung would supply a bad cable with
> > > > > an
> > > > >
> > > > > expensive top-of-the-line product like my tablet. But they
> > > > > did - so
> > > > >
> > > > > now I always suspect any USB cable I get and keep an eye on
> > > > > how well
> > > > >
> > > > > it is working.
> > > > >
> > > > > _______________________________________________
> > > > >
> > > > > mythtv-users mailing list
> > > > >
> > > > > mythtv-users@mythtv.org
> > > > >
> > > > > http://email.mg.glenb.net/c/eJxNjkEOwiAURE9TdhL-LxRZsHDjPT4FWhKgpqCJt7caE01mM29mkvF2juSVZMniqAAwOq2CjmDOTiNMQjo1ChkBlQaBIhrNZyohD1IsOVTHa-hstQjehAkhSEXGqzkQSQQhKOIkndAs27X32zBeBrweyqn1xsuzr_3Bt305UKGUC9VvmGrc3vDTON1b2Bvb7b89Hvz2L-CbPz8
> > > > >
> > > > > http://email.mg.glenb.net/c/eJxFjcsOgjAQRb-G7mw605csunDjSr-BUJhCY0GFQePfS-LC5K5OzsntQ5fa3hqRA2oLgCl6Sz5BfYwewSkTrVYmAVoPClWqvezaiUpl1FBojnImFmNwYNErU8cumnRE5zTolsgBJddjR6KEkflR6VOF533vfMty-vDIL3lfhp1c21zyPDSXvHJDnJ8bMZNYws86bCst6_76j74P1DtC
> > > > >
> > > > > MythTV Forums: http://email.mg.glenb.net/c/eJxFjDEKwzAMRU8TbzWyItX24KFL72ElVlJI0uI4hd6-gQ6FP7zHgz-mQfPIZB4Je3YOVTwXry4G8eiuQMI9kDpk7wBBo7dDXsvSEUxL2cRupZk5CUTCnIFFmVwIKBTDSCcPnkouZklza6-9628d3s_psx6rXT9tbm_7rJOp6SeXYy91P-__7QsiqTJl
> > > >
> > > > Thanks for all the suggestions. I will investigate all of
> > > > them. Something I do not see in here is an opinion that some
> > > > software problem could have evolved. I was kind of thinking of
> > > > that as a possibility given that it worked fine for so long
> > > > then seems to be degrading. OTOH I never thought of the
> > > > possibility that the USB connection could be degrading. I'm
> > > > going to try Greg's connector, assuming I can get parts during
> > > > the Apocalypse. Also, his link specifies Radio Shack parts.
> > > > What's Radio Shack?!? ;-)
> > >
> > > Well folks this is getting frustrating. I addressed a possible
> > > ventilation issue. I also unplugged the power cord I had from
> > > the Myth box USB and connected it to an old iPad charger rated at
> > > 5V/2A. No help. It wouldn't record anything, no matter how much
> > > rebooting and power-cycling. So I concluded the HDPVR was hosed
> > > and got a new one (more accurately, a replacement circuit board
> > > for it). Powered it with the same wall wart. Recorded great for
> > > a day. Just turned it on and I have failed recordings and it
> > > won't respond when I try to manually play a channel. Reboot, and
> > > it works fine, same pattern as before.
> > >
> > > I finally got a molex connector and am still going to try what
> > > Greg suggested, but I really don't think it's a power issue.
> > > Apply makes good electronics and that wart has the same specs as
> > > the power supply that comes with the HDPVR. The HDPCR isn't
> > > overheating. It's not the HDPVR itself. That only leaves the
> > > software on the myth box. Anyone have ideas how to troubleshoot
> > > that?
> > >
> > >
> > > _______________________________________________mythtv-users
> > > mailing listmythtv-users@mythtv.org
> > > http://email.mg.glenb.net/c/eJxNjkEOwiAURE9TdhL-LxRZsHDjPT4FWhKgpqCJt7caE01mM29mkvF2juSVZMniqAAwOq2CjmDOTiNMQjo1ChkBlQaBIhrNZyohD1IsOVTHa-hstQjehAkhSEXGqzkQSQQhKOIkndAs27X32zBeBrweyqn1xsuzr_3Bt305UKGUC9VvmGrc3vDTON1b2Bvb7b89Hvz2L-CbPz8
> > > http://email.mg.glenb.net/c/eJxFjcsOgjAQRb-G7mw605csunDjSr-BUJhCY0GFQePfS-LC5K5OzsntQ5fa3hqRA2oLgCl6Sz5BfYwewSkTrVYmAVoPClWqvezaiUpl1FBojnImFmNwYNErU8cumnRE5zTolsgBJddjR6KEkflR6VOF533vfMty-vDIL3lfhp1c21zyPDSXvHJDnJ8bMZNYws86bCst6_76j74P1DtC
> > > MythTV Forums: http://email.mg.glenb.net/c/eJxFjDEKwzAMRU8TbzWyItX24KFL72ElVlJI0uI4hd6-gQ6FP7zHgz-mQfPIZB4Je3YOVTwXry4G8eiuQMI9kDpk7wBBo7dDXsvSEUxL2cRupZk5CUTCnIFFmVwIKBTDSCcPnkouZklza6-9628d3s_psx6rXT9tbm_7rJOp6SeXYy91P-__7QsiqTJl
> >
> > have you tried a conf file in /etc/modprobe.d setting this option:
> > options ir-kbd-i2c enable_hdpvr=1
> >
> No. does ir-kbd stand for infrared keyboard? I don't have one of
> those.

if you are using nvidia, recently, the drm driver for nvidia brought in
different dependent modules and this was one whether or not you have
hardware using it. check your loaded modules (lsmod) to see if it is
loading. i had this issue with no ir hardware and had hdpvr issues
until i changed that option. simple enough to add a conf file and see
if you get a difference or not.
Re: HDPVR intermittent failure [ In reply to ]
On Sun, Jun 28, 2020 at 9:32 AM Greg <gregl@nycap.rr.com> wrote:

>
> On 6/27/20 9:46 PM, DryHeat122 . wrote:
>
> On Mon, May 11, 2020 at 12:59 PM DryHeat122 . <dryheat122@gmail.com>
> wrote:
>
>> On Mon, May 11, 2020 at 2:41 AM Stephen Worthington <
>> stephen_agent@jsw.gen.nz> wrote:
>>
>>> On Sun, 10 May 2020 20:20:30 -0700, you wrote:
>>>
>>> >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com> wrote:
>>>
>>> >Ok thanks I will investigate that. But it's been working fine with the
>>> >current power source for like a year now, and others on this list use it
>>> >too.
>>>
>>> USB cables often fit badly into the sockets. If so, the connection
>>> generally gets worse over time as you get dirt or oxidisation on the
>>> contacts. So badly fitting cables will degrade with time. The result
>>> is that the voltage drop across the cable will increase markedly. And
>>> they can be too thin - the amount of copper in the wires is too little
>>> and that causes high resistance and a big voltage drop across the
>>> length of the cable. Some (most?) USB cables are designed only for
>>> data transmission, or to run very low power devices. For a high power
>>> device, you need a better (thicker) cable. The high power devices do
>>> a negotiation with device supplying the power and request high power
>>> mode. If the cable is not capable of high power, that negotiation is
>>> not supposed to work and the device should either only work in low
>>> power mode or it should turn itself off. But USB cable makers often
>>> make cables not capable of high power transmission that will allow the
>>> high power mode negotiation to succeed. So even though the device
>>> supplying the power is sending high current, the voltage drop in the
>>> cable means that at the other end, the voltage can be below the level
>>> required for proper operation or to fully charge the device's battery.
>>>
>>> I have had two notably bad experiences with USB cables. One was a USB
>>> DVB-T tuner, and it was very like your experience - it would go for a
>>> number of days just fine, then suddenly stop. If I unplugged it and
>>> plugged it in again, it would usually work again. When I finally
>>> investigated properly, I found the cable was just a little loose in
>>> the PC's socket. I replaced the cable with one that fit more tightly
>>> and the tuner was much more reliable. It still occasionally caused
>>> trouble, but only when I had bumped the cables (or in one case, after
>>> we had a small earthquake). So because of that and because I needed
>>> more DVB-T tuners, I finally replaced all my DVB-T tuners with an 8
>>> tuner PCIe card.
>>>
>>> The second bad experience was my Samsung Galaxy Tab S2 tablet. Its
>>> USB charging cable was supplied with it by Samsung, so I assumed it
>>> was a good one. But right from the start, the tablet took a long time
>>> to charge, and the time gradually got longer and longer and the
>>> battery life on one charge was getting less and less. And then I
>>> started to have to jiggle the cable in the socket to get it to charge
>>> at all. I actually called the Samsung help line about this, and they
>>> said it sounds like a bad cable. So I bought a expensive (NZ$30)
>>> Pudney & Lee charging cable, which was a fair bit longer than the old
>>> Samsung cable, but fit very tightly at both ends and was significantly
>>> thicker - it has more copper in the wires in the cable. Then suddenly
>>> the battery charging times were what was specified for the tablet,
>>> rather than three times as long. And over a number of charging
>>> cycles, the battery life came back again. So the original Samsung
>>> supplied cable was clearly bad from the start - it is probably less
>>> than the specification required to charge the tablet properly as it is
>>> too thin and has too much voltage drop even when the plugs fit
>>> properly. So definitely NZ$30 well spent. But I am surprised that a
>>> reputable company like Samsung would supply a bad cable with an
>>> expensive top-of-the-line product like my tablet. But they did - so
>>> now I always suspect any USB cable I get and keep an eye on how well
>>> it is working.
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users@mythtv.org
>>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>>> http://wiki.mythtv.org/Mailing_List_etiquette
>>> MythTV Forums: https://forum.mythtv.org
>>
>>
>> Thanks for all the suggestions. I will investigate all of them.
>> Something I do not see in here is an opinion that some software problem
>> could have evolved. I was kind of thinking of that as a possibility given
>> that it worked fine for so long then seems to be degrading. OTOH I never
>> thought of the possibility that the USB connection could be degrading. I'm
>> going to try Greg's connector, assuming I can get parts during the
>> Apocalypse. Also, his link specifies Radio Shack parts. What's Radio
>> Shack?!? ;-)
>>
>
> Well folks this is getting frustrating. I addressed a possible
> ventilation issue. I also unplugged the power cord I had from the Myth box
> USB and connected it to an old iPad charger rated at 5V/2A. No help. It
> wouldn't record anything, no matter how much rebooting and power-cycling.
> So I concluded the HDPVR was hosed and got a new one (more accurately, a
> replacement circuit board for it). Powered it with the same wall wart.
> Recorded great for a day. Just turned it on and I have failed recordings
> and it won't respond when I try to manually play a channel. Reboot, and it
> works fine, same pattern as before.
>
> I finally got a molex connector and am still going to try what Greg
> suggested, but I really don't think it's a power issue. Apply makes good
> electronics and that wart has the same specs as the power supply that comes
> with the HDPVR. The HDPCR isn't overheating. It's not the HDPVR itself.
> That only leaves the software on the myth box. Anyone have ideas how to
> troubleshoot that?
>
> _______________________________________________
> mythtv-users mailing listmythtv-users@mythtv.orghttp://lists.mythtv.org/mailman/listinfo/mythtv-usershttp://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
> The next time it won't record,try to cat it and see if it responds. This
> is the command I use, cat /dev/video0 > test .. dmesg for the proper port
> it's connected to. This may help too see if it is the software or not..
>
> I am curious were you got the motherboard? There used to be a place in
> Ohio (I believe) ,but they have gone out of business.
>
It failed again (despite putting the conf file in place). Here's the
result:

steve@steve-EP45-UD3P:~$ cat /dev/video0 > test.ts
cat: /dev/video0: Input/output error

I don't know how to "dmesg for the proper port it's connected to." I think
it's just connected to a USB port, but I don't know how to find out which
one. Can you be more specific?
Re: HDPVR intermittent failure [ In reply to ]
On 7/1/2020 9:23 PM, DryHeat122 . wrote:
>
> On Sun, Jun 28, 2020 at 9:32 AM Greg <gregl@nycap.rr.com
> <mailto:gregl@nycap.rr.com>> wrote:
>
>
> On 6/27/20 9:46 PM, DryHeat122 . wrote:
>> On Mon, May 11, 2020 at 12:59 PM DryHeat122 .
>> <dryheat122@gmail.com <mailto:dryheat122@gmail.com>> wrote:
>>
>> On Mon, May 11, 2020 at 2:41 AM Stephen Worthington
>> <stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>>
>> wrote:
>>
>> On Sun, 10 May 2020 20:20:30 -0700, you wrote:
>>
>> >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com
>> <mailto:gregl@nycap.rr.com>> wrote:
>>
>> >Ok thanks I will investigate that.  But it's been
>> working fine with the
>> >current power source for like a year now, and others on
>> this list use it
>> >too.
>>
>> <snip><https://forum.mythtv.org>
>>
>>
>> Thanks for all the suggestions.  I will investigate all of
>> them.  Something I do not see in here is an opinion that some
>> software problem could have evolved.  I was kind of thinking
>> of that as a possibility given that it worked fine for so
>> long then seems to be degrading.  OTOH I never thought of the
>> possibility that the USB connection could be degrading.  I'm
>> going to try Greg's connector, assuming I can get parts
>> during the Apocalypse.  Also, his link specifies Radio Shack
>> parts.  What's Radio Shack?!? ;-)
>>
>>
>> Well folks this is getting frustrating.  I addressed a possible
>> ventilation issue.  I also unplugged the power cord I had from
>> the Myth box USB and connected it to an old iPad charger rated at
>> 5V/2A.  No help.  It wouldn't record anything, no matter how much
>> rebooting and power-cycling. So I concluded the HDPVR was hosed
>> and got a new one (more accurately, a replacement circuit board
>> for it).  Powered it with the same wall wart. Recorded great for
>> a day.  Just turned it on and I have failed recordings and it
>> won't respond when I try to manually play a channel.  Reboot, and
>> it works fine, same pattern as before.
>>
>> I finally got a molex connector and am still going to try what
>> Greg suggested, but I really don't think it's a power issue. 
>> Apply makes good electronics and that wart has the same specs as
>> the power supply that comes with the HDPVR.  The HDPCR isn't
>> overheating.  It's not the HDPVR itself.  That only leaves the
>> software on the myth box.  Anyone have ideas how to troubleshoot
>> that?
>>
>>
>  The next time it won't record,try to cat it and see if it
> responds.  This is the command I use,  cat /dev/video0 > test ..
> dmesg for the proper port it's connected to. This may help too see
> if it is the software or not..
>
> I am curious were you got the motherboard? There used to be a
> place in Ohio (I believe) ,but they have gone out of business.
>
> It failed again (despite putting the conf file in place).  Here's the
> result:
>
> steve@steve-EP45-UD3P:~$ cat /dev/video0 > test.ts
> cat: /dev/video0: Input/output error
>
> I don't know how to "dmesg for the proper port it's connected to."  I
> think it's just connected to a USB port, but I don't know how to find
> out which one. Can you be more specific?
>
>
This works on my system

dmesg | grep pvr
[    6.231302] hdpvr 2-2:1.0: firmware version 0x15 dated Jun 17 2010
09:26:53
[    6.452748] hdpvr 2-2:1.0: device now attached to video0
[    6.452844] usbcore: registered new interface driver hdpvr
docbuntu:~$


Jim
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: HDPVR intermittent failure [ In reply to ]
On Thu, Jul 2, 2020, 5:08 AM Jim <lists@morton.hrcoxmail.com> wrote:

> On 7/1/2020 9:23 PM, DryHeat122 . wrote:
> >
> > On Sun, Jun 28, 2020 at 9:32 AM Greg <gregl@nycap.rr.com
> > <mailto:gregl@nycap.rr.com>> wrote:
> >
> >
> > On 6/27/20 9:46 PM, DryHeat122 . wrote:
> >> On Mon, May 11, 2020 at 12:59 PM DryHeat122 .
> >> <dryheat122@gmail.com <mailto:dryheat122@gmail.com>> wrote:
> >>
> >> On Mon, May 11, 2020 at 2:41 AM Stephen Worthington
> >> <stephen_agent@jsw.gen.nz <mailto:stephen_agent@jsw.gen.nz>>
> >> wrote:
> >>
> >> On Sun, 10 May 2020 20:20:30 -0700, you wrote:
> >>
> >> >On Sun, May 10, 2020, 7:58 PM Greg <gregl@nycap.rr.com
> >> <mailto:gregl@nycap.rr.com>> wrote:
> >>
> >> >Ok thanks I will investigate that. But it's been
> >> working fine with the
> >> >current power source for like a year now, and others on
> >> this list use it
> >> >too.
> >>
> >> <snip><https://forum.mythtv.org>
> >>
> >>
> >> Thanks for all the suggestions. I will investigate all of
> >> them. Something I do not see in here is an opinion that some
> >> software problem could have evolved. I was kind of thinking
> >> of that as a possibility given that it worked fine for so
> >> long then seems to be degrading. OTOH I never thought of the
> >> possibility that the USB connection could be degrading. I'm
> >> going to try Greg's connector, assuming I can get parts
> >> during the Apocalypse. Also, his link specifies Radio Shack
> >> parts. What's Radio Shack?!? ;-)
> >>
> >>
> >> Well folks this is getting frustrating. I addressed a possible
> >> ventilation issue. I also unplugged the power cord I had from
> >> the Myth box USB and connected it to an old iPad charger rated at
> >> 5V/2A. No help. It wouldn't record anything, no matter how much
> >> rebooting and power-cycling. So I concluded the HDPVR was hosed
> >> and got a new one (more accurately, a replacement circuit board
> >> for it). Powered it with the same wall wart. Recorded great for
> >> a day. Just turned it on and I have failed recordings and it
> >> won't respond when I try to manually play a channel. Reboot, and
> >> it works fine, same pattern as before.
> >>
> >> I finally got a molex connector and am still going to try what
> >> Greg suggested, but I really don't think it's a power issue.
> >> Apply makes good electronics and that wart has the same specs as
> >> the power supply that comes with the HDPVR. The HDPCR isn't
> >> overheating. It's not the HDPVR itself. That only leaves the
> >> software on the myth box. Anyone have ideas how to troubleshoot
> >> that?
> >>
> >>
> > The next time it won't record,try to cat it and see if it
> > responds. This is the command I use, cat /dev/video0 > test ..
> > dmesg for the proper port it's connected to. This may help too see
> > if it is the software or not..
> >
> > I am curious were you got the motherboard? There used to be a
> > place in Ohio (I believe) ,but they have gone out of business.
> >
> > It failed again (despite putting the conf file in place). Here's the
> > result:
> >
> > steve@steve-EP45-UD3P:~$ cat /dev/video0 > test.ts
> > cat: /dev/video0: Input/output error
> >
> > I don't know how to "dmesg for the proper port it's connected to." I
> > think it's just connected to a USB port, but I don't know how to find
> > out which one. Can you be more specific?
> >
> >
> This works on my system
>
> dmesg | grep pvr
> [ 6.231302] hdpvr 2-2:1.0: firmware version 0x15 dated Jun 17 2010
> 09:26:53
> [ 6.452748] hdpvr 2-2:1.0: device now attached to video0
> [ 6.452844] usbcore: registered new interface driver hdpvr
> docbuntu:~$
>

Ok next time it crashes I will try that.

>
Re: HDPVR intermittent failure [ In reply to ]
On 7/2/2020 9:35 AM, DryHeat122 . wrote:
>
>
> On Thu, Jul 2, 2020, 5:08 AM Jim <lists@morton.hrcoxmail.com
> <mailto:lists@morton.hrcoxmail.com>> wrote:
>
> On 7/1/2020 9:23 PM, DryHeat122 . wrote:
> >
> > On Sun, Jun 28, 2020 at 9:32 AM Greg <gregl@nycap.rr.com
> <mailto:gregl@nycap.rr.com>
> > <mailto:gregl@nycap.rr.com <mailto:gregl@nycap.rr.com>>> wrote:
> >
> >
> >     On 6/27/20 9:46 PM, DryHeat122 . wrote:
> >>     On Mon, May 11, 2020 at 12:59 PM DryHeat122 .
> >>     <dryheat122@gmail.com <mailto:dryheat122@gmail.com>
> <mailto:dryheat122@gmail.com <mailto:dryheat122@gmail.com>>> wrote:
> >>
> >>         On Mon, May 11, 2020 at 2:41 AM Stephen Worthington
> >>         <stephen_agent@jsw.gen.nz
> <mailto:stephen_agent@jsw.gen.nz> <mailto:stephen_agent@jsw.gen.nz
> <mailto:stephen_agent@jsw.gen.nz>>>
> >>         wrote:
> >>
> >>             On Sun, 10 May 2020 20:20:30 -0700, you wrote:
> >>
> >>             >On Sun, May 10, 2020, 7:58 PM Greg
> <gregl@nycap.rr.com <mailto:gregl@nycap.rr.com>
> >>             <mailto:gregl@nycap.rr.com
> <mailto:gregl@nycap.rr.com>>> wrote:
> >>
> >>             >Ok thanks I will investigate that.  But it's been
> >>             working fine with the
> >>             >current power source for like a year now, and
> others on
> >>             this list use it
> >>             >too.
> >>
> >>             <snip><https://forum.mythtv.org>
> >>
> >>
> >>         Thanks for all the suggestions.  I will investigate all of
> >>         them.  Something I do not see in here is an opinion
> that some
> >>         software problem could have evolved.  I was kind of
> thinking
> >>         of that as a possibility given that it worked fine for so
> >>         long then seems to be degrading.  OTOH I never thought
> of the
> >>         possibility that the USB connection could be
> degrading.  I'm
> >>         going to try Greg's connector, assuming I can get parts
> >>         during the Apocalypse.  Also, his link specifies Radio
> Shack
> >>         parts.  What's Radio Shack?!? ;-)
> >>
> >>
> >>     Well folks this is getting frustrating.  I addressed a possible
> >>     ventilation issue.  I also unplugged the power cord I had from
> >>     the Myth box USB and connected it to an old iPad charger
> rated at
> >>     5V/2A.  No help.  It wouldn't record anything, no matter
> how much
> >>     rebooting and power-cycling. So I concluded the HDPVR was hosed
> >>     and got a new one (more accurately, a replacement circuit board
> >>     for it).  Powered it with the same wall wart. Recorded
> great for
> >>     a day.  Just turned it on and I have failed recordings and it
> >>     won't respond when I try to manually play a channel. 
> Reboot, and
> >>     it works fine, same pattern as before.
> >>
> >>     I finally got a molex connector and am still going to try what
> >>     Greg suggested, but I really don't think it's a power issue.
> >>     Apply makes good electronics and that wart has the same
> specs as
> >>     the power supply that comes with the HDPVR. The HDPCR isn't
> >>     overheating.  It's not the HDPVR itself. That only leaves the
> >>     software on the myth box.  Anyone have ideas how to
> troubleshoot
> >>     that?
> >>
> >>
> >      The next time it won't record,try to cat it and see if it
> >     responds.  This is the command I use,  cat /dev/video0 > test ..
> >     dmesg for the proper port it's connected to. This may help
> too see
> >     if it is the software or not..
> >
> >     I am curious were you got the motherboard? There used to be a
> >     place in Ohio (I believe) ,but they have gone out of business.
> >
> > It failed again (despite putting the conf file in place). 
> Here's the
> > result:
> >
> > steve@steve-EP45-UD3P:~$ cat /dev/video0 > test.ts
> > cat: /dev/video0: Input/output error
> >
> > I don't know how to "dmesg for the proper port it's connected
> to."  I
> > think it's just connected to a USB port, but I don't know how to
> find
> > out which one. Can you be more specific?
> >
> >
> This works on my system
>
> dmesg | grep pvr
> [    6.231302] hdpvr 2-2:1.0: firmware version 0x15 dated Jun 17 2010
> 09:26:53
> [    6.452748] hdpvr 2-2:1.0: device now attached to video0
> [    6.452844] usbcore: registered new interface driver hdpvr
> docbuntu:~$
>
>
> Ok next time it crashes I will try that.
>
>
Just to be clear - this is to confirm which device your hdpvr is
attached to
such as  /dev/video0 so that you can formulate the proper cat command.

Jim
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: HDPVR intermittent failure [ In reply to ]
On 7/2/2020 10:35 AM, DryHeat122 . wrote:
>
>
> On Thu, Jul 2, 2020, 5:08 AM Jim <lists@morton.hrcoxmail.com
> <mailto:lists@morton.hrcoxmail.com>> wrote:
>
> On 7/1/2020 9:23 PM, DryHeat122 . wrote:
> >
> > On Sun, Jun 28, 2020 at 9:32 AM Greg <gregl@nycap.rr.com
> <mailto:gregl@nycap.rr.com>
> > <mailto:gregl@nycap.rr.com <mailto:gregl@nycap.rr.com>>> wrote:
> >
> >
> >     On 6/27/20 9:46 PM, DryHeat122 . wrote:
> >>     On Mon, May 11, 2020 at 12:59 PM DryHeat122 .
> >>     <dryheat122@gmail.com <mailto:dryheat122@gmail.com>
> <mailto:dryheat122@gmail.com <mailto:dryheat122@gmail.com>>> wrote:
> >>
> >>         On Mon, May 11, 2020 at 2:41 AM Stephen Worthington
> >>         <stephen_agent@jsw.gen.nz
> <mailto:stephen_agent@jsw.gen.nz> <mailto:stephen_agent@jsw.gen.nz
> <mailto:stephen_agent@jsw.gen.nz>>>
> >>         wrote:
> >>
> >>             On Sun, 10 May 2020 20:20:30 -0700, you wrote:
> >>
> >>             >On Sun, May 10, 2020, 7:58 PM Greg
> <gregl@nycap.rr.com <mailto:gregl@nycap.rr.com>
> >>             <mailto:gregl@nycap.rr.com
> <mailto:gregl@nycap.rr.com>>> wrote:
> >>
> >>             >Ok thanks I will investigate that.  But it's been
> >>             working fine with the
> >>             >current power source for like a year now, and others on
> >>             this list use it
> >>             >too.
> >>
> >>             <snip><https://forum.mythtv.org>
> >>
> >>
> >>         Thanks for all the suggestions.  I will investigate all of
> >>         them.  Something I do not see in here is an opinion that
> some
> >>         software problem could have evolved.  I was kind of thinking
> >>         of that as a possibility given that it worked fine for so
> >>         long then seems to be degrading.  OTOH I never thought
> of the
> >>         possibility that the USB connection could be degrading.  I'm
> >>         going to try Greg's connector, assuming I can get parts
> >>         during the Apocalypse.  Also, his link specifies Radio Shack
> >>         parts.  What's Radio Shack?!? ;-)
> >>
> >>
> >>     Well folks this is getting frustrating.  I addressed a possible
> >>     ventilation issue.  I also unplugged the power cord I had from
> >>     the Myth box USB and connected it to an old iPad charger
> rated at
> >>     5V/2A.  No help.  It wouldn't record anything, no matter how
> much
> >>     rebooting and power-cycling. So I concluded the HDPVR was hosed
> >>     and got a new one (more accurately, a replacement circuit board
> >>     for it).  Powered it with the same wall wart. Recorded great for
> >>     a day.  Just turned it on and I have failed recordings and it
> >>     won't respond when I try to manually play a channel.
> Reboot, and
> >>     it works fine, same pattern as before.
> >>
> >>     I finally got a molex connector and am still going to try what
> >>     Greg suggested, but I really don't think it's a power issue.
> >>     Apply makes good electronics and that wart has the same specs as
> >>     the power supply that comes with the HDPVR.  The HDPCR isn't
> >>     overheating.  It's not the HDPVR itself.  That only leaves the
> >>     software on the myth box.  Anyone have ideas how to troubleshoot
> >>     that?
> >>
> >>
> >      The next time it won't record,try to cat it and see if it
> >     responds.  This is the command I use,  cat /dev/video0 > test ..
> >     dmesg for the proper port it's connected to. This may help
> too see
> >     if it is the software or not..
> >
> >     I am curious were you got the motherboard? There used to be a
> >     place in Ohio (I believe) ,but they have gone out of business.
> >
> > It failed again (despite putting the conf file in place).  Here's
> the
> > result:
> >
> > steve@steve-EP45-UD3P:~$ cat /dev/video0 > test.ts
> > cat: /dev/video0: Input/output error
> >
> > I don't know how to "dmesg for the proper port it's connected
> to."  I
> > think it's just connected to a USB port, but I don't know how to
> find
> > out which one. Can you be more specific?
> >
> >
> This works on my system
>
> dmesg | grep pvr
> [    6.231302] hdpvr 2-2:1.0: firmware version 0x15 dated Jun 17 2010
> 09:26:53
> [    6.452748] hdpvr 2-2:1.0: device now attached to video0
> [    6.452844] usbcore: registered new interface driver hdpvr
> docbuntu:~$
>
>
> Ok next time it crashes I will try that.
>
>

I think the latest firmware is 0x1e from 2012. Probably won't make a
difference though but you never know.

Rick
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org