Sundtek Support Forum
English => Sundtek MediaTV Pro (Europe) => Thema gestartet von: erdah am Oktober 11, 2009, 07:29:35 Nachmittag
-
Hi!
I'm on Karmic Koala with the latest drivers (091009). When running:
w_scan -f c -c SE > channels.conf.dvbc
I'm getting this error message:
$ sudo w_scan -f c -c SE > channels.conf.dvbc
w_scan version 20090808 (compiled for DVB API 5.0)
using settings for SWEDEN
DVB cable
DVB-C
frontend_type DVB-C, channellist 7
output format vdr-1.6
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 -> DVB-C "Sundtek DVB-C": good :-)
Using DVB-C frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 0.0
frontend Sundtek DVB-C supports
INVERSION_AUTO
QAM_AUTO not supported, trying QAM_64 QAM_256.
FEC_AUTO not supported, trying FEC_NONE.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
searching QAM64...
73000: sr6900 (time: 00:01) set_frontend:1690: FATAL: unsupported DVB API Version 0.0
-
Our DVB API was a little bit out of sync with the official DVB API, it's now up to date and the version retrieval is now also supported. We added the update to 091009, you might download and install the driver again and it will work.
-
I have this problem too, with the latest drivers.
sudo w_scan -f c -c SE > channels.conf.dvbc
w_scan version 20090808 (compiled for DVB API 5.0)
using settings for SWEDEN
DVB cable
DVB-C
frontend_type DVB-C, channellist 7
output format vdr-1.6
Info: using DVB adapter auto detection.
/dev/dvb/adapter0/frontend0 -> DVB-C "Sundtek DVB-C": good :-)
Using DVB-C frontend (adapter /dev/dvb/adapter0/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.1
frontend Sundtek DVB-C supports
INVERSION_AUTO
QAM_AUTO not supported, trying QAM_64 QAM_256.
FEC_AUTO
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
searching QAM64...
73000: sr6900 (time: 00:00) set_frontend:1690: FATAL: unsupported DVB API Version 5.1
I can't add any channels in Tvheadend.
I only get the following result on channels that should be free (in this case TV5 Monde):
Apr 07 17:18:57 serviceprobe: TV5 Monde: skipped: Sensed input from hardware but nothing for the service
-
your Distribution is not correctly installed (or at least there's a bug with the dvb headers).
you can try to lower the API Version with following command:
/opt/bin/mediaclient --setver=5.0
and retry with w_scan, w_scan was packaged for the DVB API version 5.0, but our driver by default provides API support for the DVB API 5.1, it tries to detect lower versions which works with correct systems, for incorrect systems it can be set manually
what distribution do you use?
In case of tvheadend you can also ask in the tvheadend IRC channel on freenode.net where tvheadend developers and users give support to other tvheadend users we are watching it and try to help out too.
-
I installed XBMC-Live 9.11, so it should be Ubuntu 9.10, I guess.
What would I lose on lowering the API version?
Any suggestions on how to fix my system, rather than trying to go around my problem? I kind of dislike those solutions. :)
I issued the command you suggested, and w-scan scans, however, Tvheadend now gives me the following:
Apr 07 18:55:01 serviceprobe: TV5 Monde: checking...
Apr 07 18:55:01 dvb: "/dev/dvb/adapter0" tuning to "Com Hem: 370,000 kHz" -- Front configuration failed -- Broken pipe, frequency: 370000000
Apr 07 18:55:01 subscription: "serviceprobe" unsubscribing
Apr 07 18:55:01 subscription: "serviceprobe" direct subscription failed -- Tuning failed
Apr 07 18:55:01 serviceprobe: TV5 Monde: could not subscribe
-
Ok.. I issued your command suggestion again, but changed to 5.1 and.. It works.. :)
Thanks for your help!
-
unfortunately if you set to 5.1 it will also set the API to 5.0 (it strips everything after the dot (the next driver update will take care that everything after the dot is also taken into account).
What will you lose?
> nothing, the API is backward compatible but some developers don't seem to know that.
-
Funny that it works though. I'm quite sure I didn't do anything else.
-
some applications use to check the API version that's the problem, even though it's nonsense.