On Sat, March 10, 2007 8:56 am, Lan Barnes wrote:
>
> On Sat, March 10, 2007 8:19 am, Gus Wirth wrote:
>> Lan Barnes wrote:
>>> On Fri, March 9, 2007 6:43 pm, Lan Barnes wrote:
>>>> MythTV was working beautifully, so we went from Basic Cable to
>>>> Extended
>>>> (no box, 2 - 99). I closed the front end, did MythSetup, and rescanned
>>>> the
>>>> channels (or thought I did). The scan looked feeb and scanned from 4
>>>> to
>>>> 13.
>>>>
>>>> Didn't make any sense. As I exited, it said to run mythfilldb, so I
>>>> did
>>>> as
>>>> user mythtv. Then when I went into the channel guide, it was all
>>>> screwed
>>>> up. Has 13 as KPBS and 11 as KUSI.
>>>>
>>>> I reran mythfilldb as root (superstitious) with no change.
>>>>
>>>> What have I done to myself?
>>>>
>>>> Two real questions:
>>>>
>>>> 1. how do I scan the real channels
>>>>
>>>> 2. how do I fix the database
>>>>
>>>
>>> I'm beginning to think I'd do best to
>>>
>>> 1. exit myth
>>>
>>> 2. re-run the sql script to initialize the data base
>>>
>>> 3. set up again.
>>>
>>> If you Myth gurus (Gus, Josh, anyone) agree, remind me of the sql
>>> script's
>>> name and I'm off to the races.
>>>
>>> Fortunately, nothing important is recorded ... yet.
>>
>> Did you go to the Zap2It site <http://labs.zap2it.com> and change your
>> cable lineup description to reflect the fact you are now on extended
>> cable?
>>
>
> No! I'll do it
>
>> Also, when you re-initialize the DB you need to make sure that
>> mythbackend is NOT running.
>>
>
> Ah ha! Obvious, and yet I missed in. How does one exit the back end? I'm
> guessing service stop mythtv or whatever.
>
>> Gus
>>
>
> ... the guy who knows. Thanks. More to try.
>
> BTW, the Cox guy is going to come in the house. Should I hide the Myth
> box?
>
>

Reconfiguring my zap2it, deleting and reentering the video card, and
re-running mythdatabasefill (as root) with mythbackend stopped _seems_ to
have filled the database anew. The mfdb ran for a much longer time,
indicating to me that it was downloading lots more channels.

However, I can't confirm this because, after a reboot to get a clean image
(_so_ M$, but what I do when I'm ignorant), the front end seems to work
but when I try to look at the schedule in set recordings, the front end
terminates itself w/o any warning or message. AFAICT from ps ax, no
detritus is left behind, but I could have a poison file somewhere.

Any hints? I really don't want to reinstall from the top, but I know that
would work. But again, _so_ M$. I have my pride.

-- 
Lan Barnes

SCM Analyst              Linux Guy
Tcl/Tk Enthusiast        Biodiesel Brewer


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to