Sundtek Support Forum
English => Sundtek MediaTV Pro (Europe) => Thema gestartet von: derabbink am Mai 19, 2014, 06:50:16 Nachmittag
-
I have a MediaTV Pro III that I want to use for DVB-C. I currently trying to figure out how everything works using an Ubuntu 12.04 x86_64 VM, hosted by VirtualBox.
On my provider's network, at least one DVB-C channel is unprotected and freely available.
The problem I have is that scanning, using the scan and dvbscan utils, does not seem to work:
$ scan /usr/share/dvb/dvb-c/nl-Ziggo
scanning /usr/share/dvb/dvb-c/nl-Ziggo
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 372000000 6875000 0 3
initial transponder 514000000 6875000 0 3
initial transponder 356000000 6875000 0 3
initial transponder 369000000 6875000 0 3
>>> tune to: 372000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
>>> tune to: 514000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
WARNING: >>> tuning failed!!!
>>> tune to: 514000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64 (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 356000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
WARNING: >>> tuning failed!!!
>>> tune to: 356000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64 (tuning failed)
WARNING: >>> tuning failed!!!
>>> tune to: 369000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
WARNING: >>> tuning failed!!!
>>> tune to: 369000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64 (tuning failed)
WARNING: >>> tuning failed!!!
dumping lists (0 services)
Done.
$ dvbscan /usr/share/dvb/dvb-c/nl-Ziggo
Unable to query frontend status
I installed the latest drivers from the .deb file. What I noticed is that there is currently no /etc/sundtek.conf file on my system; the installer didn't create one.
In my VirtualBox USB configuration, I have checked "USB 2.0 (EHCI) Controller". This may be relevant, considering my /var/log/mediaclient.log (see below) and this post (http://support.sundtek.com/index.php/topic,1579.msg11685.html#msg11685).
How can I make this work on VirtualBox?
I set the logging level to max (/opt/bin/mediaclient --loglevel=max) and this is what I got in /var/log/mediasrv.log while trying to scan:
//log corresponding to scan command
2014-05-19 18:00:20 [3232] Waking up in digital TV mode
2014-05-19 18:00:22 [3232] Power up demodulator
2014-05-19 18:00:43 [3232] SETTING DVB-C
2014-05-19 18:00:43 [3232] Setting Frequency: 369000000
2014-05-19 18:00:43 [3232] Setting Symbolrate: 6875000
2014-05-19 18:00:43 [3232] Setting Modulation: 3
2014-05-19 18:00:43 [3232] setting symbolrate: 6875
2014-05-19 18:00:43 [3232] Tuning DVB-C Frequency: 369000000
2014-05-19 18:00:43 [3232] Setting Frequency: 372000000
2014-05-19 18:00:43 [3232] Setting Symbolrate: 6875000
2014-05-19 18:00:43 [3232] Setting Modulation: 3
2014-05-19 18:00:43 [3232] setting symbolrate: 6875
2014-05-19 18:00:43 [3232] Tuning DVB-C Frequency: 372000000
2014-05-19 18:00:44 [3232] Resetting TS Port
2014-05-19 18:00:46 [3232] Resetting TS Port
2014-05-19 18:00:48 [3232] Resetting TS Port
2014-05-19 18:00:50 [3232] Resetting TS Port
2014-05-19 18:00:52 [3232] Resetting TS Port
2014-05-19 18:00:54 [3232] Resetting TS Port
2014-05-19 18:00:56 [3232] Resetting TS Port
2014-05-19 18:00:58 [3232] Resetting TS Port
2014-05-19 18:01:00 [3232] Resetting TS Port
2014-05-19 18:01:00 [3232] Setting Frequency: 514000000
2014-05-19 18:01:00 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:00 [3232] Setting Modulation: 3
2014-05-19 18:01:00 [3232] setting symbolrate: 6875
2014-05-19 18:01:00 [3232] Tuning DVB-C Frequency: 514000000
2014-05-19 18:01:07 [3232] Setting Frequency: 514000000
2014-05-19 18:01:07 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:07 [3232] Setting Modulation: 3
2014-05-19 18:01:07 [3232] setting symbolrate: 6875
2014-05-19 18:01:07 [3232] Tuning DVB-C Frequency: 514000000
2014-05-19 18:01:14 [3232] Setting Frequency: 356000000
2014-05-19 18:01:14 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:14 [3232] Setting Modulation: 3
2014-05-19 18:01:14 [3232] setting symbolrate: 6875
2014-05-19 18:01:15 [3232] Tuning DVB-C Frequency: 356000000
2014-05-19 18:01:22 [3232] Setting Frequency: 356000000
2014-05-19 18:01:22 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:22 [3232] Setting Modulation: 3
2014-05-19 18:01:22 [3232] setting symbolrate: 6875
2014-05-19 18:01:22 [3232] Tuning DVB-C Frequency: 356000000
2014-05-19 18:01:29 [3232] Setting Frequency: 369000000
2014-05-19 18:01:29 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:29 [3232] Setting Modulation: 3
2014-05-19 18:01:29 [3232] setting symbolrate: 6875
2014-05-19 18:01:29 [3232] Tuning DVB-C Frequency: 369000000
2014-05-19 18:01:36 [3232] Setting Frequency: 369000000
2014-05-19 18:01:36 [3232] Setting Symbolrate: 6875000
2014-05-19 18:01:36 [3232] Setting Modulation: 3
2014-05-19 18:01:36 [3232] setting symbolrate: 6875
2014-05-19 18:01:36 [3232] Tuning DVB-C Frequency: 369000000
2014-05-19 18:01:59 [3232] Enabling Standby
//log corresponding to dvbscan command
2014-05-19 18:06:01 [3232] Waking up device
2014-05-19 18:06:01 [3232] Waking up in digital TV mode
2014-05-19 18:06:03 [3232] Power up demodulator
2014-05-19 18:06:24 [3232] SETTING DVB-C
2014-05-19 18:06:24 [3232] Setting Frequency: 369000000
2014-05-19 18:06:24 [3232] Setting Symbolrate: 6875000
2014-05-19 18:06:24 [3232] Setting Modulation: 3
2014-05-19 18:06:24 [3232] setting symbolrate: 6875
2014-05-19 18:06:24 [3232] Tuning DVB-C Frequency: 369000000
2014-05-19 18:06:24 [3232] Setting Frequency: 372000000
2014-05-19 18:06:24 [3232] Setting Symbolrate: 6875000
2014-05-19 18:06:24 [3232] Setting Modulation: 3
2014-05-19 18:06:24 [3232] setting symbolrate: 6875
2014-05-19 18:06:24 [3232] Tuning DVB-C Frequency: 372000000
2014-05-19 18:06:39 [3232] Enabling Standby
When I looked in the /var/log/mediaclient.log, I discovered a bunch of lines similar to the following; although I'm not sure how they relate to my scanning attempts:
2014-05-19 17:10:56 [20535] connection to driver service timed out
-
I would not wonder about that, try to use the network infrastructure of the driver with Virtualbox.
USB Pass through performance in virtual machines is usually not the best one.
http://support.sundtek.com/index.php/topic,179.0.html