[mythtv-users] Problem in the code or with the tuners

Greg Oliver oliver.greg at gmail.com
Wed Sep 29 14:02:51 UTC 2010


On Wed, Sep 29, 2010 at 6:38 AM, David Whyte <david.whyte at gmail.com> wrote:
> Hi,
>
> I have done some Googling, but it seems that other people seeing the
> same error/log messages are for many random reasons.
>
> Running 0.23.1 on mythbuntu 10.04.
>
> I have two K-World PCI Dual Tuner DVB-T cards in my BE (running
> mythbuntu 10.04).  While they are haven't done too much damage to the
> GAF of my under-used myth system, I can't trust them...I know they are
> going to cause me serious pain in the future.  The newer drivers seem
> flakey and so I am using the drivers from mythbuntu 9.10.  I still
> seem to have issues where they are always found to be in a warm state
> at boot and in the past I found one tuner would die until after a
> reboot.  I can't do machine restarts, since this seems to put them in
> a funny state. I always turn my server off, disconnect the power and
> try to power up the machine before actually starting it back up.
>
> I felt some serious pain tonight from the GF!!!
>
> One of my GF's recordings over-ran and we had been watching it in
> almost real-time when the playback ended so I quickly ducked into Live
> TV to catch the end of the show.  Unfortunately, I got into a problem
> I noticed the other day, where the tuner seems to take forever to lock
> but only in live TV.  This led to the FE seeming to crash.
>
> My BE logs show the following:
>
> errors)
> 2010-09-29 20:33:15.229 MythSocket(8e2c168:44): writeStringList:
> Error, No data written on writeBlock (915
> errors)
> 2010-09-29 20:33:16.246 MythSocket(8e2c168:44): writeStringList:
> Error, No data written on writeBlock (910 errors)
> 2010-09-29 20:33:17.262 MythSocket(8e2c168:44): writeStringList:
> Error, No data written on writeBlock (907 errors)
> 2010-09-29 20:33:17.279 ProgramInfo(): Updated pathname '':'' ->
> '2344_20100929203240.mpg'
> 2010-09-29 20:33:18.287 MythSocket(8e2c168:44): writeStringList:
> Error, No data written on writeBlock (907 errors)
> 2010-09-29 20:33:18.303 MainServer::ANN Playback
> 2010-09-29 20:33:18.310 adding: mythfe-dayroom as a client (events: 0)
> 2010-09-29 20:33:18.303 MainServer::ANN Playback
> 2010-09-29 20:33:18.327 adding: mythfe-dayroom as a client (events: 0)
> 2010-09-29 20:33:18.335 MainServer, Warning: Unknown socket closing
> MythSocket(0x8cfb898)
> 2010-09-29 20:33:18.303 MainServer, Warning: Unknown socket closing
> MythSocket(0xffffffff9d042eb0)
> 2010-09-29 20:33:18.352 MainServer, Warning: Unknown socket closing
> MythSocket(0xffffffff9d042eb0)
> 2010-09-29 20:33:18.319 MainServer, Warning: Unknown socket closing
> MythSocket(0xffffffff9d00e500)
> 2010-09-29 20:33:18.303 MainServer, Warning: Unknown socket closing
> MythSocket(0xffffffffa1501648)
> 2010-09-29 20:33:18.303 MainServer::HandleAnnounce FileTransfer
> 2010-09-29 20:33:18.385 adding: mythfe-dayroom as a remote file transfer
> 2010-09-29 20:33:18.303 Waiting for a process request thread..
> 2010-09-29 20:33:18.361 MythSocket(ffffffff9d042eb0:-1):
> writeStringList: Error, socket went unconnected.
>                        We wrote 0 of 21 bytes with 1 errors
> 2010-09-29 20:33:18.370 MythSocket(ffffffff9d00e500:-1):
> writeStringList: Error, socket went unconnected.
>                        We wrote 0 of 10 bytes with 1 errors
> 2010-09-29 20:33:18.377 MainServer, Warning: Unknown socket closing
> MythSocket(0xffffffffa1501648)
> 2010-09-29 20:33:18.345 MythSocket(8cfb898:-1): writeStringList:
> Error, socket went unconnected.
>                        We wrote 0 of 10 bytes with 1 errors
>
>
> I was able to go to mythweb and schedule a recording, which was
> successful and we watched the end of the show.  I then tried watching
> Live TV and got to the point where the FE appeared to crash again!
>
> Is the above problem something that the cr at ppy tuners is causing or is
> it a software bug?  I am at the point where I think I might drop some
> dollars on a DVB-T HDHomeRun since they get excellent reviews from
> anyone that has gone near them, and just allocate them to Live TV
> viewing only, since this is where the problems seems to come from.
> (My GF channel surfs, but there is no antenna point near where the TV
> is currently located, hence the dependency on Live TV).
>
> Any feedback would be appreciated.

A cheaper workaround is to start recording and immediately go to
watching it rather than livetv..  I know it is cumbersome, but it
works.  I would recommend a HDHR though..  They are just *easy*


More information about the mythtv-users mailing list