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

Seiten: [1]
1
I have two Media TV Pro sticks on a Cubietruck with Debian and tvheadend.
Everything works a few days after installation but suddenly my syslog gets flooded with the following entries I don't understand:

Jun  3 20:25:01 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_Sundtek_DVB_C__III_434000000" one is skipped
Jun  3 20:25:01 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:03 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_Sundtek_DVB_C__III_434000000" one is skipped
Jun  3 20:25:03 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:05 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_Sundtek_DVB_C__III_434000000" one is skipped
Jun  3 20:25:05 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:06 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_Sundtek_DVB_C__III_434000000" one is skipped
Jun  3 20:25:06 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:08 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:10 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:12 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:13 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:15 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:17 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:18 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:20 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:22 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:24 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:26 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:27 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:29 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter0_Sundtek_DVB_C__III_498000000" one is skipped
Jun  3 20:25:29 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_Sundtek_DVB_C__III_434000000" one is skipped
Jun  3 20:25:31 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_Sundtek_DVB_C__III_434000000" one is skipped
Jun  3 20:25:33 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_Sundtek_DVB_C__III_434000000" one is skipped
Jun  3 20:25:34 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier "_dev_dvb_adapter1_Sundtek_DVB_C__III_434000000" one is skipped
Jun  3 20:25:36 cubie tvheadend[2313]: dvb: Multiple DVB multiplexes with same identifier _dev_dvb_adapter1_Sundtek_DVB_C__III_434000000" one is skipped

I posted in a tvheadend forum but no response.
Maybe I am wron here as well but I hope for any ideas to understand the problem.

E.

2
Sundtek MediaTV Pro (Europe) / new MediaPro stick - no signal
« am: April 27, 2014, 01:44:59 Nachmittag »
I have a new (my second) MediPro Stick and try to get it running but have problems:

The driver seems to work.
erik@seeadler:~$ ps -efa| grep media
root      1178     1  0 13:00 ?        00:00:06 /opt/bin/mediasrv -d --pluginpath=/opt/bin
root      1179  1178  0 13:00 ?        00:00:00 /opt/bin/mediasrv -d --pluginpath=/opt/bin
erik      4596  3434  0 13:25 pts/1    00:00:00 grep --color=auto media
erik@seeadler:~$ mediaclient -e
**** List of Media Hardware Devices ****
device 0: [MediaTV Pro III USB (EU)]  DVB-C, DVB-T, DVB-T2, ANALOG-TV, FM-RADIO, REMOTE-CONTROL, OSS-AUDIO, RDS
  [BUS]:
     ID: 3-1
  [SERIAL]:
     ID: U140409205537
  [DVB-C]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [DVB-T]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [DVB-T2]:
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [ANALOG-TV]:
     VIDEO0: /dev/video0
     VBI0: /dev/vbi0
  [FM-RADIO]:
     RADIO0: /dev/radio0
     RDS: /dev/rds0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
  [OSS]:
     OSS0: /dev/dsp0
[code]
I can create channel.conf files with w_scan for DVB-T and DVB-C.
While scanning in the output of
mediaclient --lc
I  see the w_scan connected

When I try to test if I see a tv channel according to

http://wiki.sundtek.de/index.php/TreiberInstallation

and e.g. start kaffeine I see no channels.

The test with mplayer shows nothing
[code]
erik@seeadler:~$ cat /dev/dvb/adapter0/dvr0 | mplayer -cache 1024 -
MPlayer2 2.0-701-gd4c5b7f-2ubuntu2 (C) 2000-2012 MPlayer Team
Cannot open file '/home/erik/.mplayer/input.conf': No such file or directory
Failed to open /home/erik/.mplayer/input.conf.
Cannot open file '/etc/mplayer/input.conf': No such file or directory
Failed to open /etc/mplayer/input.conf.
Failed to read LIRC config file ~/.lircrc.

Playing -.
Reading from stdin...
Cache size set to 1024 KiB
Cache fill:  0.00% (0 bytes)

vdr logs always "keine Kanalinfo" or so...

In the DVB-C mode when connected to the cable there vdr errors ( I still struggle getting it running at all but the sysllog my reveal some hints..)
Apr 27 12:50:50 seeadler vdr: [3750] switching to channel 1
Apr 27 12:50:50 seeadler vdr: [3750] info: Kanal nicht verfügbar!
Apr 27 12:50:55 seeadler vdr: [3949] changing pids of channel 382 from 2047+2047=2:2048=deu@3,2049=deu@3:0:0 to 2047+2047=2:2048=deu@3,2049=deu@3:0:32
Apr 27 12:50:55 seeadler vdr: [3949] changing pids of channel 155 from 1279+1279=2:1280=deu@3,1281=eng@3;1283=deu@106:0:0 to 1279+1279=2:1280=deu@3,1281=eng@3;1283=deu@106:0:32
Apr 27 12:50:56 seeadler vdr: [3949] changing pids of channel 157 from 255+255=2:256=deu@3:0:0 to 255+255=2:256=deu@3:0:32
Apr 27 12:50:57 seeadler vdr: [3949] changing pids of channel 159 from 4863+4863=2:4864=deu@3,4865=eng@3:0:0 to 4863+4863=2:4864=deu@3,4865=eng@3:0:32
Apr 27 12:50:57 seeadler vdr: [3949] changing pids of channel 160 from 255+255=2:256=deu@3:0:0 to 255+255=2:256=deu@3:0:32
Apr 27 12:50:57 seeadler vdr: [3949] changing pids of channel 161 from 1791+1791=2:1792=deu@3,1793=deu@3:0:0 to 1791+1791=2:1792=deu@3,1793=deu@3:0:32
Apr 27 12:51:01 seeadler vdr: [3750] switching to channel 1
Apr 27 12:51:01 seeadler vdr: [3750] info: Kanal nicht verfügbar!
Apr 27 12:51:12 seeadler vdr: [3750] switching to channel 1
Apr 27 12:51:12 seeadler vdr: [3750] info: Kanal nicht verfügbar!


Any idea how to understand whats going wrong?
So my first stick bought on 23.12.13 was changed because of a hardware defect. Now i want to make sure that it is "only" my problem if I see nothing.

I remember with my first stick I could see an example channel in kaffeine or vlc, i don't remember (it is currently recording on my Raspi, I could check later if the "old" one works).
[/code][/code]

3
Sundtek MediaTV Pro (Europe) / Re:USB errors disabling driver on Raspberry Pi
« am: April 27, 2014, 01:22:08 Nachmittag »
I just want to mention, that I had very (very!) weird problems with USB and the Raspberry due to the backpowering of powered USB hubs to the Raspberry.

After weeks of searching I found that hint in a Raspi forum and cut the red wire inside the USB cable from the hub to the Raspi.
After that it works very stable.
I have tvheadend backend running on Raspi.

I have a xystec 7 port powered hub.

4
Software / Re:dvb-c mit Raspberry Pi und OpenElec ruckelt
« am: April 27, 2014, 12:45:45 Nachmittag »
Hi,
Ich habe seit einiger Zeit tvheadend unter Debian auf dem Raspberry laufen, allerdings ohne frontend.
Das funktionert eigentich sehr gut. Die Last ist bei Aufnahmen (DVB-C) um die 60% - 80%. Die Aufnahmen - auch HD - sind gut (genug für mich als interessierten Laien).

Mit Openelec und xbmc hatte ich (leider) auch Performance Probleme.

Beim streamen übers Netz von dem Raspi auf einen PC xbmc mit tvheadend frontend reisst die Verbindung auch immer ab nach einer gewissen Zeit (nach einer halben bis 7 Minuten).   

Da mein Eindruck war, dass es generell schon funktioniert und nur die Performance des Raspi zu gering ist,
 versuche ich mein Glück derzeit mit einem Cubietruck. Ich will einen PVR mit xbmc und Mediapro ohne Intel... 

vdr ist die am besten dokumentierteste Software, die ich bisher gefunden habe und hat eine voll übersichtliche Architektur *harhar*. Ich versuchs auch grad mit sehr geringer Trial-And-Error-Effektivität. ;-)

5
Sundtek MediaTV Pro (Europe) / Re:USB errors disabling driver on Raspberry Pi
« am: März 18, 2014, 08:06:05 Vormittag »
I know that is a late reply, but sice I have a lot pain with similar problems (and same log events) here my experience:

I have a 7 pot powered xystec hub and had to cut the red wire which was back-powering the Raspberry Pi !

After that my frequent network (usb) crashes went away. But after ~half a day the network interface /wlan and lan) went down and came again after about 50 pings. Sometimes it crashed completely.

Now using a stronger Power supply and it seem to be stable.

So be very careful with eowersupply on Raspberry, it seems to be extremly sensitive and causes very weird problem symptoms..

BTW any information about power consumption of the Sundtec sticks?

Example logs (out of millions of lines)
Mar 17 14:14:49 rasperik kernel: [65706.784785] usb 1-1.2.2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 192 rq 13 len 4 ret -71
Mar 17 14:14:50 rasperik kernel: [65706.820697] usb 1-1.2.2: usbfs: USBDEVFS_CONTROL failed cmd mediasrv rqt 64 rq 2 len 2 ret -71
Mar 17 14:14:50 rasperik kernel: [65707.066324] hub 1-1.2:1.0: cannot reset port 1 (err = -71)
Mar 17 14:14:50 rasperik kernel: [65707.066577] hub 1-1.2:1.0: cannot reset port 1 (err = -71)
Mar 17 14:14:50 rasperik kernel: [65707.066855] hub 1-1.2:1.0: cannot reset port 1 (err = -71)
Mar 17 14:14:50 rasperik kernel: [65707.067053] hub 1-1.2:1.0: cannot reset port 1 (err = -71)
Mar 17 14:14:50 rasperik kernel: [65707.067392] hub 1-1.2:1.0: cannot reset port 1 (err = -71)
Mar 17 14:14:50 rasperik kernel: [65707.067419] hub 1-1.2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
Mar 17 14:14:50 rasperik kernel: [65707.067759] hub 1-1.2:1.0: cannot disable port 1 (err = -71)
.....

regards
E.

6
Treiber / Re:vdr mit Sundtek MediaTV Pro III (raspberry pi mit raspian, DVB-C)
« am: Januar 13, 2014, 08:59:53 Vormittag »
Danke. Gut dass ich es weiss und nicht noch weitere Zeit mit fruchtlosen Bemühungen verbringe würde.
Bin ansonsten recht zufrieden mit Sundtek...

7
Treiber / Re:vdr mit Sundtek MediaTV Pro III (raspberry pi mit raspian, DVB-C)
« am: Januar 12, 2014, 04:42:18 Nachmittag »
Hallo Ich habe auch meinen Stick am 24.12.2013 bekommen und habe auch Probleme mit Artefakten und Tonstörungen.
Muss ich den umtauschen??

Viele Grüße
Kallewirsch

8
Treiber / Re:Linux Treiber 4. Januar 2014
« am: Januar 12, 2014, 04:24:58 Nachmittag »
Danke für den neuen Treiber !

Eine Frage: Gibts irgendwo ein Startscript für z.B. Debian /etc/init.d ?
Ich starte jetzt erst mal über einen manuellen Eintrag in /etc/rc.local. Sauberer wäre aber ein kleines Startscript, wie bei allen Serverdiensten.

VG
Kallewirsch

9
Dokumentation / Re:Sendereinstellung mit mediaclient
« am: Januar 12, 2014, 04:19:26 Nachmittag »
Hallo zusammen,
ich habe einen MediaTV Pro III USB und gerade die Treiber auf Debian installiert. Ich habe kein "scan" Tool.
Sollte das bei dem Treiberpaket dabei sein?
Ich habe das Debian Paket installiert.

Alles Gute im neuen Jahr
Kallewirsch

Seiten: [1]