USB Cinergy HTC Stick not recognized after TBS5925 install

[stilmant]

Hello,

I'm using TBS 5925 on a dedicated server and it is working fine.
I now want to use one TBS 5925 on a laptop where is also connected a USB Cinergy HTC stick.

The linux flavor is

Code: Select All Code

Linux Lux1-Ops-Lilo20 3.8.0-29-generic #42-Ubuntu SMP Tue Aug 13 19:40:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

on this linux the USB Cinergy HTC stick is natively recognized.
But after compiling and installing TBS 5925, the USB Cinergy HTC stick is no more recognized, the only output from dmesg about it is

Code: Select All Code

[ 1370.640520] usb 2-1.4: new high-speed USB device number 6 using ehci-pci
[ 1370.734363] usb 2-1.4: New USB device found, idVendor=0ccd, idProduct=00b2
[ 1370.734371] usb 2-1.4: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[ 1370.734375] usb 2-1.4: Product: Cinergy_HTC_Stick
[ 1370.734379] usb 2-1.4: Manufacturer: TERRATEC
[ 1370.734383] usb 2-1.4: SerialNumber: 02?TERRATE
[ 1374.042705] usb 2-1.2: new high-speed USB device number 7 using ehci-pci
[ 1374.135240] usb 2-1.2: New USB device found, idVendor=734c, idProduct=5925
[ 1374.135249] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1374.135254] usb 2-1.2: Product: TBS-5925
[ 1374.135258] usb 2-1.2: Manufacturer: TBS-Tech
[ 1374.135261] usb 2-1.2: SerialNumber: 001
[ 1374.135665] dvb-usb: found a 'TBS 5925 DVB-S2 USB2.0' in cold state, will try to load a firmware
[ 1374.135672] dvb-usb: downloading firmware from file 'dvb-usb-tbsqbox-id5925.fw'
[ 1374.135675] tbs5925: start downloading TBS5925 firmware
[ 1374.254086] dvb-usb: found a 'TBS 5925 DVB-S2 USB2.0' in warm state.
[ 1374.254221] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 1374.254459] DVB: registering new adapter (TBS 5925 DVB-S2 USB2.0)
[ 1374.390481] dvb-usb: MAC address: 00:22:ab:c0:29:57
[ 1374.510938] tbs5925: TBS 5925 FE Attached.
[ 1374.510938]
[ 1374.511117] DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
[ 1374.511325] stb6100_attach: Attaching STB6100
[ 1374.511690] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/input/input20
[ 1374.511808] dvb-usb: schedule remote query interval to 250 msecs.
[ 1374.511815] dvb-usb: TBS 5925 DVB-S2 USB2.0 successfully initialized and connected.


to make and install the TBS5925 driver I done

Code: Select All Code

sudo apt-get install build-essential linux-headers-$(uname -r)
su -
[...]
tar xjvf ../linux-tbs-drivers.tar.bz2
cd linux-tbs-drivers/
./v4l/tbs-x86_64.sh
make
make install


after reboot, once I've seen that the USB Cinergy HTC Stick was no more recognized I do

Code: Select All Code

rm -rf /lib/modules/3.8.0-29-generic/kernel/drivers/media/
rm -rf /lib/modules/3.8.0-19-generic/kernel/drivers/media/
cd tbs/
make install


but this not helped

I missing something... can someone can drive me a bit here, please?
Should I explicitly compile something for the Cinergy stick from the STB source tree?

Thanks

[stilmant]

Update:
USB Cinergy HTC stick uses em28xx module
I suspect path to that module the possible source of issue:

> the legacy installed Ubuntu path is:
/lib/modules/3.8.0-29-generic/kernel/drivers/media/usb/em28xx (notice usb/em28xx)

> the installed path using TBS sources compile 'make install' is:
/lib/modules/3.8.0-29-generic/kernel/drivers/media/video/em28xx (now video/em28xx)

Should I call a specific command to update the system about that new Path? (not sure if this is the reason however.)

[updatelee]

its been mentioned how lots before

sudo rm -R /lib/modules/{uname -a}/kernel/drivers/media
sudo make install
sudo reboot

UDL

[stilmant]

Hi, updatelee

Do you see in my initial post that I called that command?

(note: it is recommended by TBS to be root so I don't need to use 'sudo')

I will redo it however...

[cody]

it seems TBS Linux driver package is missing support for that Cinergy HTC Stick and the way that to be solved is to patch TBS Linux driver package and add that way support for Cinergy HTC Stick to it. so, when install it both drivers will be installed (for 5925 and Cinergy HTC Stick) and not like at the moment installing one of the drivers removes the other.

so, it seems the necessary patches are quite simple:

https://linuxtv.org/patch/8446/

as well here is another patch that refines the above:

http://www.spinics.net/lists/linux-media/msg48863.html

if it's hard for you to apply yourself those patches to TBS Linux driver package we can do it for you and provide you with test TBS Linux driver package with those patches included. in any case the above patches are very small, i.e. just few lines and thus what's missing currently in TBS Linux driver package should be quite small.

[stilmant]

Thank you for the quick feedback.

I've patched from both of your direct links. Device is loaded. (I've not tested its tuning capabilities however)

From this one
http://www.spinics.net/lists/linux-media/msg48863.html
there is some Follow-Ups:
http://www.spinics.net/lists/linux-media/msg48861.html

I would need to patch it as well, I guess. I've not done it yet.
From there I wonder if some other patch exist since the kernel source tree you use?

I would appreciate if you provide me with a test TBS Linux driver package with those patches included. I guess you will include those patch in future coming drivers package too?

I can understand you use a specific kernel sources version for your drivers release, can you please provide the version? will you merge with more recent Linux kernel in future? Have you a road-map?

Many thanks.

[cody]

you can always compare the source code of the involved drivers for your device, e.g. 'em28xx' and with more recent V4L tree like the one from kernel 3.8 you were using and evaluate which changes are just cosmetic due for example to change in V4L infrastructure or bring something new. most changes that happen are really just cosmetic and actual not bug fixes and those changes are to reflect extensions in V4L infrastructure like new version of the frontend API. so, those doesn't give you anything new actually for particular device. however, some new hardware settings like initialization values and so on can be important. we can't be very useful for 3rd party devices, because we don't have them to test and so that's why we include patches for them only per request and if those patches are tested by someone having such device. V4L tree in TBS Linux driver package is span from the original V4L tree and we're concern to provide proper work of our own devices, i.e. all changes we made in that V4L tree are to server our own purpose and were not focused on the other devices.

[stilmant]

Thanks for the feedback,

I don't know about the dependencies of your modules and the legacy modules but is it possible after a build of your drivers to copy only needed TBS modules in /lib/modules/{uname -a}/kernel/drivers/media ?
Is there some common modules adapted for your drivers that would prevent that approach?

Like that the support of your drivers would not break Linux native device supports.

[updatelee]

Thanks for the feedback,

I don't know about the dependencies of your modules and the legacy modules but is it possible after a build of your drivers to copy only needed TBS modules in /lib/modules/{uname -a}/kernel/drivers/media ?
Is there some common modules adapted for your drivers that would prevent that approach?

Like that the support of your drivers would not break Linux native device supports.

Thats usually a recipe for disaster.

If both your kernel and the TBS modules are compiled with exactly the same options and the kernel is pretty close to the TBS tree's version then maybe just maybe that would work, but I still wouldnt recommend it.

UDL