Page 1 of 1

yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 services

PostPosted: Sat Nov 05, 2011 9:30 pm
by afde
I'm running yavdr 0.4 with kernel 2.6.38
I've installed compiling linux-tbs-sources and followed instructions
when I try szap-s2 on hotbird RAI1 channel it works and it tells me FE HAS LOCK
the if I try to scan with w_scan it tells me signal ok but it goes filter time out
same issue if I use scan-s2 : pid timeout and non channel dumped.

any of you has a clue ?

Re: yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 service

PostPosted: Sun Nov 06, 2011 7:52 am
by recoder
Same problem here, I upgraded to Ubuntu 11.10, 3.0.0-12-generic, compiled the driver 111017, szap & co ... and can not get any lock on a channell :-(

Looking forward to some ideas ...

Cheers, Peter

Re: yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 service

PostPosted: Sun Nov 06, 2011 6:23 pm
by afde
Well ,
I'm really sad to read your post... so even upgrading to kernel
3.0 won't do...if we find another one with same issue,TBS should delete "linux" support
related to TBS 5890,
And If we don't find a solution I am willing to get a refund
because I bought this device mainly because of extensive linux support.
Anyway before that, I am going to give a try to Dvblast since
they mentioned a load of work on compatibility to this software
in the README_TBS_5890 in the driver package.

Cheers

Re: yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 service

PostPosted: Mon Nov 07, 2011 6:48 am
by szymonciow
Unfortunately all above is true.
There isn't a real support for this tuner under linux.
There aren't stable linux drivers, so TBS5980 is completely unusable.
Simon

Re: yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 service

PostPosted: Tue Nov 15, 2011 4:48 am
by jamf1
I have this problem as well (EDIT: I used V111017 on Ubuntu 11.10). Did anybody get the TBS5980 working on linux?

@recoder: Did it work on older Ubuntu/Kernel versions? If yes, on which versions did it work?

thx

Re: yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 service

PostPosted: Tue Nov 15, 2011 5:04 am
by szymonciow
Hmm ....
In kernel 2.6.38.7 with 110710 drivers I can say: yes it's working but... from time to time, between "freezes" :)
But seriously I can watch tv (tvheadend and xbmc) but some times I have to reload the drivers (rmmod, modprobe).
It's rather annoying for me...
Simon

Re: yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 service

PostPosted: Tue Nov 15, 2011 5:24 am
by jamf1
szymonciow Wrote:But seriously I can watch tv (tvheadend and xbmc) but some times I have to reload the drivers (rmmod, modprobe).


At least there is a way to get things working :-) Well, I will try it out with the versions you mentioned, hopefully it will work for me as well.

Thx for the quick answer.

Cheers,
Chris

Re: yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 service

PostPosted: Tue Nov 15, 2011 9:18 pm
by jamf1
Today new drivers are available: V111115

Let's see if they fixed this problem.

cheers,
Chris

Re: yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 service

PostPosted: Sun Nov 20, 2011 11:19 am
by afde
hi everybody
after contacting support i got able to make it work under linux:
it was a bug in the driver.
They sent me a patched file that should be available in the new driver release
(i have to recompile to confirm that).
Anyway thats how did it:
1) extracted the drivers from scratch
2) copied the patched file in the sources
# sudo cp tbs-qbox2ci.c linux-tbs-sources/linux/drivers/media/dvb/dvb-usb
3) recompiled the drivers

I scanned with w_scan and found services.

So as far as I can tell everything is working fine except for the cam but that's another story...

Re: yavdr 0.4 signal ok szap-s2 FE has lock w_scan 0 service

PostPosted: Sun Nov 20, 2011 4:36 pm
by jamf1
Hi,

For me scanning was already fixed with v111115 and kernel 3.0 but the cam isn't working stable with this version. I tried Irdeto Smit and Irdeto Smarcard. Both don't work stable and bring the message in dmesg "Invalid PC card inserted :(". But I will try the v111118, maybe it helps with the ci/cam problem.

cheers,
Chris