Sundtek and Nova-T at the same time

[OldSkul]

My primary stick is Nova-T (tuner C) and today i installed sundtek stick. It only shows as tuner D when i put this line in sundtek.conf: vtuner_skip0=vtuner0

Usb stick is then detected as tuner D but when i zap to random dvb-c channel, it wants to use tuner C which is DVB-T. Basically its a mess. Anyone has a clue what to do here?

[OldSkul]

I am also attaching two dmesg files. Dmesg1 was made when only nova-t was installed. Dmesg2 was made when both sticks were installed.

http://www.sendspace.com/file/rov4n8

[OldSkul]

I also tested same situation on ET-5000. Same image, same sticks (nova-t and sundtek) and everything works as expected. I assume there must be something wrong with vuduo driver+sundtek drivers.

In the past i already tested two usb dvb-t sticks (nova-t and volar-hd) and they worked together without any problems. But it was old kernel back then. Now its newer one.

I also put clean latest pli image on VU+DUO and same problem as described in first post.

[Sundtek]

A simple way might be to re-create the virtual tuner interface nodes. That would be a workaround for a bug of the vu+ broadcom modules.

If possible contact us again via Skype.

You might be able to do that by running:

mv /dev/misc/vtuner1 /dev/misc/vtuner3
mv /dev/misc/vtuner0 /dev/misc/vtuner1
mv /dev/misc/vtuner3 /dev/misc/vtuner0

In order to make that work you might add it to the second line of sun_dvb.sh in /usr/sundtek

The problem is probably the slot allocation in the VU+ broadcom module.

[OldSkul]

I tried your suggestion but it doesnt work. Tuner C (Sundtek) works OK, but when i use tuner D (Nova-T), picture is black. Receiver doesnt use tuner D. When i check which tuners are present under Enigma2 Information, i can see both tuners.

What to do now?

[Sundtek]

Try to put those commands into /usr/sundtek/sun_dvb.sh (paste it after the first line of this script)

[OldSkul]

This is first thing i did! *.sh file looks like this:

#!/bin/sh
mv /dev/misc/vtuner1 /dev/misc/vtuner3
mv /dev/misc/vtuner0 /dev/misc/vtuner1
mv /dev/misc/vtuner3 /dev/misc/vtuner0
if [ -f /usr/sundtek/mediasrv ]; then
  DRIVERPATH=/usr/sundtek
......

[Sundtek]

and you still have this one in sundtek.conf vtuner_skip0=vtuner0?

[OldSkul]

Yes!

I can give you remote access to my box if that will help you.

[OldSkul]

Any clue what to do here?

[Sundtek]

Pieterg is looking into it to skip vtuner0 if it's already in use as this is the main issue actually. Unfortunately we're a little bit busy here for this week so further support for this has to be postponed until the beginning of next week.

[Sundtek]

By the way try moving the files back at the end of sun_dvb.sh

[OldSkul]

Tuner doesnt work at all with these lines at the end. I tried to put them before and after "exit 0" line!

[Sundtek]

The explanation is:

The VU+ System has an internal slot mechanism

1
2

actually at the beginning when our driver starts up no change is needed it should take 1 and no vtuner_skip should be used from your side.
After the registration (at the end of the script), the node /dev/misc/vtuner0 should be swapped with /dev/misc/vtuner1

OpenPLi will by default allocate vtuner0 for the first tuner, the internal VU+ slot mechanism will still think that the first allocated tuner will be Number 1. While OpenPLI will think the other way around.

[OldSkul]

New drivers are out and they apperantly improved vtuner performance. Maybe they fixed this issue?