TBSDTV Community Forum

i didn't request collecting logs during the build, installation and loading of the drivers, because no problems were expected there since no changes in those parts were made in the drivers - the changes made are executed after you run some application software and try to lock, not during load, when ...

Marco, i spent most of the time today investigating different tuner settings in Windows and Linux driver - i found one that seem relevant, because it affects frequencies lower than 190 MHz and both yours and that reported by Thomas are in that range. so, hopefully, that's what wrong, but if the test...

Marco, thank you for the test details and my first comment is actually to both Thomas and you - please, do not mistake signal statistics in percentage (as your TV sets do), which is meaningless compared to statistics in dB, dBm, AGC or even in 'raw' values from the hardware, which at least Linux dri...

please, look how to solve the problem here:

viewtopic.php?f=52&t=7631#p24903

the post there is for 6280, but it applies for 6284 too.

BTW, when you test in Windows, please, double check and make sure that modulation (QAM) value set in Windows is the same as in Linux, because the driver can't auto-detect that and it entirely depends on what the application software tells about the modulation. one another idea i have is that maybe d...

no problem, test when you have time - currently your testing environment is the best lead we have to solve the problem. so, let me explain - we're trying to understand what's going on, but the idea the NAS is related is that maybe it interference with 5680 on hardware level, i.e. it generates noise ...

hmm, the things are not completely fine - i mean on your 'czap' log the lock is lost from time to time and it's the same on dvblast log as you pointed out. however, at least there is some signal lock, no matter it's unstable compared to the NAS, which means the problem on the NAS is something differ...

that's actually quite good result, because it shows you have lock - what failed and caused "WARNING: filter timeout pid 0x0011" is the data transfer, which is initiated by 'scan' after lock is acquired - i guess that happened due to CAM inserted in the CI slot or something like that, becau...

Hi and thank you for preparing such testing environment - you made real good progress and i believe the few new issues you faced on PC are easily resolvable - here are my suggestions: a) in Linux "frequency X out of range" error message should be just error in your configuration file. so, ...

it's fixed for me now and i can post too. so, here is the picture of our test: http://thumbnails104.imagebam.com/24459/e6d2c1244582958.jpg so, please, anyone having such problem - contact us, we need someone to provide us PC with remote access to check on the real live signal. thank you.