Beiträge anzeigen

Diese Sektion erlaubt es ihnen alle Beiträge dieses Mitglieds zu sehen. Beachten sie, dass sie nur solche Beiträge sehen können, zu denen sie auch Zugriffsrechte haben.


Nachrichten - SevenW

Seiten: [1]
1
Drivers / Synology package: Unable to specify first_adapter
« am: Januar 20, 2018, 12:03:48 Nachmittag »
Hi,

For unknown reasons my anysee adapter and the sundtek stick both use adapter0 on my DS216. From a previous odroid setup I was familiar with the first_adapter=2 setting. Now it appears that the start-stop-status script removes the line with first_adapter=2 from /etc/sundtek.conf actively.

The removal is related to what I assume a cleanup action when a dvblink package has been deinstalled.

Could you make the removal more specific? For example you could remove the line only when it reads "first_adapater=8", as that is what the scripts conditionally puts in the conf file. Or make it optionally, or cofigurable through the UI.

In the current situation I have to make sepcifc adaptations to the sundtek start-stop-status script,which I do prefer not to do, as after a furutre update I might be struggling with the same issues again.

Thanks,
SevenW

2
Drivers / Synology package corrupts tvheadend dierkse 4.4.20180117-1
« am: Januar 20, 2018, 11:54:56 Vormittag »
Hi,

After spending several evenings figuring out all kind of privelige issues in tvheadend, I finally discovered that the sundtek start-stop-status script actually creates a new user account and changes the ownership of the tvheadend installation to that new user.

This may have been needed a few years back. Currently, it looks like Dierkse has the user accounts gotten right, and now the "hack" in the Sundtek driver is not required. Stronger, it seems to break tvheadend now.

Can you update the synology package either without having this "hack", or making it conditional on a tvheadend version, or make it configurable in the package install UI?

Thanks,
SevenW

3
Sundtek MediaTV Pro (Europe) / Re:USB errors disabling driver on Raspberry Pi
« am: November 20, 2012, 11:11:37 Nachmittag »
I can confirm that the USB issues are improved on the Raspberry, but not to the extend that it makes DVB-C usable. I have performed several tests on Raspberry Pi and on a Pogoplug v2.

The updated sundtek driver now indeeds keeps working, but USB communication gets messed up and even breaks the communication to the USB connected SmartCard reader.

Raspberry PI, kernel 3.1.19+, old sundtek driver:
Sundtek Media Pro: Not able to pass channel scanning in TVHeadEnd
Cinergy HTC USB XS (with linuxTV drivers): Able to scan channels, but contunity errors.

Raspberry PI, kernel 3.2.27+, new sundtek driver:
Sundtek Media Pro: Works reasonably well, but one continuty error per 2 seconds (Image distortion). SD unencrypted and encrypted working, HD unencrypted working.

Raspberry PI, kernel 3.6, new sundtek driver:
SD unencrypted and encrypted working, HD unencrypted working for all DVB-C sticks tested. HD encrypted is a too heavy load and does not work with any of the tested sticks.
Sundtek Media Pro: one continuity error every two seconds.
Cinergy HTC USB XS: more frequent continuty erros.
Anysee E30 Combo plus: Sometimes it works, but caused frequent hangups in TVHeadEnd.

Pogoplug, archlinux 3.1.x: with old sundtek driver and LinuxTV driver for Cinergy:
Both the Sundtek Media Pro and the Cinergy HTC USB XS worked, without continutiy erros for:
SD unencrypted and encrypted, and HD unencrypted. HD encrypte caused timeouts and was not usable.

To summarize: Regarding computing power the raspberry pi and pogoplug are sufficient to even decrypt a SD channel. The Raspbberry Pi USB port makes it unusable, and the pogoplug is just fine.

Currently the jury is still out on whether the Raspberry Pi USB can be fixed, but I am not going to hold my breath.

4
Sundtek MediaTV Pro (Europe) / Re:USB errors disabling driver on Raspberry Pi
« am: August 17, 2012, 12:16:01 Vormittag »
By now I tested with three different USB Hubs, and the error occurs in all cases in the same way. I also changed several usb cables and played around with different power supplies for the hubs. All three hubs are externally powered by an AC adapter. The hubs tested are:

  • ICIDU AI-707906 4-ports usb hub, powered by 5V, 2A adapter
  • Conceptronic C4USB2 4 port USB2.0 Hub, powered bu 5V, 1A and 5V, 2A adapter
  • SITECOM CN-019 4port usb 2.0, powered by 6V, 2.1A adpater (5V at USB-out!)

The error most of the time occurs changing the transponder, after setting the demodulator to 3. It can happen after ten seconds of transponder scanning, but also after two minutes. Besides the driver shutting down itself, very often it totally hangs the raspberry, so I need to remove and reconnect power to restart.

Can the driver be made a bit more fault tolerant?

Regards,
SevenW

5
Sundtek MediaTV Pro (Europe) / USB errors disabling driver on Raspberry Pi
« am: August 14, 2012, 10:58:47 Nachmittag »
When scanning services with TVHeadEnd, after one or two minutes a USB error occurs which disables the driver. I am using raspbian on Raspberry PI.
mediaserv.log
2012-08-14 22:27:32 [2787] USB Transfer problem, shutting down driver instance (-1 - 14)debug log
Aug 14 22:27:27 -------- kernel: [ 2742.787516]  usb 1-1.2.4: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 0 len 5 ret -844680027I am aware of USB issues on the raspberry. So I already did the following:
- Using a 4-port powered USB hub.
- Using dtvtransfermode=bulk
- Enable HW pidfiltering, as per this post http://support.sundtek.com/index.php/topic,941.msg6515.html#msg6515

I observed BTW that the file /etc/sundtek.conf apparently does not have effect. Both enabling loglevel=max and hwpidfiltering does not take effect after a reboot.

I hope there is more tweaking possible on usb timing parameters, or maybe the driver can be made more robust for incidental USB errors.

regards,
SevenW

Seiten: [1]