The driver installation is currently mainly done on the console, we are working on providing a graphical installer lateron. The driver is developed by Sundtek Ltd. and runs as normal application (in userspace), if unexpected problems occur the system will not be affected by it, aside of that it has the advantage that it is not bound to any particular kernel version which makes difficult compiling unnecessary.

Minimum System requirements Linux 2.6.15/libc2.4+ 32 or 64 bit (which is basically supported by all distributions which have been available for the last 4 years/since 2006), 1.5 Ghz

* Apple (Sundtek MediaTV Gold/will be released soon, mediaclient commands will work, although the Apple support comes with an extra Mac based installer and extra TV application)

Please note that the linux 2.6.27 and 2.6.28 series have a bug in the USB System wich makes the memory usage of the Linux system grow, this causes the system to run out of memory after some time. You can read more about this issue and how to fix it on the Linux USB Mailinglist, it is probably easier to use Linux 2.6.15 - 2.6.26 or 2.6.29+.

In case you do not have a device but already want to play around with it, you can try to use our virtual demo driver which supports emulating video devices. After the installation just run "/opt/bin/mediaclient --tvdummy" for creating a virtual driver instance. Screenshot

by default most linux tv players do not support digital audio properly, in order to fix that problem our driver supports internal audio processing, which means that the driver automatically tries to play the available data to the default soundcard, while the TV application is just in charge of displaying the video.

PowersavingThe powersaving will be activated after 15 seconds of inactivity, after this time the device will start to cool down. Powersaving also increases the lifetime of the USB TV device.

Troubleshooting

it's possible that some applications already access the device driver during the bootup. This will cause the device to be set to the corresponding device mode.To check which applications are accessing the driver you can run following command:

please note tvtime does not support audio playback by itself, the multimedia framework itself is taking care about it, this also shows up the audio process being connected to the driver.

In order to disconnect (not to kill) tvtime from the driver following command can be used:

Zitat

$ /opt/bin/mediaclient --dc 329

Pulseaudio

There are some useful pulseaudio tools available (for example pavucontrol). Pavucontrol allows to individually configure the audio volume. Since pulseaudio is not stable yet it might happen that the driver switches back to Alsa during the runtime.

By default the signalreporting returns 0% or 100%, this can be changed to a more accurate signalreporting by using following command:

Code:

/opt/bin/mediaclient --signalreporting=1

(inaccurate reporting does not take such a long time to read the information from the device, with more accurate signalreporting mplayer won't run smoothly)

Code:

Syntax:/opt/bin/mediaclient -d /dev/video[n] --readsignal=[i]whereas n is the videodevice (accordingly to /opt/bin/mediaclient -e) and i how often the signal should be read. If i is smaller or equal 0 the signalstatistics will only stop when the user interrupts the application.

In order to automatically start an application when the device gets plugged in or removed:

The configurationfile /etc/sundtek.conf can contain 2 parameters, device_attach and device_detach.Those parameters can be used to start or reinitialize applications after the driver initialized a device.

DEVID will automatically be replaced with the device ID which is also returned by /opt/bin/mediaclient -e

----

Changing the transfermode for DVB-T/C from Isochronous to Bulk (some embedded PCs do not support Isochronous transfer with linux), this option can also work around some possible kernel isochronous bugs which are in 2.6.26-2.6.29 and 2.6.32.9 - 2.6.33.1.

By default when the devices are shipped, the device will be in Isochronous mode

To change it to Bulk:$ /opt/bin/mediaclient --dtvtransfermode=bulk -d /dev/dvb/adapter0/frontend0 Setting transfermode to BulkPlease reconnect your device in order to activate the transfer mode change

After switching the mode the device needs to be replugged

----

Hardware PID Filter

In order to use the hardware PID filter it needs to be enabled. The USB TV tuner supports up to 15 PID filters. The PID Filters can lower the required USB 2.0 bandwidth significantly - this is recommended for embedded PCs.

We just tested the installer on Ubuntu 12.04 and it does not cause any problems.Since the architecture check already fails (that is what checking sytem ... Your system is currently unsupported means) it seems like your download is corrupted or incomplete.

I tried all relevant installation methods (installer, netinstall and the deb (it seems to download and execute the netinstall script), the downloads where complete. But all resulted in the same failure.

Anything I can try, or information I can provide to help resolve this issue?

We still believe that your download is corrupted, the architecture check only tries to run a 32 or 64bit application on x86. Once this fails it means that your system cannot run any application. This would be the very first installer issue on x86 since the beginning of our driver support.

I'm quite sure the download is ok. What I did now is the following, download the full installer, put it on a USB drive and install that on my old laptop. All 100% ok.

Now with the same USB drive I again tried to install on my new laptop and the error is the same as before. I also tried the following command: # sudo bash sundtek_installer_development.sh -system 64bit

The result:

Code:

Welcome to the Sundtek linux driver setup

Legal notice:This software comes without any warranty, use it at your own risk