2ride
09-05-2003, 01:48 AM
In a prior post Cali wrote said the following:
quote:Originally posted by kozmo21
What do you look for in the log files that shows a tuner could be bad?
key word is not COULD....There IS at aleast one bad tuenr
This tells the story
quote:
Cam[120]: Initialized css to 49
Jan 17 20:50:42 (none) CamManager[124]: CamManager : Main loop pid: 124
quote:
ApgLogFrequency( 0 sec )
Jan 17 20:50:10 (none) kernel: Finished creating ApgDriverFrameIter
Jan 17 20:50:10 (none) kernel: Using a smartSorter!
Jan 17 20:50:10 (none) kernel: Creating ApgReader
I have this same issue with a friends dsr6000 that he bought off ebay ( for over $300, incidentaly )
I am attempting to help him was hoping you could expound on the meaning of these log entries and exactly why they indicate a bad tuner.
As a followup, now that I am relatively certain a bad tuner is the culprit, is there anything I can do via software to disable the suspect tuner?
Any other suggestions?
Sell it to a repair guru?
Thanks in advance
quote:Originally posted by kozmo21
What do you look for in the log files that shows a tuner could be bad?
key word is not COULD....There IS at aleast one bad tuenr
This tells the story
quote:
Cam[120]: Initialized css to 49
Jan 17 20:50:42 (none) CamManager[124]: CamManager : Main loop pid: 124
quote:
ApgLogFrequency( 0 sec )
Jan 17 20:50:10 (none) kernel: Finished creating ApgDriverFrameIter
Jan 17 20:50:10 (none) kernel: Using a smartSorter!
Jan 17 20:50:10 (none) kernel: Creating ApgReader
I have this same issue with a friends dsr6000 that he bought off ebay ( for over $300, incidentaly )
I am attempting to help him was hoping you could expound on the meaning of these log entries and exactly why they indicate a bad tuner.
As a followup, now that I am relatively certain a bad tuner is the culprit, is there anything I can do via software to disable the suspect tuner?
Any other suggestions?
Sell it to a repair guru?
Thanks in advance