Cannot tune to any DVB-C channels

[NKognito]

I bought TBS 6205 few weeks ago and I so far I haven't been able to get the card working properly under Ubuntu 15.10. I believe that I have managed to compile and install the drivers ok as the dmesg lists for each tuner something like this:

[ 11.079128] TurboSight TBS 6205 Frontend:
tbs6205fe - software version is 2.0.0.0
[ 11.220102] TurboSight TBS 6205 Frontend:
tbs6205fe - Successfully Initialized
[ 11.221267] TurboSight TBS6205 DVB-T2 card adapter3 MAC=ff:ff:ff:ff:ff:ff
[ 11.221269] DVB: registering adapter 3 frontend 0 (TurboSight TBS 6205 DVBC frontend)...

However, when I try to tune or scan for channels, nothing seems to happen. I have primarily tried with Kaffeine, but also with command line tools. Kaffeine's TV channel scan lists 80% signal ratio and 0% SNR, so I assume the card gets some signal from the antenna cable. The DVB-C signal comes from Elisa's cable TV service in Helsinki and for Kaffeine I use a w_scan generated tuning data that used to work fine with my earlier DVB-C card (Terratec Cinergy) until that card decided to stop working. And Samsung Bluray/DVB recorder box that feeds the picture to my old DVB-T only TV set works with this signal fine too.

Kernel version is currently 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

And lspci report following information on the DVB card:

Code: Select All Code

02:00.0 Multimedia controller: Device 544d:6178
        Subsystem: Device 6205:0001
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 16
        Region 0: Memory at f7500000 (32-bit, non-prefetchable) [size=256K]
        Capabilities: [50] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [70] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [90] Express (v1) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s, Exit Latency L0s unlimited, L1 <1us
                        ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [100 v1] Device Serial Number 00-00-00-00-00-00-00-00
        Kernel driver in use: TBS PCIE


[steven]

Hi

You are using the DVB-T driver please have a try install DVB-C driver like this:

///DVBC +DVBS
rm -rf /lib/modules/${version}/kernel/drivers/media

the version you can get with
uname -a

like this:
# uname -a
Linux skyip 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:09:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
# ls /lib/modules/3.19.0-
3.19.0-25-generic/ 3.19.0-30-generic/
# rm -rf /lib/modules/3.19.0-30-generic/driver/media

then
1. tar jxvf linux-tbs-drivers_xxx.tar.bz2
2. cd linux-tbs-drivers
3 ./v4l/tbs-x86_64.sh
4 ./v4l/tbs-dvbc-x86_64.sh

5. make -j4

make install
restart

Thanks

Kind Regards

steven

[NKognito]

No, I don't think that I'm using DVB-T driver: look at the last line of dmesg output, where it says "DVBC". In first time or so, I did accidentally compile the drivers in DVB-T mode, so I think I know the (small) difference by now.

I have done all those driver building steps several times (apart from deleting old media drivers directory and using -j4 option in make).

[tarik341]

make -C /tmp/linux-tbs-drivers/v4l
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird betreten
No version yet, using 3.19.0-25-generic
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird verlassen
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird betreten
scripts/make_makefile.pl
./scripts/make_kconfig.pl /lib/modules/3.19.0-25-generic/build /lib/modules/3.19.0-25-generic/build
Updating/Creating .config
Preparing to compile for kernel version 3.19.0
Preparing to compile for kernel version 3.19.0

***WARNING:*** You do not have the full kernel sources installed.
This does not prevent you from building the v4l-dvb tree if you have the
kernel headers, but the full kernel source may be required in order to use
make menuconfig / xconfig / qconfig.

If you are experiencing problems building the v4l-dvb tree, please try
building against a vanilla kernel before reporting a bug.

Vanilla kernels are available at http://kernel.org.
On most distros, this will compile a newly downloaded kernel:

cp /boot/config-`uname -r` <your kernel dir>/.config
cd <your kernel dir>
make all modules_install install

Please see your distro's web site for instructions to build a new kernel.


***WARNING:*** You do not have the full kernel sources installed.
This does not prevent you from building the v4l-dvb tree if you have the
kernel headers, but the full kernel source may be required in order to use
make menuconfig / xconfig / qconfig.

If you are experiencing problems building the v4l-dvb tree, please try
building against a vanilla kernel before reporting a bug.

Vanilla kernels are available at http://kernel.org.
On most distros, this will compile a newly downloaded kernel:

cp /boot/config-`uname -r` <your kernel dir>/.config
cd <your kernel dir>
make all modules_install install

Please see your distro's web site for instructions to build a new kernel.

Created default (all yes) .config file
./scripts/make_myconfig.pl
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird verlassen
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird betreten
perl scripts/make_config_compat.pl /lib/modules/3.19.0-25-generic/build ./.myconfig ./config-compat.h
make -C firmware prep
creating symbolic links...
make[2]: Entering directory `/tmp/linux-tbs-drivers/v4l/firmware'
make[2]: Leaving directory `/tmp/linux-tbs-drivers/v4l/firmware'
make -C firmware
make[2]: Entering directory `/tmp/linux-tbs-drivers/v4l/firmware'
CC ihex2fw
make[2]: gcc: Command not found
make[2]: *** [ihex2fw] Error 127
make[2]: Leaving directory `/tmp/linux-tbs-drivers/v4l/firmware'
make[1]: *** [firmware] Fehler 2
make[1]: *** Auf noch nicht beendete Prozesse wird gewartet …
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird verlassen
make: *** [all] Fehler 2
root@ubuntu:/tmp/linux-tbs-drivers#

[tarik341]

now this fehler

root@ubuntu:/tmp/linux-tbs-drivers# make -j4
make -C /tmp/linux-tbs-drivers/v4l
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird betreten
make -C firmware prep
creating symbolic links...
make[2]: Entering directory `/tmp/linux-tbs-drivers/v4l/firmware'
make[2]: Leaving directory `/tmp/linux-tbs-drivers/v4l/firmware'
make -C firmware
make[2]: Entering directory `/tmp/linux-tbs-drivers/v4l/firmware'
CC ihex2fw
make[2]: gcc: Command not found
make[2]: *** [ihex2fw] Error 127
make[2]: Leaving directory `/tmp/linux-tbs-drivers/v4l/firmware'
make[1]: *** [firmware] Fehler 2
make[1]: *** Auf noch nicht beendete Prozesse wird gewartet …
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird verlassen
make: *** [all] Fehler 2
root@ubuntu:/tmp/linux-tbs-drivers#

[andersh]

I bought TBS 6205 few weeks ago and I so far I haven't been able to get the card working properly under Ubuntu 15.10. I believe that I have managed to compile and install the drivers ok as the dmesg lists for each tuner something like this:

I have the card working properly on Ubuntu 15.10 with DVB-C (apart from the low signal levels reported - which I don't think is a Ubuntu issue), so there is something that went wrong with your compile and install.

As far as I can see from my .bash_history I did the following on a clean Ubuntu 15.10 server install:

Code: Select All Code

sudo apt-get install build-essential
sudo apt-get install linux-headers-generic
sudo apt-get install unp
unp linux-tbs-drivers.tar.bz2
cd linux-tbs-drivers/
find -type d -exec chmod 755 \{\} \;
./v4l/tbs-x86_64.sh
./v4l/tbs-dvbc-x86_64.sh
make -j4
sudo mv /lib/modules/$(uname -r)/kernel/drivers/media ~/media.bak
sudo make install


Then I installed tvheadend and was up and running in an instant.

[steven]

now this fehler

root@ubuntu:/tmp/linux-tbs-drivers# make -j4
make -C /tmp/linux-tbs-drivers/v4l
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird betreten
make -C firmware prep
creating symbolic links...
make[2]: Entering directory `/tmp/linux-tbs-drivers/v4l/firmware'
make[2]: Leaving directory `/tmp/linux-tbs-drivers/v4l/firmware'
make -C firmware
make[2]: Entering directory `/tmp/linux-tbs-drivers/v4l/firmware'
CC ihex2fw
make[2]: gcc: Command not found
make[2]: *** [ihex2fw] Error 127
make[2]: Leaving directory `/tmp/linux-tbs-drivers/v4l/firmware'
make[1]: *** [firmware] Fehler 2
make[1]: *** Auf noch nicht beendete Prozesse wird gewartet …
make[1]: Verzeichnis »/tmp/linux-tbs-drivers/v4l« wird verlassen
make: *** [all] Fehler 2
root@ubuntu:/tmp/linux-tbs-drivers#

is "CC Command not found". so, it seems like "gcc" (GNU C Compiler) is
not installed in your system, that's why i suggest to do:

# sudo apt-get update
# sudo apt-get install gcc
# sudo apt-get install g++

[NKognito]

Ok, I finally made some progress with this problem and by having a quite wild idea: since the TBS6205 card has two RF interfaces I decided to swap the antenna cable to the other interface (labeled "RF OUT") and surprisingly now I finally can get some sort of signal in. Sadly the signal quality seems quite bad, but that might be caused by my cabling and sorting out this kind of issues is much easier than situation where nothing seems to happen when I try to tune to DVB channels.

So, this was a physical hardware problem: the labels next to RF interfaces were mislabeled.