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

Seiten: [1]
1
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re:kernel requirements for lirc (/dev/input/...)
« am: Juni 03, 2015, 09:55:26 Nachmittag »
Hi,

I've got the answer: :)

The default configuration file provided by your company seems to be faulty in the way that there is a 0x00000000000 entry after every code mapping.

This seems to confuse lirc. I deleted these second entries and everything worked just fine. :)

2
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re:kernel requirements for lirc (/dev/input/...)
« am: Mai 25, 2015, 01:34:31 Nachmittag »
Hi,

Code: [Auswählen]
/etc/init.d/lirc stop
[ ok ] Stopping execution daemon: irexec:.
[ ok ] Stopping remote control daemon(s): LIRC:.
root@cubietruck:~# /opt/bin/mediaclient --updaterc=3 -d /dev/mediainput0
Updating remote control layout
done
Doing a
Code: [Auswählen]
cat /dev/input/event0gives me
Code: [Auswählen]
�cUҎ��cUҎ�cU����cU���cUt���cUt��cU����cU���cU7^��cU7^�cU�^��cU�^while pushing buttons at the rc.

Stopping vdr and starting lirc, irw gives me nothing:
Code: [Auswählen]
/etc/init.d/vdr stop
Stopping Linux Video Disk Recorder: vdr.
root@cubietruck:~# irw
connect: Connection refused
root@cubietruck:~# /etc/init.d/lirc start
[ ok ] Loading LIRC modules:.
[ ok ] Starting remote control daemon(s) : LIRC :.
[ ok ] Starting execution daemon: irexec:.
root@cubietruck:~# irw
 
BUT::
Stopping vdr and lirc, then pressing buttons at the rc gives me:
Code: [Auswählen]
May 25 13:36:42 localhost kernel: [  172.053463] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 1
May 25 13:36:42 localhost kernel: [  172.053483] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.053601] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 0
May 25 13:36:42 localhost kernel: [  172.053610] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.211109] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 1
May 25 13:36:42 localhost kernel: [  172.211126] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.211212] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 0
May 25 13:36:42 localhost kernel: [  172.211221] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.236751] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 1
May 25 13:36:42 localhost kernel: [  172.236768] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 25 13:36:42 localhost kernel: [  172.236851] evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 0
May 25 13:36:42 localhost kernel: [  172.236860] evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
So the rc seems to be working in some way, but what am I missing in the lirc configuration ?

3
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re:kernel requirements for lirc (/dev/input/...)
« am: Mai 25, 2015, 12:04:23 Nachmittag »
Hi,

thanks for the hint, I enabled the uniput module and now it's getting recognized as
Code: [Auswählen]
/opt/bin/getinput.sh
waiting 5 seconds...
Sundtek IR Event: /dev/input/event0
and dmesg|grep input gives me
Code: [Auswählen]
dmesg|grep input
[    9.461560] input: Sundtek Ltd. Remote Control as /devices/virtual/input/input0
[    9.462040] evbug: Connected device: input0 (Sundtek Ltd. Remote Control at unknown)
but following the instructions at your lirc howto page doesn't get the remote working, irw gives me no output.

This is my hardware.conf:
Code: [Auswählen]
# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Don't start irexec, even if a good config file seems to exist.
#START_IREXEC=false

#Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="devinput"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/input/event0"
MODULES=""

# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""
I've got the "big" remote control, so I copied the sundtek_vcr_remote.conf to /etc/lirc/lircd.conf and did a
Code: [Auswählen]
/opt/bin/mediaclient --updaterc=1 -d /dev/mediainput0
Updating remote control layout
done
dpkg-reconfigure lirc doesn't give me a configuration menu (ncurses-dev installed), so I edited the hardware.conf manually.

Starting lirc I get
Code: [Auswählen]
May 25 12:00:04 localhost lircd-0.9.0-pre1[2566]: lircd(devinput) ready, using /var/run/lirc/lircd
May 25 12:00:04 localhost lircd-0.9.0-pre1[2566]: accepted new client on /var/run/lirc/lircd
May 25 12:00:04 localhost lircd-0.9.0-pre1[2566]: initializing '/dev/input/event0'
May 25 12:00:04 localhost kernel: [   47.743886] input: Sundtek Ltd. Remote Control (lircd bypass) as /devices/virtual/input/input3
May 25 12:00:04 localhost kernel: [   47.745543] evbug: Connected device: input3 (Sundtek Ltd. Remote Control (lircd bypass) at unknown)
irw gives me not output at all.

What can I do ?

4
{Single, Dual, Quad} Sundtek SkyTV Ultimate / kernel requirements for lirc (/dev/input/...)
« am: Mai 24, 2015, 04:12:12 Nachmittag »
Dear Sundtek Support Team,

I'm using a SkyTV Ultimate on a Cubietruck (Debian Wheezy, Kernel 3.19.4) with VDR and lirc.
My problem is, that the IR-Device of the stick isn't being recognized by the system:

Code: [Auswählen]
/opt/bin/getinput.sh
waiting 5 seconds...
ls: cannot access /event*: No such file or directory
The event structure is enabled in kernel config, first it was compiled as a module, now it is fixed, but that doesn't change the fact, that there is no entry in /dev/input/event...
I can get output from the IR-device doing a
Code: [Auswählen]
cat /dev/mediainput0, but I can't use /dev/mediainput0 with lirc/devinput config.

I want to be able to run a shutdown script using irexec, but since there's no entry in /dev/input/..., it can't be accessed by lirc.

Please help. :)

5
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Treiber-Bug Linux-Treiber vom 24.03.2015 (?!)
« am: April 06, 2015, 01:18:55 Nachmittag »
Hallo Sundtek,

ich habe einen extra Post zu meinem Problem in http://support.sundtek.com/index.php/topic,1848.0.html aufgemacht.

Kurz und knapp:
Mein System:

Cubietruck mit Debian Wheezy -> uname -a:
Code: [Auswählen]
Linux cubie 3.4.61+ #2 SMP PREEMPT Sat Mar 8 11:16:50 UTC 2014 armv7l GNU/Linux

, VDR headless und Streamdev.
Code: [Auswählen]
vdr (2.0.5/2.0.0) - The Video Disk Recorder
streamdev-server (0.6.1-git) - VDR Streaming Server
mediaclient -e:
Code: [Auswählen]
**** List of Media Hardware Devices ****
device 0: [Sundtek SkyTV Ultimate IV]  DVB-S/S2, ANALOG-TV, REMOTE-CONTROL, OSS-AUDIO
  [INFO]:
     STATUS: ACTIVE
  [BUS]:
     ID: 2-1
  [SERIAL]:
     ID: U140919020324
  [DVB-S/S2]:
     FESTATUS: ACTIVE
     LNBVOLTAGE: ENABLED
     LNBSUPPLY: ACADAPTER
     LNBSTATUS: OK
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [ANALOG-TV]:
     VIDEO0: /dev/video0
     VBI0: /dev/vbi0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
  [OSS]:
     OSS0: /dev/dsp0

Sundtek Linux-Treiber vom 24.03.2015.


Seit vier Tagen habe ich die SkyTV Ultimate IV auf diesem System im Einsatz und bekomme immer wieder Ausfälle der Karte, welche in einem "Frontend timed out" resultieren.

Zuvor hatte ich bei identischem System und Konfiguration eine TT4600USB laufen, unter welcher diese Probleme NIE aufgetreten sind, die Probleme begannen mit der SkyTV-Karte.

Hinzufügen muss ich noch, dass die Karte an einem Unicable-System hängt (SCR6, 1980).
Die Unicable-Konfig wird über den VDR vorgenommen (scr.conf) und hat bis zum Kartenwechsel auch einwandfrei funktioniert.

Am System / VDR kann es nicht liegen, daher wäre es sinnvoll, wenn man über mediaclient Debug-Infos während des Streamdev-Betriebs im Unicable-Mode erhalten könnte.

Auffällig ist, dass nach einem reboot und damit nach einem "reset" der Karte alles wieder funktioniert.


...mit der freundlichen Bitte um Hilfe :)

P.S.: lsusb -v :

...hätte ich gerne nachgereicht, ABER:
Code: [Auswählen]
Fehler beim Schreiben des Beitrags.
Beitrag hat die max. Länge erreicht (20000 Zeichen).

What the ...?

...und eben wieder (14:16 Uhr):
Code: [Auswählen]
Apr  6 14:16:02 cubie vdr: [2371] frontend 0/0 timed out while tuning to channel 23, tp 111836
Apr  6 14:16:03 cubie vdr: [2373] Streamdev: Accepted new client (HTTP) 192.168.1.55:50411
Apr  6 14:16:03 cubie vdr: [2490] streamdev-writer thread started (pid=2367, tid=2490, prio=high)
Apr  6 14:16:03 cubie vdr: [2491] streamdev-livestreaming thread started (pid=2367, tid=2491, prio=high)
Apr  6 14:16:05 cubie vdr: [2492] receiver on device 1 thread started (pid=2367, tid=2492, prio=high)
Apr  6 14:16:06 cubie vdr: [2493] TS buffer on device 1 thread started (pid=2367, tid=2493, prio=high)
Apr  6 14:16:16 cubie vdr: [2371] frontend 0/0 timed out while tuning to channel 1, tp 110743
Apr  6 14:16:23 cubie vdr: [2373] client (HTTP) 192.168.1.55:50411 has closed connection
Apr  6 14:16:23 cubie vdr: [2373] streamdev-server: closing HTTP connection to 192.168.1.55:50411
Apr  6 14:16:23 cubie vdr: [2491] streamdev-livestreaming thread ended (pid=2367, tid=2491)
Apr  6 14:16:23 cubie vdr: [2490] streamdev-writer thread ended (pid=2367, tid=2490)
Apr  6 14:16:23 cubie vdr: [2373] buffer stats: 0 (0%) used
Apr  6 14:16:23 cubie vdr: [2373] Streamdev: Accepted new client (HTTP) 192.168.1.55:50415
Apr  6 14:16:23 cubie vdr: [2495] streamdev-livestreaming thread started (pid=2367, tid=2495, prio=high)
Apr  6 14:16:23 cubie vdr: [2494] streamdev-writer thread started (pid=2367, tid=2494, prio=high)
Apr  6 14:16:24 cubie vdr: [2493] TS buffer on device 1 thread ended (pid=2367, tid=2493)
Apr  6 14:16:24 cubie vdr: [2492] buffer stats: 0 (0%) used
Apr  6 14:16:24 cubie vdr: [2492] receiver on device 1 thread ended (pid=2367, tid=2492)
Apr  6 14:16:24 cubie vdr: [2496] receiver on device 1 thread started (pid=2367, tid=2496, prio=high)
Apr  6 14:16:26 cubie vdr: [2497] TS buffer on device 1 thread started (pid=2367, tid=2497, prio=high)
Apr  6 14:16:33 cubie vdr: [2371] frontend 0/0 timed out while tuning to channel 24, tp 111836

mediaclient -e:
Code: [Auswählen]
**** List of Media Hardware Devices ****
device 0: [Sundtek SkyTV Ultimate IV]  DVB-S/S2, ANALOG-TV, REMOTE-CONTROL, OSS-AUDIO
  [INFO]:
     STATUS: ACTIVE
  [BUS]:
     ID: 2-1
  [SERIAL]:
     ID: U140919020324
  [DVB-S/S2]:
     FESTATUS: ACTIVE
     LNBVOLTAGE: ENABLED
     LNBSUPPLY: ACADAPTER
     LNBSTATUS: OK
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [ANALOG-TV]:
     VIDEO0: /dev/video0
     VBI0: /dev/vbi0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
  [OSS]:
     OSS0: /dev/dsp0

dmesg:
Code: [Auswählen]
[   23.214588] usb 2-1: usbfs: process 775 (mediasrv) did not claim interface 0 before use

6
{Single, Dual, Quad} Sundtek SkyTV Ultimate / Re:Sky IV + vdr frontend timed out
« am: April 05, 2015, 11:21:29 Vormittag »
Hi,

ich habe genau das gleiche Problem auf meinem Cubietruck (Debian Wheezy, VDR headless mit streamdev-server). :)

Bei mir lief die Karte drei Tage ohne Probleme, dann gabs plötzlich Ruckler im Stream, bis schließlich gar nichts mehr ging. Meine Signal-Werte sind genau gleich zu deinen.

Immer, wenn ich versuche einen Kanal über den Streamdev aufzurufen, erhalte ich:
Code: [Auswählen]
vdr[1324]: [1328] frontend 0/0 timed out while tuning to channel 4 (arte), tp 110743
Apr 05 11:07:03  vdr[1324]: [1328] frontend 0/0 timed out while tuning to channel 4 (arte), tp 110743
Apr 05 11:08:08  vdr[1324]: [1328] frontend 0/0 timed out while tuning to channel 4 (arte), tp 110743
Apr 05 11:09:13  vdr[1324]: [1328] frontend 0/0 timed out while tuning to channel 4 (arte), tp 110743
Apr 05 11:10:18  vdr[1324]: [1328] frontend 0/0 timed out while tuning to channel 4 (arte), tp 110743
Apr 05 11:11:23  vdr[1324]: [1328] frontend 0/0 timed out while tuning to channel 4 (arte), tp 110743
Erneutes Aufrufen des Senders ergibt:

Code: [Auswählen]
Atelier vdr[1324]: [1643] buffer stats: 0 (0%) used
Apr 05 11:16:01 vdr[1324]: [1643] device 1 receiver thread ended (pid=1324, tid=1643)
Apr 05 11:16:01 vdr[1324]: [1647] device 1 receiver thread started (pid=1324, tid=1647, prio=high)
Apr 05 11:16:01 vdr[1324]: [1648] device 1 TS buffer thread started (pid=1324, tid=1648, prio=high)
Apr 05 11:16:10 vdr[1324]: [1328] frontend 0/0 timed out while tuning to channel 4 (arte), tp 110743
mediaclient -e:
Code: [Auswählen]
**** List of Media Hardware Devices ****
device 0: [Sundtek SkyTV Ultimate IV]  DVB-S/S2, ANALOG-TV, REMOTE-CONTROL, OSS-AUDIO
  [INFO]:
     STATUS: ACTIVE
  [BUS]:
     ID: 3-3
  [SERIAL]:
     ID: U140919020324
  [DVB-S/S2]:
     FESTATUS: ACTIVE
     LNBVOLTAGE: ENABLED
     LNBSUPPLY: ACADAPTER
     LNBSTATUS: OK
     FRONTEND: /dev/dvb/adapter0/frontend0
     DVR: /dev/dvb/adapter0/dvr0
     DMX: /dev/dvb/adapter0/demux0
  [ANALOG-TV]:
     VIDEO0: /dev/video0
     VBI0: /dev/vbi0
  [REMOTECONTROL]:
     INPUT0: /dev/mediainput0
  [OSS]:
     OSS0: /dev/dsp0
Ich werde später meine alte DVB-Karte (TT4600USB) anhängen und schauen, ob ich darüber ein Signal bekomme...dann ist zumindest das Problem bezüglich Kabel/VDR ausgeschlossen. :)

-> SIEHE http://support.sundtek.com/index.php/topic,1878.0.html  :)

Seiten: [1]