[linux-dvb] Gene's pcHDTV 3000 analog problem

Michael Krufky mkrufky at m1k.net
Tue Nov 29 19:45:55 CET 2005


Gene Heskett wrote:

>On Tuesday 29 November 2005 13:12, Michael Krufky wrote:
>  
>
>>Michael Krufky wrote:
>>    
>>
>>>My card was working fine for a good long time, but ever since about 2
>>>months ago, the analog tuner no longer works.  ONLY the ATSC digital
>>>tuner is working.  The tuner does NOT include a tda9887, AFAIK, and I
>>>have also tested in windows.  Regardless of whether I am using Linux
>>>or Windows, I can only view an ATSC digital stream, NTSC analog no
>>>longer works at all.  Both used to work in both OS's.
>>>
>>>AFAIK, this is a physical hardware problem, and has nothing to do
>>>with any bad coding.  For the life of me, I cannot figure out what
>>>went wrong.
>>>
>>>Maybe someone might be able to tell us what factors can burn out a
>>>hybrid tuner's analog capabilities, and leave digital tuning
>>>capabilities intact.
>>>
>>>Maybe the Thomson DDT 761x tuners are faulty?
>>>      
>>>
>>CityK wrote:
>>    
>>
>>>Michael Krufky wrote:
>>>      
>>>
>>>>CityK wrote:
>>>>        
>>>>
>>>>>a) Is there any chance that your loss of analog might be in any way
>>>>>related to this:
>>>>>http://www.linuxtv.org/pipermail/linux-dvb/2005-July/003536.html ?
>>>>>I'm not sure what Mac eventually introduced, or whether or not it
>>>>>would possibly have affected your card.
>>>>>          
>>>>>
>>>>No... Mac was talking about ways to switch RF inputs on the
>>>>FusionHDTV3 Gold-Q model, which used a microtune tuner with two RF
>>>>inputs.  My tuner only has one input, and it has always worked with
>>>>Mac's callback implementation.  Kirk has used a similar method to
>>>>implement this in nxt200x.
>>>>        
>>>>
>>>Yep, that is very clear.  I'm just throwing out ideas ... Recall that
>>>you wrote:
>>>
>>>/ I use the same rf input to use
>>>/>/ OTA VSB as I use for cable QAM.  I think that if you
>>>/>/ altered the frontend like this, it could break the
>>>/>/ usability on my board./
>>>
>>>I was just wondering if there was (a long shot) connection between
>>>your analog going dead and this.....I was thinking along the lines of
>>>a bit becoming "stuck" ... which reminds me, was there not discussion
>>>about something being stuck, and requiring a switch into a Windows
>>>environment to unstick the bit, early in the development of the
>>>Fusion drivers?
>>>      
>>>
>>I appreciate the ideas, but unfortunately the rf selection isn't the
>>culprit here - Mac implemented this by using a callback that IS defined
>>for the Gold-Q card, but NOT defined for the Gold-T board.... BTW, if
>>there are any other boards that use lgdt330[2,3] , they can also use
>>this callback function to change RF inputs.
>>
>>..and about that "stuck" bit, being fixed only by a cold boot -- That
>>was during development of the FusionHDTV5 Gold driver... completely
>>different animal, using LG DT3303 (instead of DT3302), and using
>>LG-TDVS-H062F, containing TUA6034 tuner (and tda9887), rather than the
>>Thomson DDT 7611 / [Temic/Microtune] 4042 tuner.
>>
>>IIRC, we worked that out in the end by programming the tda9887 chip.
>>
>>    
>>
>>>>>b) What analog demodulator is used in the Fusion 3s
>>>>>(18ac:d800,18ac:d810,18ac:d820) ?  What did Mac use? (he didn't
>>>>>mention:
>>>>>http://www.linuxtv.org/mailinglists/linux-dvb/2004/08-2004/msg00074
>>>>>.html)
>>>>>          
>>>>>
>>>>Wow... Very interesting thread, although unrelated to this topic.
>>>>        
>>>>
>>>I hummed and hawed about whether or not to start a new topic ... but
>>>as this particular discussion (dead analog in Fusion 3) was
>>>introduced in this thread, I thought I would continue it
>>>here....Nonetheless, thank you for adjusting the subject heading to
>>>more accurately reflect the topic.
>>>      
>>>
>>You did nothing wrong... I was only trying to say that I didnt see the
>>relevance -- Thanks for explaining, now I see what you are saying.  I
>>was by NO MEANS criticising you for digressing from the thread topic.
>>Sorry for the misunderstanding.
>>
>>    
>>
>>>>Wow... Very interesting thread, although unrelated to this topic. In
>>>>that thread, Mac was discussing DVB API changes needed to support
>>>>the American standards.
>>>>        
>>>>
>>>Yes, I know what Mac was discussing.  Perhaps I didn't articulate my
>>>points to question b) very well.  Anyways, what I was trying to
>>>convey was:
>>>a) That was the first post Mac made regarding the Fusion 3, in
>>>particular, its analog side, and he didn't mention what analog
>>>demodulator it was using....In fact, I don't recall him ever
>>>mentioning what IC is employed.
>>>b) Discovering what analog demodulation IC is used might greatly aid
>>>in the discovery of why the analog side of your card is no longer
>>>functioning...and whether or not it can be restored (hopefully).
>>>      
>>>
>>I agree.  Thanks for explaining this, I had missed your point,
>>originally.  How can I find out what IC is employed?  (I have a feeling
>>that you're going to tell me to write to DViCO -- They always reply to
>>my mails, but they take approx 2 months each time :-(  )
>>
>>I'll take another look at the Thomson DDT 761x datasheet ... maybe
>>there's some info about it there.
>>
>>/me hopes!
>>    
>>
>[...]
>
>/me too.  And I just rebuilt 2.6.14 w/o the cvs, did a cold boot, and
>it works just fine except the modprobe stage was silent at the cli. 
>But my logs are being spammed with:
>
>Nov 29 13:24:49 coyote kernel: CORE IOCTL: 0xc02c5638
>Nov 29 13:24:49 coyote kernel: CORE IOCTL: 0xc054561d
>Nov 29 13:24:49 coyote last message repeated 2 times
>Nov 29 13:24:49 coyote kernel: CORE IOCTL: 0xc008561c
>Nov 29 13:24:49 coyote kernel: CORE IOCTL: 0xc0445624
>Nov 29 13:24:49 coyote kernel: CORE IOCTL: 0xc008561c
>Nov 29 13:24:49 coyote kernel: CORE IOCTL: 0xc054561d
>Nov 29 13:24:53 coyote last message repeated 131 times
>Nov 29 13:24:53 coyote kernel: CORE IOCTL: 0xc008561c
>
>
>My hard drives have been power cycled more times in the last few days
>playing with this than at any time in their history since I have a BIG
>ups.
>
>So I think I'm back to 2.6.14.3 for a while. Lemme know if and when
>there is something else to test.  Right now I'm vacuuming up water in
>the basement for the first time in years, it rained HARD here earlier.
>
Gene-

There IS something more to test, unless I missed an email from you....

...and it's going to be very hard for people to follow your problem... 
Please stick with your original thread to discuss your particular problem.

What happens when you install v4l-dvb cvs on top of 2.6.14.y ?

(Gene's card uses Thomson DDT 7610 - we need to figure out what analog 
demod is in play, here.)

-Mike



More information about the linux-dvb mailing list