TBS6982SE - card or driver problem?
Posted: Fri Apr 29, 2016 2:09 am
Hi,
I have been having a bit of difficulty scanning known transponders on AMC21 with both scan-s2 and w_scan using a new install of Debian Stretch x86_64, and as V4l modules required a some headers not in Debian, a newly compiled vanilla kernel (4.4.7 originally, now with 4.4.8). The tuner is on loan from a friend and while it seemed to work in windows it did not pick up all the transponders. A MicroHD receiver does work well on the feed reporting signal strength at 90% and good quality on all desired FTA transponders.
Frequencies from Lyngsat (or the MicroHD scanning) did not match with what the card is reporting using a 4.4.7 kernel and the open source drivers. I thought this was potentially was an open source driver issue, so tried with the TBS 160405 drivers on the 4.4.7 kernel with no success.
I then went back to TBS drivers on freshly compiled and installed 4.4.8 kernel again but again with no success. I then removed the TBS modules and installed the open source drivers. Both scan-s2 and w_scan report services on the frequencies which do not correspond to those which should be found. For example this w_scan vdr result is for signals that should have been found at 12180 but are found at 11186.
1. Is it possible that the card is not working as it should? I have read elsewhere that frequencies are a bit off when scanned with different cards, but this seems a bit more than I would expect?
2. The frequency offset does not seem to be a constant, as trying for the other wanted AMC21 transponders with that offset still has not been successful. Is this frequency offset a driver issue?
3. Are the TBS 160405 drivers compatible with a 4.4.7 or 4.4.8 64-bit kernel?
Any suggestions would be appreciated.
Thanks
Wayne
PS With those with multiple kernels getting wrong symbol versions messages in the logs - use
I have been having a bit of difficulty scanning known transponders on AMC21 with both scan-s2 and w_scan using a new install of Debian Stretch x86_64, and as V4l modules required a some headers not in Debian, a newly compiled vanilla kernel (4.4.7 originally, now with 4.4.8). The tuner is on loan from a friend and while it seemed to work in windows it did not pick up all the transponders. A MicroHD receiver does work well on the feed reporting signal strength at 90% and good quality on all desired FTA transponders.
Frequencies from Lyngsat (or the MicroHD scanning) did not match with what the card is reporting using a 4.4.7 kernel and the open source drivers. I thought this was potentially was an open source driver issue, so tried with the TBS 160405 drivers on the 4.4.7 kernel with no success.
I then went back to TBS drivers on freshly compiled and installed 4.4.8 kernel again but again with no success. I then removed the TBS modules and installed the open source drivers. Both scan-s2 and w_scan report services on the frequencies which do not correspond to those which should be found. For example this w_scan vdr result is for signals that should have been found at 12180 but are found at 11186.
- Code: Select All Code
HD01;PBS:11186:vC56M2O35S1:??:22000:49=27:0;52,53,54:0:0:3:1:1:0
HD02;PBS:11186:vC56M2O35S1:??:22000:65=27:0;68,69,70:0:0:4:1:1:0
HD03;PBS:11186:vC56M2O35S1:??:22000:81=27:0;84,85,86:0:0:5:1:1:0
SD01;PBS:11186:vC56M2O35S1:??:22000:177=27:0;180,181,182,183:0:0:11:1:1:0
SD02 Create;PBS:11186:vC56M2O35S1:??:22000:193=27:0;196,197,198:0:0:12:1:1:0
SD03 VME;PBS:11186:vC56M2O35S1:??:22000:209=27:0;212,213,214:0:0:13:1:1:0
FNX SD08;PBS:11186:vC56M2O35S1:??:22000:241=27:244@3:0:0:15:1:1:0
SD04 World;PBS:11186:vC56M2O35S1:??:22000:225=27:0;228,229,230:0:0:14:1:1:0
Done, scan time: 05:30.190
1. Is it possible that the card is not working as it should? I have read elsewhere that frequencies are a bit off when scanned with different cards, but this seems a bit more than I would expect?
2. The frequency offset does not seem to be a constant, as trying for the other wanted AMC21 transponders with that offset still has not been successful. Is this frequency offset a driver issue?
3. Are the TBS 160405 drivers compatible with a 4.4.7 or 4.4.8 64-bit kernel?
Any suggestions would be appreciated.
Thanks
Wayne
PS With those with multiple kernels getting wrong symbol versions messages in the logs - use
- Code: Select All Code
$locate media.ko