[mythtv-users] OT: unreliable firmware load after cold boot

[R. G. Newbury]

On 07/18/2012 03:46 PM, Warpme wrote:
> On 7/18/12 7:58 PM, R. G. Newbury wrote:
>> On 07/18/2012 02:41 AM, phipps-hutton at sky.com wrote:
>>>
>>> Quoting Mike Perkins <mikep at randomtraveller.org.uk>:
>>>
>>>> On 17/07/12 21:34, R. G. Newbury wrote:
>>>>> It took a brute force ring-around to ensure that all three (in my
>>>>> case) were
>>>>> removed: that is: I did modprobe -r #3, modprobe -r #2, modprobe -r
>>>>> #1, modprobe
>>>>> -r #2, modprobe -r #3. modprobe -r #2. Then installed them in proper
>>>>> order and
>>>>> get a 'registered' or 'initialized' report.
>>>>>
>>>> Is this the kind of situation that calls for udev rules?
>>>
>>> No, the fix should be in the dependencies compiled into the modules so
>>> that modprobe #3 just works.
>>
>> Ahh, dreaming in technicolor are we??
>>
>> Would be nice but!
>>
>> A quick modinfo shows that none of the three lists any of the others
>> as a dependency, but my experimentation showed that they are all
>> needed and in a set order.
>> They are described as a 'driver' 'demodulator driver' and 'tuner
>> driver' each matching the chipset on the card.
>>
>> But I had completely forgotten about modinfo. I will have to turn on
>> some debugging. Mythtv's setup does not like this card and does not
>> set it up properly or does not 'see' it properly.
>> It tunes with azap and vlc handles it nicely, but myth does not....
>>
>> Geoff
>>
>>
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
> Indeed, mythtv-setup is another problem :-(
> No mater what I was trying, tuners on this card wasn't recognized.
> Infact other tuners also wasn't recognized. Problem seems to be somehow
> dependent on number of tuners in system, as in my cloned test system
> with only 2 tuners I was able to configure them).
> After hours of tries I was forced to do all capturecard, cardinput,
> diseqc_tree (including SCR trees) & inputgroups setup manually at sql
> level.
> Positive is that I have full view how my DVB subsystem is configured
> (monotonic tuners numbers, clear diseqc tree, etc) - but, being under
> time pressure (production system), I was little frustrated that
> down-time took 3h instead of 15min :-(


Could you be so kind as to email me the records in the various tables 
which relate explicitly to this tuner? If it will work with some pokes 
and prods, I'm up for some table bashing.

Geoff