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 - HWTest

Seiten: [1] 2
1
Drivers / Re:Sundtek DVB-T and Wetek
« am: November 25, 2016, 04:13:03 Nachmittag »
Done under the old ticket.

2
Drivers / Re:Sundtek DVB-T and Wetek
« am: November 23, 2016, 12:14:32 Nachmittag »
Any news on this?

3
Drivers / Re:Sundtek DVB-T and Wetek
« am: April 23, 2016, 02:40:35 Nachmittag »
OK, thanks.

4
Drivers / Re:Sundtek DVB-T and Wetek
« am: April 23, 2016, 02:17:44 Nachmittag »
Any news on this?
My ticket is unchanged (156f6899b0e88c).
Should I try the chat (again)?
Last time, I have tried, I was advised to create a ticket ...

5
Drivers / Re:Sundtek DVB-T and Wetek
« am: April 02, 2016, 05:44:02 Nachmittag »
Did you get it to work?
only tried to install drivers with SSI and then with Sundtek Control Center.
Using now newest OpenATV 5.1

No.

6
Drivers / Re:Sundtek DVB-T and Wetek
« am: März 29, 2016, 04:58:03 Nachmittag »
OK

7
Drivers / Re:Sundtek DVB-T and Wetek
« am: März 29, 2016, 04:31:36 Nachmittag »
OK, now I got it :-)

The tuner is now visible in E2 but it still doesn't work, when I record something with the first (internal tuner) I cant switch to another mux, its grayed out. When I disable the first tuner, so only the USB tuner stays active, I get no signal.
The blue LED on the stick behaves the same, it goes on during the boot but after a couple of seconds it goes off and stays off.

8
Drivers / Re:Sundtek DVB-T and Wetek
« am: März 29, 2016, 04:02:43 Nachmittag »
That's what I did (edit nim_sockets in /tmp) but I thought it doesn't help sitting in /tmp, so what have I to do with the edited nim_sockets file? Leaving it in /tmp makes no sense, it gets deleted after a reboot.

According the py and pyo files, that's what I thought.

9
Drivers / Re:Sundtek DVB-T and Wetek
« am: März 29, 2016, 02:57:04 Nachmittag »
Sorry, I'm a bit lost...

It's a PBnigma image.

I've added this to the nim_sockets :

NIM Socket 1:
Type: DVB-T
Name: Sundtek DVB-T (1/0) (USB)
Frontend_Device: 1

But I'm not able to overwrite the original file with the modified one.

When I delete the pyo and copy the py file, it creates a new pyo file.

I was advised on your IRC support chat to create a ticket, when I posted my problem there.

10
Drivers / Re:Sundtek DVB-T and Wetek
« am: März 28, 2016, 06:23:10 Nachmittag »
Ok, thanks.
So it is possible but I'm not sure how.
I didn't find the NimManager.py only NimManager.pyo
I'm afraid simply replacing the /proc/bus/nim_sockets with /dev/dvb/adapter1 is not the solution ... ?

11
Drivers / Re:Sundtek DVB-T and Wetek
« am: März 28, 2016, 03:49:35 Nachmittag »
Meaning it'll not work on the Wetek in E2?

12
Drivers / Sundtek DVB-T and Wetek
« am: März 26, 2016, 01:51:01 Nachmittag »
I have a problem with my Sundtek DVB-T stick on my Wetek play running PBnigma.
I've installed the driver using sundtek_netinst, then unpacked the stb.tar a started using the sun_dvb start_t.
The blue light on the stick comes on and after a couple of seconds it goes off and the tuner is not visible under E2.
I've found nothing relevant in the logs.
Has anybody an idea what to check and how to make it work?

13
Es hat geklappt.
Vielen dank.

14
Sundtek MediaTV Pro / Stick in Ubuntu 12.04 über Netzwerk automatisch mounten?
« am: Juni 25, 2012, 09:23:17 Nachmittag »
Wie kann ich den Stick in Ubuntu 12.04 über das Netzwerk automatisch mounten?

Im /etc/sundtek.org habe ich:
device_attach=/etc/init.d/tvheadend restart
device_detach=/etc/init.d/tvheadend restart
ir_disabled=1
bulk_notification=on
network_tuner_ip=x.x.x.x
[U11083XXXXXXX]
initial_dvb_mode=DVBT

Ich dachte die Zeile "network_tuner_ip=x.x.x.x" sollte reichen, reicht aber nicht.
Nach einem manuellem mount (/opt/bin/mediaclient --mount=x.x.x.x) und TVHeadend Restart ( /etc/init.d/tvheadend restart) funtioniert es normal.

15
Sundtek MediaTV Pro / Re:OpenELEC über Netzwerk
« am: Juni 08, 2012, 07:51:38 Nachmittag »
Ultraman (vpeter) hat die Treiber für OpenELEC für mich modifiziert und jetzt läuft es 1A.

Nochmals vielen Dank an Ultraman (vpeter)  :)

Seiten: [1] 2