[mythtv-users] mythv 0.25 issues

jacek burghardt jaceksburghardt at gmail.com
Sun Apr 8 16:00:50 UTC 2012

Well i am tryining to get linup and it thinks for few moments and it stops.
It would be nice to get that fixed and ad an option that will give warning
whe user typed wrong user name password.
New issue I had scanner my hauppage cable card tunner and I can get live tv
2012-04-08 09:58:18.347013 E  TVRec(1): Failed to set channel to 4_1.
Reverting to kState_None
2012-04-08 09:58:18.347034 I  TVRec(1): Changing from WatchingLiveTV to None
2012-04-08 09:58:59.194471 E  DTVMux: ParseTuningParams -- Unknown tuner
2012-04-08 09:58:59.194501 E  DTVChan(20100ECA-1):
SetChannelByString(20_1): Failed to initialize multiplex options
2012-04-08 09:58:59.194509 E  TVRec(3): Failed to set channel to 20_1.
Reverting to kState_None
2012-04-08 09:59:18.534117 E  DTVMux: ParseTuningParams -- Unknown tuner
2012-04-08 09:59:18.534147 E  DTVChan(20100ECA-0): SetChannelByString(7_1):
Failed to initialize multiplex options
2012-04-08 09:59:18.534154 E  TVRec(1): Failed to set channel to 7_1.
Reverting to kState_None
I wonder is this becuase my cable card is not active yet

On Sun, Apr 8, 2012 at 9:47 AM, Scott & Nicole Harris
<snharris99 at live.com>wrote:

> So it is very strange that mythtv-setup does not create proper schema ?
>> On new setup I had start mythbackend in order to get proper database
>> config and then run mythtv-setup.
>> Another issue is that I can't get lineup from schedule direct at all
>> works fine with 0.24 fixes.
>> I have pfsense running with antivirus and squid. I wonder if anyone has
>> any idea on how I can fix that issue.
>> Upgrading from 0.24 fixes to 0.25 creates database error issue.
> I had the db error issues as well.  I had to start mythbackend from the
> command line to see what was going on then manually drop tables / columns
> one at a time as it complained about it and failed until it stopped
> complaining.  The problem is, if it fails part way through, but say has
> already added a new table or a new column to an existing table, then next
> time through, it isn't happy because things it's trying to do (again) have
> already been done.  All in all, I think there may need to be a much better
> use of "IF EXISTS"/ "IF NOT EXISTS" in the update scripts...though that's
> really a stab on my part.
> As far as the schedules direct, did you do a fresh installation or did you
> do a brand new channel scan that overwrote your old channels?  I had a
> similar issue when testing 0.25 on a fresh installation (i.e. not an
> upgrade of an existing 0.24 installation).  Turned out, my channels had no
> xmlids and therefore couldn't generate a proper schedule.
> ______________________________**_________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/**listinfo/mythtv-users<http://www.mythtv.org/mailman/listinfo/mythtv-users>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20120408/97ab4d62/attachment.html>

More information about the mythtv-users mailing list