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

R. G. Newbury newbury at mandamus.org
Thu Jul 19 00:51:14 UTC 2012

On 07/18/2012 03:37 PM, Devin Heitmueller wrote:
> On Wed, Jul 18, 2012 at 3:01 PM, R. G. Newbury<newbury at mandamus.org>  wrote:
>> Which of course makes perfect and reasonable sense. The problem is how to
>> work around a situation where the invocation is not happening correctly. I
>> presume that there are a series of pokes and peeks, but they are internal to
>> the module code and not exposed. We really need to latch onto something
>> exposed, and unique.
>> And it may not exist.
>> And as you say, there are lots of hardware items which use different
>> chipsets internally, while declaring that they are twins to a different
>> model. Or they just report themselves wrongly anyway!
> Let me ask around and see if I can get my hands on a 2250.  The
> problem I ran into the last time somebody suggested that module
> loading order fixed it was actually a race condition related to udev
> calling v4l-id while the digital side of the board was still
> initializing.
> Can you send me the actual symptoms you encounter (including the dmesg
> output showing any error messages during initialization)?
> Devin

But of course. Tomorrow, or even later tonight.


More information about the mythtv-users mailing list