Sundtek Support Forum

Hi all, hope everything is well with all you.

I am facing a problem with my sundtek mediatv pro III.  PVRs softwares like tvheadend can't find the adapter. The last driver is installed and I can see the adapter at /dev/dvb.

HAve someone faced this problem before? I'm on debian 10 - kernel 5.3.18-2

Thank you

Hello,

I've been using my mediatv pro III normally but today when I came home it can't be detected anymore.

Tried it on linux and windows and none of them can detect it.

When starting up the system be sure nothing accesses the device

Run:
/opt/bin/mediaclient --cat /dev/dvb/adapter0/dvr0 > /dev/null


this will prevent that the device will go to standby and turn off the datatransfer  (the turning off the datatransfer part causes the issue with the usb 3.0 controllers at the moment)
The tuners have no problem with that since they are very low power.

Second of all start VDR

This would be a workaround for now until the USB 3.0 controller issue will be fixed.

I've removed vdr's default init script using update-rc.d and created my own script with follow content:
/opt/bin/mediaclient --cat /dev/dvb/adapter0/dvr0 > /dev/null
sleep 3
/etc/init.d/vdr start
But the system is still hanging.

Ok from the Logfile I see that this is a faulty AMD system, possibly that there's another USB controller bug hitting you.
AMD SB600 / SB700 boards are known to have various issues.

in your logfile there's one indicator for one workaround that is needed by this controller:
ehci-pci 0000:00:12.2: EHCI Host Controller
[    2.924058] ehci-pci 0000:00:12.2: new USB bus registered, assigned bus number 1
[    2.925778] ehci-pci 0000:00:12.2: applying AMD SB700/SB800/Hudson-2/3 EHCI dummy qh workaround
[    2.927844] ehci-pci 0000:00:12.2: debug port 1
[    2.928987] ehci-pci 0000:00:12.2: irq 17, io mem 0xfe3ff800


You might try to change the transfermode of the USB device.

/opt/bin/mediaclient --transfermode=iso -d /dev/dvb/adapter0/frontend0

Maybe that helps.

I would really advice to get some Raspberry PI and use the device via network, or try to get a workable USB PCI/PCIe controller.
A problem on our driver side is not possible in that area unfortunately (otherwise we'd prefer to fix it in order to avoid other ones having the same issue...)

If you can reproduce this issue you should report this bug on https://bugzilla.kernel.org/

Humm, I have an pcie usb 3.0 installed in this server but as soon as I plug  in the mediatv a get a hell of kernel hang messages. I'll post my dmesg with the media tv plugged in, maybe you can help.

Is this a USB 3.0 port?

Seems like a USB Controller driver bug. You might have to change the Linux Kernel in order to get a better driver compatibility with your USB Controller Hardware.
This has nothing to do with the device nor the driver itself.
The driver is only application based, the worst thing that could happen is that the driver application crashes itself - but in no circumstance it would be allowed to create kernel issues because the driver does not even have enough permissions for that.
If that happens your USB Controller is very likely not well supported.

There are some USB 2.0 through USB 3.0 issues at the moment with the Linux USB controller driver, not sure if that also affects your system.

As a quick workaround you might try to use a Raspberry PI and use the device via network:
http://support.sundtek.com/index.php/topic,179.0.html

Since the driver supports network sharing on device level you could still use VDR with the virtual device on your target system.

No, it's a USB 2.0 port and the hardware is a HP Microserver N40L which I use as NAS.

Now I can start VDR, watch some TV but after a while the mediasrv crash with this kernel message and stops VDR.

My main problem is that this server is my only server and I don't have any other spare computer around to install another distro with a compatible kernel. But if this is the only solution, I'll have to reinstall my NAS using a compatible distro with a compatible kernel. Do you mind to tell which kernel version is compatible with your driver?

Thank you

Bruno

Use mplayer -ao null -vo null (add the last 4 parameters), mplayer will show up some Details on the console.


tsscan will show up transponder information in a more verbose format (not the one which can be read by vdr).

Hello, thank you for your help! I've found a solution for my problem.

I have set StandardCompliance = 1 in setup.conf and everything is working now.

Which system do you use?

HD Channels need AC3 Support, does your XBMC Setup support AC3?

I am not entirely sure but usually HD channels also deliver MP2 Audio channels, you possibly might have to change the Audio channel in the tvheadend setup (I didn't do that myself yet because we never experienced such issue yet).

It's working with some HD channels including with AC3 audio xbmc doesn't shows audio tracks in the problematic ones.

I think it's some related to how channels.conf was generated.

Looking at channels.conf w_scan has generated, I've found that the channels without audio doesn't have APID set up like the channels with audio:

Without audio : FOX HD;(null):267000:M256:C:5217:2320=27:0;2321,2322:0;2116:1861,1802:631:2:40:0
With audio: ESPN HD ;(null):129000:M256:C:5217:1056=27:1057=eng@4;1058:0:1802,1861:571:2:35:0

I'm using VDR 2.1.6 + VNSI Server 1.2

It's in progress and on our list, possibly around at the beginning / mid of next week.
Sorry for the late reply.

That's a great addition to the windows driver, can't wait to see this working!

Thank you!