Beiträge von crow

crow · 18. Dezember 2013

Hat niemand so eine Karte oder ein Derivat im Einsatz? Irgendeine Idee etwas anderes zu probieren?
Anschauen von den Kanäle funktioniert natürlich ohne Probleme, falls ich das nicht geschrieben habe.

crow · 16. Dezember 2013

Bei meinem Freund funktioniert Motor Unterstützung unter VDR 2.1.2 nicht. Ich habe beide Technologien (USALS und DiSEqC) probiert, die sein Motor unterstützt, leider ohne Erfolg.
Es kann natürlich sein, dass es ein Treiber Thema ist, aber ich weiß nicht, was ich noch sonst probieren soll.

Es geht um DVBSky S960 [1] unter Archlinux x86_64 Distribution, und VDR Development Version 2.1.2.
Auf der Produkt Seite sind einige Features:
. DiSEqC 1.2/2.0 & USALS Support
. Support Linux VDR, i.e. CNVDR

Kernel ist "Linux vdrbox 3.9.3-1" und der Treiber, der offiziell auf der Support Seite aufgelistet ist [2] media_build-bst-130806.
Dmesg zeigt folgendes:

Zitat

[ 7.395367] usb 1-1: dvb_usb_v2: found a 'DVBSky S960/S860' in warm state
[ 7.395529] usb 1-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 7.395566] DVB: registering new adapter (DVBSky S960/S860)
[ 7.395673] usbcore: registered new interface driver dvb_usb_dvbsky
[ 7.396969] dvbsky_usb MAC address=00:17:42:54:96:0c
[ 7.396982] usb 1-1: dvb_usb_v2: MAC address: 00:17:42:54:96:0c
[ 7.524599] DS3000 chip version: d0 attached.
[ 7.525841] TS202x chip version[1]: c1 attached.
[ 7.537721] TS202x chip version[2]: c3 attached.
[ 7.580383] m88ds3103_load_firmware: Waiting for firmware upload (dvb-fe-ds3103.fw)...
[ 7.691546] m88ds3103_load_firmware: Waiting for firmware upload(2)...
[ 8.753594] usb 1-1: DVB: registering adapter 0 frontend 0 (Montage DS3103/TS2022)...
[ 9.000010] Registered IR keymap rc-dvbsky
[ 9.000207] input: DVBSky S960/S860 as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/rc/rc0/input14
[ 9.000340] rc0: DVBSky S960/S860 as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/rc/rc0
[ 9.000351] usb 1-1: dvb_usb_v2: schedule remote query interval to 300 msecs
[ 9.000359] usb 1-1: dvb_usb_v2: 'DVBSky S960/S860' successfully initialized and connected

Alles anzeigen

DVB Karte in devices:

Zitat

[skydvbs@vdrbox ~]$ ls -ltr /dev/dvb/
total 0
drwxr-xr-x 2 root root 120 Dec 16 10:32 adapter0 [skydvbs@vdrbox ~]$
ls -ltr /dev/dvb/adapter0/ total 0
crw-rw---- 1 root video 212, 5 Dec 16 10:32 dvr0
crw-rw---- 1 root video 212, 7 Dec 16 10:32 net0
crw-rw---- 1 root video 212, 4 Dec 16 10:32 demux0
crw-rw---- 1 root video 212, 3 Dec 16 10:32 frontend0
[skydvbs@vdrbox~]$

Alles anzeigen

diseqc.conf

Zitat

#S360E 11700 V 9750 t V W20 P W20 t v
#S360E 99999 V 10600 t V W20 P W20 T v
#S360E 11700 H 9750 t V W20 P W20 t V
#S360E 99999 H 10600 t V W20 P W20 T V

#1 Eutelsat Hot Bird 13A/13B/13C
S13.0E 11700 V 9750 t v W15 P1 W15 t
S13.0E 99999 V 10600 t v W15 P1 W15 T
S13.0E 11700 H 9750 t V W15 P1 W15 t
S13.0E 99999 H 10600 t V W15 P1 W15 T
#2 Astra 1KR/1L/1M/2C
S19.2E 11700 V 9750 t v W15 P2 W15 t
S19.2E 99999 V 10600 t v W15 P2 W15 T
S19.2E 11700 H 9750 t V W15 P2 W15 t
S19.2E 99999 H 10600 t V W15 P2 W15 T

Alles anzeigen

Setup.conf

Zitat

DiSEqC = 1
LnbFrequHi = 10600
LnbFrequLo = 9750
LnbSLOF = 11700
SiteLat = 453
SiteLon = 72
PrimaryDVB = 2

Alles anzeigen

Motor wird manchmal angesteuert, wenn ich VDR neue starte, aber nicht immer, und das passiert bei USALS und DiSEqC Technologie.

Hat Jemand vielleicht noch eine Idee was ich hier probieren kann?
Bin für jede Antwort dankbar.

[1] http://www.dvbsky.net/Products_S960.html
[2] http://www.dvbsky.net/download…a_build-bst-130806.tar.gz

crow · 13. November 2013

Es funktioniert mit fix eingetragenem evmap Name in der 98-eventlircd.rules.

Folgenden Anpassung habe ich noch an der Datei remote.conf gemacht:

Zitat

LIRC.Up KEY_UP
LIRC.Down KEY_DOWN
LIRC.Menu KEY_MENU
LIRC.Ok KEY_OK
LIRC.Back KEY_ESC
LIRC.Left KEY_LEFT
LIRC.Right KEY_RIGHT
LIRC.Red KEY_F1
LIRC.Green KEY_F2
LIRC.Yellow KEY_F3
LIRC.Blue KEY_F4
LIRC.0 KEY_0
LIRC.1 KEY_1
LIRC.2 KEY_2
LIRC.3 KEY_3
LIRC.4 KEY_4
LIRC.5 KEY_5
LIRC.6 KEY_6
LIRC.7 KEY_7
LIRC.8 KEY_8
LIRC.9 KEY_9
LIRC.Info KEY_INFO
LIRC.Play KEY_PLAY
LIRC.Pause KEY_PAUSE
LIRC.Stop KEY_STOP
LIRC.Record KEY_RECORD
LIRC.FastFwd KEY_FASTFORWARD
LIRC.FastRew KEY_REWIND
LIRC.Next KEY_NEXT
LIRC.Back KEY_BACK
LIRC.Power KEY_POWER
LIRC.Channel+ KEY_CHANNELUP
LIRC.Channel- KEY_CHANNELDOWN
LIRC.PrevChannel KEY_PREVIOUS
LIRC.Volume+ KEY_VOLUMEUP
LIRC.Volume- KEY_VOLUMEDOWN
LIRC.Mute KEY_MUTE
LIRC.Subtitles KEY_SUBTITLE
LIRC.Schedule KEY_EPG
LIRC.Channels KEY_CHANNEL
LIRC.Commands KEY_FAVORITES
LIRC.Audio KEY_AUDIO
LIRC.Timers KEY_TIME
LIRC.Recordings KEY_PVR
LIRC.Setup KEY_SETUP
LIRC.User0 KEY_TEXT
LIRC.User1 KEY_PROG1
LIRC.User2 KEY_PROG2
LIRC.User3 KEY_PROG3
LIRC.User4 KEY_PROG4
LIRC.User5 KEY_AUDIO
LIRC.User6 KEY_VIDEO
LIRC.User7 KEY_IMAGES
LIRC.User8 KEY_FN
LIRC.User9 KEY_SCREEN

Alles anzeigen

crow · 12. November 2013

Bei udev monitoring mit "udevadm monitor --environment --udev" sehe ich folgendes:

Zitat

UDEV [426.216733] add /devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input9 (input)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input9
EV=3
ID_FOR_SEAT=input-pci-0000_00_04_1-usb-0_3
ID_INPUT=1
ID_INPUT_KEY=1
ID_PATH=pci-0000:00:04.1-usb-0:3
ID_PATH_TAG=pci-0000_00_04_1-usb-0_3
ID_SERIAL=noserial
KEY=6c0904 2470c100000000 0 800010000 19040000840 1e168000000001 f800000000000ffc
MODALIAS=input:b0003v9022pD650e0000-e0,1,k71,72,73,74,86,8B,9E,A4,A7,A8,D0,E3,160,166,167,16C,16D,16E,172,175,182,188,18B,192,193,195,196,ramlsfw
NAME="IR-receiver inside an USB DVB receiver"
PHYS="usb-0000:00:04.1-3/ir0"
PRODUCT=3/9022/d650/0
PROP=0
SEQNUM=1634
SUBSYSTEM=input
TAGS=:seat:
USEC_INITIALIZED=6201401

UDEV [426.292712] add /devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input9/event3 (input)
ACTION=add
DEVLINKS=/dev/input/by-path/pci-0000:00:04.1-usb-0:3-event-ir /dev/input/ira
DEVNAME=/dev/input/event3
DEVPATH=/devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input9/event3
ID_INPUT=1
ID_INPUT_KEY=1
ID_PATH=pci-0000:00:04.1-usb-0:3
ID_PATH_TAG=pci-0000_00_04_1-usb-0_3
ID_SERIAL=noserial
MAJOR=13
MINOR=67
SEQNUM=1635
SUBSYSTEM=input
USEC_INITIALIZED=1514
eventlircd_enable=true
eventlircd_evmap=03__.evmap

Alles anzeigen

mit fix eingetragenem evmap Name "03_9022_d650.evmap" schaut es viel besser aus:

Zitat

SUBSYSTEM=="input", ATTRS{idVendor}=="9022", \
ENV{eventlircd_enable}="true", \
ENV{eventlircd_evmap}="03_9022_d650.evmap"

Zitat

UDEV [836.120218] add /devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input10 (input)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input10
EV=3
ID_FOR_SEAT=input-pci-0000_00_04_1-usb-0_3
ID_INPUT=1
ID_INPUT_KEY=1
ID_PATH=pci-0000:00:04.1-usb-0:3
ID_PATH_TAG=pci-0000_00_04_1-usb-0_3
ID_SERIAL=noserial
KEY=6c0904 2470c100000000 0 800010000 19040000840 1e168000000001 f800000000000ffc
MODALIAS=input:b0003v9022pD650e0000-e0,1,k71,72,73,74,86,8B,9E,A4,A7,A8,D0,E3,160,166,167,16C,16D,16E,172,175,182,188,18B,192,193,195,196,ramlsfw
NAME="IR-receiver inside an USB DVB receiver"
PHYS="usb-0000:00:04.1-3/ir0"
PRODUCT=3/9022/d650/0
PROP=0
SEQNUM=1652
SUBSYSTEM=input
TAGS=:seat:
USEC_INITIALIZED=6103832

UDEV [836.196289] add /devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input10/event3 (input)
ACTION=add
DEVLINKS=/dev/input/by-path/pci-0000:00:04.1-usb-0:3-event-ir /dev/input/ira
DEVNAME=/dev/input/event3
DEVPATH=/devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input10/event3
ID_INPUT=1
ID_INPUT_KEY=1
ID_PATH=pci-0000:00:04.1-usb-0:3
ID_PATH_TAG=pci-0000_00_04_1-usb-0_3
ID_SERIAL=noserial
MAJOR=13
MINOR=67
SEQNUM=1653
SUBSYSTEM=input
USEC_INITIALIZED=4380
eventlircd_enable=true
eventlircd_evmap=03_9022_d650.evmap

Alles anzeigen

Test läuft.

crow · 12. November 2013

Die zwei alten Posts wurden aktualisiert!
Die Dateien 98-eventlircd-names.rules und 98-eventlircd.rules habe ich von yavdr-remote übernommen. Der Eintrag aus dem zweiten Post wurde unter anysee.evmap hinzugefügt.

Ausgabe von udevadm

Zitat

# udevadm info --query=all --attribute-walk --name=/dev/input/ira

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device '/devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input3/event3':
KERNEL=="event3"
SUBSYSTEM=="input"
DRIVER==""

looking at parent device '/devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input3':
KERNELS=="input3"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="IR-receiver inside an USB DVB receiver"
ATTRS{phys}=="usb-0000:00:04.1-3/ir0"
ATTRS{uniq}==""
ATTRS{properties}=="0"

looking at parent device '/devices/pci0000:00/0000:00:04.1/usb1/1-3':
KERNELS=="1-3"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="3"
ATTRS{idVendor}=="9022"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="2"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0000"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="2407"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Cypress"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="d650"
ATTRS{bDeviceClass}=="00"
ATTRS{product}=="EZ-USB FX2"

looking at parent device '/devices/pci0000:00/0000:00:04.1/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="6"
ATTRS{bcdDevice}=="0311"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:04.1"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="32"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.11.6-1-ARCH ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"

looking at parent device '/devices/pci0000:00/0000:00:04.1':
KERNELS=="0000:00:04.1"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="21"
ATTRS{subsystem_vendor}=="0x10de"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,0000000f"
ATTRS{device}=="0x0aa6"
ATTRS{uframe_periodic_max}=="100"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-3"
ATTRS{vendor}=="0x10de"
ATTRS{subsystem_device}=="0xcb79"
ATTRS{numa_node}=="-1"
ATTRS{d3cold_allowed}=="1"

looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""

#

Alles anzeigen

In der Datei /etc/eventlircd.d/03_9022_d650.evmap is folgendes. Übernommen von tevii s650 tastenbelegung

Code

1	=	KEY_1
2	=	KEY_2
3	=	KEY_3
4	=	KEY_4
5	=	KEY_5
6	=	KEY_6
7	=	KEY_7
8	=	KEY_8
9	=	KEY_9
0	=	KEY_0
F1	=	KEY_RED 
F2	=	KEY_GREEN 
F3	=	KEY_YELLOW
F4	=	KEY_BLUE
F5	=	KEY_FN
F6	=	KEY_SCREEN
Up	=	KEY_UP
Left	=	KEY_LEFT
Right	=	KEY_RIGHT
Down	=	KEY_DOWN
Mute	=	KEY_MUTE
VolumeDown	=	KEY_VOLUMEDOWN
VolumeUp	=	KEY_VOLUMEUP
Power	=	KEY_POWER2
Open	=	KEY_OPEN
Menu	=	KEY_MENU
Back	=	KEY_ESC
PlayPause	=	KEY_PAUSE
Record	=	KEY_RECORD
Rewind	=	KEY_REWIND
Fast Forward	=	KEY_FASTFORWARD		
Ok	=	KEY_OK
Info	=	KEY_INFO
Time	=	KEY_TIME
Favorites	=	KEY_FAVORITES
EPG	=	KEY_EPG
PVR	=	KEY_PVR
Subtitle	=	KEY_SUBTITLE
Mode	=	KEY_MODE
Tuner	=	KEY_TUNER
Audio	=	KEY_AUDIO
List	=	KEY_CHANNEL
ChannelUp	=	KEY_CHANNELUP
ChannelDown	=	KEY_CHANNELDOWN
Last	=	KEY_PREV
AB	=	KEY_TEXT

Alles anzeigen

crow · 24. Oktober 2013

Hallo,
Kann mir jemand hier helfen, wie ich diseqc.conf, die ich mit dem VDR 1.7.* benutzt habe, auf VDR 2.1.2 umstelle um motorisierte Satschüssel zu verwenden.

Zitat

#1 Eutelsat Hot Bird 13A/13B/13C
S13.0E 11700 V 9750 t v W15 [E0 31 6B 01] W1 [E0 31 6B 01] W1 [E0 31 6B 01] W15 t
S13.0E 99999 V 10600 t v W15 [E0 31 6B 01] W1 [E0 31 6B 01] W1 [E0 31 6B 01] W15 T
S13.0E 11700 H 9750 t V W15 [E0 31 6B 01] W1 [E0 31 6B 01] W1 [E0 31 6B 01] W15 t
S13.0E 99999 H 10600 t V W15 [E0 31 6B 01] W1 [E0 31 6B 01] W1 [E0 31 6B 01] W15 T
#2 Astra 1KR/1L/1M/2C
S19.2E 11700 V 9750 t v W15 [E0 31 6B 02] W1 [E0 31 6B 02] W1 [E0 31 6B 02] W15 t
S19.2E 99999 V 10600 t v W15 [E0 31 6B 02] W1 [E0 31 6B 02] W1 [E0 31 6B 02] W15 T
S19.2E 11700 H 9750 t V W15 [E0 31 6B 02] W1 [E0 31 6B 02] W1 [E0 31 6B 02] W15 t
S19.2E 99999 H 10600 t V W15 [E0 31 6B 02] W1 [E0 31 6B 02] W1 [E0 31 6B 02] W15 T
#3 Eutelsat 16A
S16.0E 11700 V 9750 t v W15 [E0 31 6B 03] W1 [E0 31 6B 03] W1 [E0 31 6B 03] W15 t
S16.0E 99999 V 10600 t v W15 [E0 31 6B 03] W1 [E0 31 6B 03] W1 [E0 31 6B 03] W15 T
S16.0E 11700 H 9750 t V W15 [E0 31 6B 03] W1 [E0 31 6B 03] W1 [E0 31 6B 03] W15 t
S16.0E 99999 H 10600 t V W15 [E0 31 6B 03] W1 [E0 31 6B 03] W1 [E0 31 6B 03] W15 T
#4 Astra 3B
S23.5E 11700 V 9750 t v W15 [E0 31 6B 04] W1 [E0 31 6B 04] W1 [E0 31 6B 04] W15 t
S23.5E 99999 V 10600 t v W15 [E0 31 6B 04] W1 [E0 31 6B 04] W1 [E0 31 6B 04] W15 T
S23.5E 11700 H 9750 t V W15 [E0 31 6B 04] W1 [E0 31 6B 04] W1 [E0 31 6B 04] W15 t
S23.5E 99999 H 10600 t V W15 [E0 31 6B 04] W1 [E0 31 6B 04] W1 [E0 31 6B 04] W15 T
#6 Eutelsat 28A & Astra 1N/2A/2B
S28.2E 11700 V 9750 t v W15 [E0 31 6B 06] W1 [E0 31 6B 06] W1 [E0 31 6B 06] W15 t
S28.2E 99999 V 10600 t v W15 [E0 31 6B 06] W1 [E0 31 6B 06] W1 [E0 31 6B 06] W15 T
S28.2E 11700 H 9750 t V W15 [E0 31 6B 06] W1 [E0 31 6B 06] W1 [E0 31 6B 06] W15 t
S28.2E 99999 H 10600 t V W15 [E0 31 6B 06] W1 [E0 31 6B 06] W1 [E0 31 6B 06] W15 T
#5 Hellas Sat 2
S39.0E 11700 V 9750 t v W15 [E0 31 6B 05] W1 [E0 31 6B 05] W1 [E0 31 6B 05] W15 t
S39.0E 99999 V 10600 t v W15 [E0 31 6B 05] W1 [E0 31 6B 05] W1 [E0 31 6B 05] W15 T
S39.0E 11700 H 9750 t V W15 [E0 31 6B 05] W1 [E0 31 6B 05] W1 [E0 31 6B 05] W15 t
S39.0E 99999 H 10600 t V W15 [E0 31 6B 05] W1 [E0 31 6B 05] W1 [E0 31 6B 05] W15 T
#9 Hispasat
S30.0W 11700 V 9750 t v W15 [E0 31 6B 11] W1 [E0 31 6B 11] W1 [E0 31 6B 11] W15 t
S30.0W 99999 V 10600 t v W15 [E0 31 6B 11] W1 [E0 31 6B 11] W1 [E0 31 6B 11] W15 T
S30.0W 11700 H 9750 t V W15 [E0 31 6B 11] W1 [E0 31 6B 11] W1 [E0 31 6B 11] W15 t
S30.0W 99999 H 10600 t V W15 [E0 31 6B 11] W1 [E0 31 6B 11] W1 [E0 31 6B 11] W15 T
#8 Thor
S1.0W 11700 V 9750 t v W15 [E0 31 6B 07] W1 [E0 31 6B 07] W1 [E0 31 6B 07] W15 t
S1.0W 99999 V 10600 t v W15 [E0 31 6B 07] W1 [E0 31 6B 07] W1 [E0 31 6B 07] W15 T
S1.0W 11700 H 9750 t V W15 [E0 31 6B 07] W1 [E0 31 6B 07] W1 [E0 31 6B 07] W15 t
S1.0W 99999 H 10600 t V W15 [E0 31 6B 07] W1 [E0 31 6B 07] W1 [E0 31 6B 07] W15 T

Alles anzeigen

crow · 30. Mai 2013

Mit folgender 98-eventlircd.rules Regel versuche ich meinen Empfänger, der als HID-Device erkannt wurde, zu eventlircd zu mappen.

Zitat

SUBSYSTEM=="input", ATTRS{idVendor}=="9022", ATTRS{idProduct}=="d650", \
ENV{eventlircd_enable}="true", \
ENV{eventlircd_evmap}="03_$env{ID_VENDOR_ID}_$env{ID_MODEL_ID}.evmap"

Trotzdem findet ir-keytable immer noch nichts.

crow · 27. Mai 2013

Aktualisiert am 12.11.2013 20:30
Ich wollte wieder versuchen die Fernbedienung der Tevii S650 USB zum Laufen zu bringen.
Distribution: archlinux x86_64 (Linux vdrbox 3.11.6-1-ARCH) letzte update am 12.11.2013 20:00 durchgeführt.
App: eventlircd
Hardware: Tevii S650 USB eingebauter IR und Fernbedienung

In der Datei /etc/udev/rules.d/10-local.rules habe ich diesen Eintrag gemacht:

Zitat

KERNEL=="event*",ATTRS{phys}=="usb-0000:00:04.1-3/ir0",SYMLINK+="input/ira"

Im Verzeichnis "/dev/input/" ist der Name ira neben event3 zu finden.

Zitat

# ls -ltr /dev/input/ | grep -i ira
lrwxrwxrwx 1 root root 6 Nov 12 20:44 ira -> event3

Bei mir findet ir-keytable den Empfänger nicht:

Zitat

# ir-keytable
Couldn't find any node at /sys/class/rc/rc*.

Ausgabe von cat /proc/bus/input/devices erkennt den Fernbedienungsempfänger aber schon:

Zitat

I: Bus=0003 Vendor=9022 Product=d650 Version=0000
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:00:04.1-3/ir0
S: Sysfs=/devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=6c0904 2470c100000000 0 800010000 19040000840 1e168000000001 f800000000000ffc

Alles anzeigen

Ich nehme an mein Empfänger wird als HID Device erkannt.

crow · 26. Mai 2013

Es schaut genau so aus wie im wiki. Für mich schaut auch so aus als das kein RC6-Code sind...
CIR is auf RC6 umgestellt über ir-keytable. Wenn ich auf andere protokole umstelle und test versuche passiert nicht.
Wirklich seltsam...

crow · 26. Mai 2013

Irgendwie sind mehr als helfte von code die selbe.. Ist das normal?
Das sind knopf von 0 - 9:

Code

[]# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1369519583.197873: event type EV_MSC(0x04): scancode = 0x1001
1369519583.197873: event type EV_SYN(0x00).
1369519598.240119: event type EV_MSC(0x04): scancode = 0x800
1369519598.240119: event type EV_SYN(0x00).
1369519604.669494: event type EV_MSC(0x04): scancode = 0x80
1369519604.669494: event type EV_SYN(0x00).
1369519617.521728: event type EV_MSC(0x04): scancode = 0x04
1369519617.521728: event type EV_SYN(0x00).
1369519624.089665: event type EV_MSC(0x04): scancode = 0x20
1369519624.089665: event type EV_SYN(0x00).
1369519629.177840: event type EV_MSC(0x04): scancode = 0x20
1369519629.177840: event type EV_SYN(0x00).
1369519639.719886: event type EV_MSC(0x04): scancode = 0x10
1369519639.719886: event type EV_SYN(0x00).
1369519644.780316: event type EV_MSC(0x04): scancode = 0x20
1369519644.780316: event type EV_SYN(0x00).
1369519654.788546: event type EV_MSC(0x04): scancode = 0x20
1369519654.788546: event type EV_SYN(0x00).
1369519659.419282: event type EV_MSC(0x04): scancode = 0x20
1369519659.419282: event type EV_SYN(0x00).
^C
[]#

Alles anzeigen

crow · 25. Mai 2013

Das schaut gut aus..

Code

[]# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1369511620.715525: event type EV_MSC(0x04): scancode = 0x40
1369511620.715525: event type EV_KEY(0x01) key_down: KEY_OK(0x0001)
1369511620.715525: event type EV_SYN(0x00).
1369511620.964634: event type EV_KEY(0x01) key_up: KEY_OK(0x0001)
1369511620.964634: event type EV_SYN(0x00).
1369511622.752185: event type EV_MSC(0x04): scancode = 0x08
1369511622.752185: event type EV_KEY(0x01) key_down: KEY_DOWN(0x0001)
1369511622.752185: event type EV_SYN(0x00).
1369511623.001307: event type EV_KEY(0x01) key_up: KEY_DOWN(0x0001)
1369511623.001307: event type EV_SYN(0x00).
1369511631.478100: event type EV_MSC(0x04): scancode = 0x04
1369511631.478100: event type EV_KEY(0x01) key_down: KEY_UP(0x0001)
1369511631.478100: event type EV_SYN(0x00).
1369511631.727964: event type EV_KEY(0x01) key_up: KEY_UP(0x0001)
1369511631.727964: event type EV_SYN(0x00).
^C
[]#

Alles anzeigen

Ich weiß nicht welche ganu profil ich dafür brauche. Ist ein Orginal XBOX360 Fernbedinung, und CIR die mit ASRock ION 330HT geliefert worden ist.

crow · 25. Mai 2013

Nein es klappt auch nicht wenn ich laden erwzirge:

Code

[root@vdrbox rules.d]# ir-keytable -c -w /etc/rc_keymaps/xbox360-mce
Read xbox-mce table
Old keytable cleared
Wrote 95 keycode(s) to driver
Protocols changed to RC-6
[root@vdrbox rules.d]# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1369508035.097117: event type EV_MSC(0x04): scancode = 0x40
1369508035.097117: event type EV_SYN(0x00).
1369508036.992988: event type EV_MSC(0x04): scancode = 0x04
1369508036.992988: event type EV_SYN(0x00).
1369508080.945536: event type EV_MSC(0x04): scancode = 0x08
1369508080.945536: event type EV_SYN(0x00).
^C


[root@vdrbox rules.d]# nano /etc/rc_keymaps/xbox360-mce
[root@vdrbox rules.d]# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event2) with:
    	Driver nuvoton-cir, table rc-rc6-mce
    	Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
    	Enabled protocols: RC-6
    	Name: Nuvoton w836x7hg Infrared Remote
    	bus: 25, vendor/product: 1050:00b4, version: 0x0073
    	Repeat delay = 500 ms, repeat period = 125 ms
[root@vdrbox rules.d]# ir-keytable -c -w /etc/rc_keymaps/xbox360-mce
Read rc-rc6-mce table
Old keytable cleared
Wrote 95 keycode(s) to driver
Protocols changed to RC-6


[root@vdrbox rules.d]# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event2) with:
    	Driver nuvoton-cir, table rc-rc6-mce
    	Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
    	Enabled protocols: RC-6
    	Name: Nuvoton w836x7hg Infrared Remote
    	bus: 25, vendor/product: 1050:00b4, version: 0x0073
    	Repeat delay = 500 ms, repeat period = 125 ms
[root@vdrbox rules.d]# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1369508154.973194: event type EV_MSC(0x04): scancode = 0x40
1369508154.973194: event type EV_SYN(0x00).
1369508158.167395: event type EV_MSC(0x04): scancode = 0x08
1369508158.167395: event type EV_SYN(0x00).
1369508160.666121: event type EV_MSC(0x04): scancode = 0x08
1369508160.666121: event type EV_SYN(0x00).
^C

Alles anzeigen

in anhang ist xbox360-mce file.

crow · 25. Mai 2013

Ja eventlircd ist gestoppt:

Code

[# ir-keytable -t
[root@vdrbox rules.d]# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1369505736.128355: event type EV_MSC(0x04): scancode = 0x10
1369505736.128355: event type EV_SYN(0x00).
1369505750.907827: event type EV_MSC(0x04): scancode = 0x08
1369505750.907827: event type EV_SYN(0x00).
^C
[root@vdrbox rules.d]# evtest /dev/input/event3
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "MCE IR Keyboard/Mouse (nuvoton-cir)"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
	Event code 1 (KEY_ESC)
	Event code 2 (KEY_1)
	Event code 3 (KEY_2)
	Event code 4 (KEY_3)
	Event code 5 (KEY_4)
	Event code 6 (KEY_5)
	Event code 7 (KEY_6)
	Event code 8 (KEY_7)
	Event code 9 (KEY_8)
	Event code 10 (KEY_9)
	Event code 11 (KEY_0)
	Event code 12 (KEY_MINUS)
	Event code 13 (KEY_EQUAL)
	Event code 14 (KEY_BACKSPACE)
	Event code 15 (KEY_TAB)
	Event code 16 (KEY_Q)
	Event code 17 (KEY_W)
	Event code 18 (KEY_E)
	Event code 19 (KEY_R)
	Event code 20 (KEY_T)
	Event code 21 (KEY_Y)
	Event code 22 (KEY_U)
	Event code 23 (KEY_I)
	Event code 24 (KEY_O)
	Event code 25 (KEY_P)
	Event code 26 (KEY_LEFTBRACE)
	Event code 27 (KEY_RIGHTBRACE)
	Event code 28 (KEY_ENTER)
	Event code 29 (KEY_LEFTCTRL)
	Event code 30 (KEY_A)
	Event code 31 (KEY_S)
	Event code 32 (KEY_D)
	Event code 33 (KEY_F)
	Event code 34 (KEY_G)
	Event code 35 (KEY_H)
	Event code 36 (KEY_J)
	Event code 37 (KEY_K)
	Event code 38 (KEY_L)
	Event code 39 (KEY_SEMICOLON)
	Event code 40 (KEY_APOSTROPHE)
	Event code 41 (KEY_GRAVE)
	Event code 42 (KEY_LEFTSHIFT)
	Event code 43 (KEY_BACKSLASH)
	Event code 44 (KEY_Z)
	Event code 45 (KEY_X)
	Event code 46 (KEY_C)
	Event code 47 (KEY_V)
	Event code 48 (KEY_B)
	Event code 49 (KEY_N)
	Event code 50 (KEY_M)
	Event code 51 (KEY_COMMA)
	Event code 52 (KEY_DOT)
	Event code 53 (KEY_SLASH)
	Event code 54 (KEY_RIGHTSHIFT)
	Event code 55 (KEY_KPASTERISK)
	Event code 56 (KEY_LEFTALT)
	Event code 57 (KEY_SPACE)
	Event code 58 (KEY_CAPSLOCK)
	Event code 59 (KEY_F1)
	Event code 60 (KEY_F2)
	Event code 61 (KEY_F3)
	Event code 62 (KEY_F4)
	Event code 63 (KEY_F5)                                                                                                 	[65/2665]
	Event code 64 (KEY_F6)
	Event code 65 (KEY_F7)
	Event code 66 (KEY_F8)
	Event code 67 (KEY_F9)
	Event code 68 (KEY_F10)
	Event code 69 (KEY_NUMLOCK)
	Event code 70 (KEY_SCROLLLOCK)
	Event code 71 (KEY_KP7)
	Event code 72 (KEY_KP8)
	Event code 73 (KEY_KP9)
	Event code 74 (KEY_KPMINUS)
	Event code 75 (KEY_KP4)
	Event code 76 (KEY_KP5)
	Event code 77 (KEY_KP6)
	Event code 78 (KEY_KPPLUS)
	Event code 79 (KEY_KP1)
	Event code 80 (KEY_KP2)
	Event code 81 (KEY_KP3)
	Event code 82 (KEY_KP0)
	Event code 83 (KEY_KPDOT)
	Event code 85 (KEY_ZENKAKUHANKAKU)
	Event code 86 (KEY_102ND)
	Event code 87 (KEY_F11)
	Event code 88 (KEY_F12)
	Event code 89 (KEY_RO)
	Event code 90 (KEY_KATAKANA)
	Event code 91 (KEY_HIRAGANA)
	Event code 92 (KEY_HENKAN)
	Event code 93 (KEY_KATAKANAHIRAGANA)
	Event code 94 (KEY_MUHENKAN)
	Event code 95 (KEY_KPJPCOMMA)
	Event code 96 (KEY_KPENTER)
	Event code 97 (KEY_RIGHTCTRL)
	Event code 98 (KEY_KPSLASH)
	Event code 99 (KEY_SYSRQ)
	Event code 100 (KEY_RIGHTALT)
	Event code 102 (KEY_HOME)
	Event code 103 (KEY_UP)
	Event code 104 (KEY_PAGEUP)
	Event code 105 (KEY_LEFT)
	Event code 106 (KEY_RIGHT)
	Event code 107 (KEY_END)
	Event code 108 (KEY_DOWN)
	Event code 109 (KEY_PAGEDOWN)
	Event code 110 (KEY_INSERT)                                                                                            	[20/2665]
	Event code 111 (KEY_DELETE)
	Event code 113 (KEY_MUTE)
	Event code 114 (KEY_VOLUMEDOWN)
	Event code 115 (KEY_VOLUMEUP)
	Event code 116 (KEY_POWER)
	Event code 117 (KEY_KPEQUAL)
	Event code 119 (KEY_PAUSE)
	Event code 121 (KEY_KPCOMMA)
	Event code 122 (KEY_HANGUEL)
	Event code 123 (KEY_HANJA)
	Event code 124 (KEY_YEN)
	Event code 125 (KEY_LEFTMETA)
	Event code 126 (KEY_RIGHTMETA)
	Event code 127 (KEY_COMPOSE)
	Event code 128 (KEY_STOP)
	Event code 129 (KEY_AGAIN)
	Event code 130 (KEY_PROPS)
	Event code 131 (KEY_UNDO)
	Event code 132 (KEY_FRONT)
	Event code 133 (KEY_COPY)
	Event code 134 (KEY_OPEN)
	Event code 135 (KEY_PASTE)
	Event code 136 (KEY_FIND)
	Event code 137 (KEY_CUT)
	Event code 138 (KEY_HELP)
	Event code 140 (KEY_CALC)
	Event code 142 (KEY_SLEEP)
	Event code 150 (KEY_WWW)
	Event code 152 (KEY_SCREENLOCK)
	Event code 158 (KEY_BACK)
	Event code 159 (KEY_FORWARD)
	Event code 161 (KEY_EJECTCD)
	Event code 163 (KEY_NEXTSONG)
	Event code 164 (KEY_PLAYPAUSE)
	Event code 165 (KEY_PREVIOUSSONG)
	Event code 166 (KEY_STOPCD)
	Event code 173 (KEY_REFRESH)
	Event code 176 (KEY_EDIT)
	Event code 177 (KEY_SCROLLUP)
	Event code 178 (KEY_SCROLLDOWN)
	Event code 183 (KEY_F13)
	Event code 184 (KEY_F14)
	Event code 185 (KEY_F15)
	Event code 186 (KEY_F16)
	Event code 187 (KEY_F17)
	Event code 188 (KEY_F18)
	Event code 189 (KEY_F19)
	Event code 190 (KEY_F20)
	Event code 191 (KEY_F21)
	Event code 192 (KEY_F22)
	Event code 193 (KEY_F23)
	Event code 194 (KEY_F24)
	Event code 272 (BTN_LEFT)
	Event code 273 (BTN_RIGHT)
    Event type 2 (EV_REL)
	Event code 0 (REL_X)
	Event code 1 (REL_Y)
    Event type 4 (EV_MSC)
	Event code 4 (MSC_SCAN)
  Event type 20 (EV_REP)
Properties:
Testing ... (interrupt to exit)
^C


[]#

Alles anzeigen

Bei evtest passiert nichts, und auch wenn eventlircd gestartet ist und mit VDR auf tasten drück passiert nichts.

crow · 25. Mai 2013

Hallo wieder,

Muss wieder mich mit dem beschäftigen. Noch immer habe
ich das Problem, CIR mit XBOX360 remote zu verbinden und mit VDR/XBMC zu
nutzen. Habe in zwischen zeit Medion X10 benutzt, leider nach zwei Monate ist Fernbedienung kaputt gegangen, und bis es neue kommt muss ich abwarten).

zur hardware:

Code

cat /proc/bus/input/devices
.
.
I: Bus=0019 Vendor=1050 Product=00b4 Version=0073
N: Name="Nuvoton w836x7hg Infrared Remote Transceiver"
P: Phys=nuvoton/cir0
S: Sysfs=/devices/pnp0/00:03/rc/rc0/input2
U: Uniq=
H: Handlers=kbd event2
B: PROP=0
B: EV=100013
B: KEY=108fc010 2478d100000000 0 18c00 18040302801 8e168000000000 ffe
B: MSC=10


I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="MCE IR Keyboard/Mouse (nuvoton-cir)"
P: Phys=/input0
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=kbd mouse0 event3
B: PROP=0
B: EV=100017
B: KEY=30000 7 ff87207ac14057ff febeffdfffefffff fffffffffffffffe
B: REL=3
B: MSC=10


.
.
.

Alles anzeigen

Code

[]# dmesg | grep nuvoton
[	7.021544] nuvoton_cir: driver has been successfully loaded
[	7.059438] input: MCE IR Keyboard/Mouse (nuvoton-cir) as /devices/virtual/input/input3
[	7.075431] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0


[]# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event3) with:
    	Driver nuvoton-cir, table rc-rc6-mce
    	Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
    	Enabled protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
    	Name: Nuvoton w836x7hg Infrared Remote
    	bus: 25, vendor/product: 1050:00b4, version: 0x0073
    	Repeat delay = 500 ms, repeat period = 125 ms
[]#

Alles anzeigen

Dann habe ich eventlircd installiert mit /etc/systemd/system/eventlircd.service

Code

[Unit]
Description=Eventlircd Daemon
After=systemd-udevd.service


[Service]
Type=forking
ExecStartPre=/bin/mkdir -p /run/lirc
ExecStartPre=/bin/rm -f /dev/lircd
ExecStartPre=/bin/rm -f /run/lirc/lircd
ExecStartPre=/bin/ln -s /run/lirc/lircd /dev/lircd
ExecStart=/usr/sbin/eventlircd --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd
ExecStopPost=/bin/rm -f /dev/lircd
ExecStopPost=/bin/rm -f /run/lirc/lircd


[Install]
WantedBy=multi-user.target

Alles anzeigen

Keymap file /etc/rc_keymaps/xbox360-mce file von hier mit folgenden eintrag in /etc/rc_maps.cfg

Code

[]# cat /etc/rc_maps.cfg
nuvoton-cir 	*   	/etc/rc_keymaps/xbox360-mce
[#

config geladen:

Code

[ rc_keymaps]# ir-keytable -a /etc/rc_maps.cfg --sysdev rc0
Old keytable cleared
Wrote 95 keycode(s) to driver
Protocols changed to RC-6
[ rc_keymaps]# ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event3) with:
Driver nuvoton-cir, table rc-rc6-mce
Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
Enabled protocols: RC-6
Name: Nuvoton w836x7hg Infrared Remote
bus: 25, vendor/product: 1050:00b4, version: 0x0073
Repeat delay = 500 ms, repeat period = 125 ms
[ rc_keymaps]#

Alles anzeigen

beim ir-keytable -t test ich bekomme inputs aber bei evtest nicht.

Auf evtest ist nicht zu sehen:

Code

[ ~]# evtest /dev/input/event3
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "MCE IR Keyboard/Mouse (nuvoton-cir)"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
	Event code 1 (KEY_ESC)
	Event code 2 (KEY_1)
.
.
.

Alles anzeigen

VDR remote.conf ist von hier

Weiß nicht was ich noch machen soll. Ratschlag?

crow · 5. Mai 2013

daran hab ich auch Interesse

crow · 18. Februar 2013

Zitat von Copperhead

vdr4arch ist schon aktuell. Für alle, die vdr4arch benutzen (Viele sollten es ja nicht sein). Bitte nicht aktualisieren bzw. beim Update ffmpeg auslassen. ffmpeg in Archlinux ist heute neu gekommen und softhddevice kann damit nicht.

Danke und Danke an Klaus für die neue Version.

crow · 11. November 2012

Zitat von seahawk1986

Ich habe mit meinem CIR das alles durchprobiert und IMHO ist es unsinnig den CIR mit lirc zu betreiben, wenn man eine Fernbedienung hat, deren Protokoll direkt vom rc-core Treiber unterstützt wird. Wenn man dann trotztdem einen Lirc-Sockel haben will, sind Dienste wie inputlirc oder eventlircd deutlich besser geeignet und man spart sich die ganze unnötige Konfiguration mit für lirc.

Kannst mir bitte das kurz erkleren, was mit dem rc-core treiber du gemeint hast? Also bis jetzt kenne ich nur lirc, yaVDR soll mit eventlircd laufen oder? Aber wie kann man etwas was in die rc-core treiber unterstüzt ist steuern, bzw mit VDR und XBMC verbinden?

Edit #1:
Oh ich habe das von dir gefunden, werde es probieren.
Hilfsskript für rc-core Empfänger

crow · 11. November 2012

Ich habe beiden lircd.conf aus VDR-Wiki ausprobiert, leider ohne erfolgt. Also vor posten hier habe ich glaub 100 varianten schon probiert. Jetzt habe ich einfach keine idee mehr. In lirc startup script ändere ich --protocol=LIRC oder --protocol=RC-6 also ich hoffe ir-keytable bekommt das mit.
Jetzt habe ich lircd disabled, alles disabled was auf device greifen kann, ein reboot und nur mit "ir-keytable -p rc-6 -t" probiert, leider ohne irgend an erfolg.

Code

# ir-keytable -v
Found device /sys/class/rc/rc0/
Input sysfs node is /sys/class/rc/rc0/input3/
Event sysfs node is /sys/class/rc/rc0/input3/event3/
Parsing uevent /sys/class/rc/rc0/input3/event3/uevent
/sys/class/rc/rc0/input3/event3/uevent uevent MAJOR=13
/sys/class/rc/rc0/input3/event3/uevent uevent MINOR=67
/sys/class/rc/rc0/input3/event3/uevent uevent DEVNAME=input/event3
Parsing uevent /sys/class/rc/rc0/uevent
/sys/class/rc/rc0/uevent uevent NAME=rc-rc6-mce
/sys/class/rc/rc0/uevent uevent DRV_NAME=nuvoton-cir
input device is /dev/input/event3
/sys/class/rc/rc0/protocols protocol rc-5 (disabled)
/sys/class/rc/rc0/protocols protocol nec (disabled)
/sys/class/rc/rc0/protocols protocol rc-6 (enabled)
/sys/class/rc/rc0/protocols protocol jvc (disabled)
/sys/class/rc/rc0/protocols protocol sony (disabled)
/sys/class/rc/rc0/protocols protocol sanyo (disabled)
/sys/class/rc/rc0/protocols protocol mce_kbd (disabled)
/sys/class/rc/rc0/protocols protocol lirc (disabled)
Found /sys/class/rc/rc0/ (/dev/input/event3) with:
    	Driver nuvoton-cir, table rc-rc6-mce
    	Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC other
    	Enabled protocols: RC-6
    	Repeat delay = 500 ms, repeat period = 125 ms


# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
^C
# ir-keytable -p RC-6 -t
Protocols changed to RC-6
Testing events. Please, press CTRL-C to abort.
^C
# ir-keytable -p RC-6 -d /dev/input/event3 -t
/protocol: No such file or directory
Couldn't change the IR protocols
Testing events. Please, press CTRL-C to abort.
^C
# ir-keytable -d /dev/input/event3 -t
Testing events. Please, press CTRL-C to abort.
^C

Alles anzeigen

Soll ir-keytable -t irgendwas liefern in denn fall jetzt? Ich bin nicht sicher ob CIR und ein XBOX360 RC6 remote zusammen funktionieren können.

EDIT #1:
Ok jetzt schaut besser aus. Scheinbar ist der CIR nicht so start genung oder so was.. Jetzt stehe ich neben ION und ir-keytable probiert und tada da ist was, bei mode2 kommt noch immer nichts.

Code

( Knopf 1)
# ir-keytable -t
Testing events. Please, press CTRL-C to abort.
1352644431.191974: event MSC: scancode = 800f7401
1352644431.191977: event sync
1352644431.295233: event MSC: scancode = 800f7401
1352644431.295236: event sync
^C


# mode2 -d /dev/lirc0

Alles anzeigen

crow · 11. November 2012

Hardware:
ASRock ION 330HT [1]
XBOX360 Remote [2]

Software: Archlinux 64Bit (archlinux-2012.11.01-dual.iso )

Problem:
ASRock MCE Remote Controller [3] ist kapput gegangen, bzw. es funktionieren nicht alle knopfe (bsp. on/off schalter etc).

Also CIR wird gefunden und module wird geladen:

Code

[]$ dmesg | grep nuvoton
[	6.154075] nuvoton_cir: driver has been successfully loaded
[	7.704188] input: MCE IR Keyboard/Mouse (nuvoton-cir) as /devices/virtual/input/input6
[	7.793878] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0
[]$

Mehr info von CIR:

Code

[]# ir-keytable -v
Found device /sys/class/rc/rc0/
Input sysfs node is /sys/class/rc/rc0/input3/
Event sysfs node is /sys/class/rc/rc0/input3/event3/
Parsing uevent /sys/class/rc/rc0/input3/event3/uevent
/sys/class/rc/rc0/input3/event3/uevent uevent MAJOR=13
/sys/class/rc/rc0/input3/event3/uevent uevent MINOR=67
/sys/class/rc/rc0/input3/event3/uevent uevent DEVNAME=input/event3
Parsing uevent /sys/class/rc/rc0/uevent
/sys/class/rc/rc0/uevent uevent NAME=rc-rc6-mce
/sys/class/rc/rc0/uevent uevent DRV_NAME=nuvoton-cir
input device is /dev/input/event3
/sys/class/rc/rc0/protocols protocol rc-5 (disabled)
/sys/class/rc/rc0/protocols protocol nec (disabled)
/sys/class/rc/rc0/protocols protocol rc-6 (disabled)
/sys/class/rc/rc0/protocols protocol jvc (disabled)
/sys/class/rc/rc0/protocols protocol sony (disabled)
/sys/class/rc/rc0/protocols protocol sanyo (disabled)
/sys/class/rc/rc0/protocols protocol mce_kbd (disabled)
/sys/class/rc/rc0/protocols protocol lirc (enabled)
Found /sys/class/rc/rc0/ (/dev/input/event3) with:
    	Driver nuvoton-cir, table rc-rc6-mce
    	Supported protocols: NEC RC-5 RC-6 JVC SONY LIRC other
    	Enabled protocols: LIRC
    	Repeat delay = 500 ms, repeat period = 125 ms
[]#

Alles anzeigen

Und /etc/lirc/hardware.conf:

Code

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Nuvoton Transceivers/Remotes"
REMOTE_MODULES="lirc_dev nuvoton-cir"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="lirc_wb677/lircd.conf.wb677"
#REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb"
REMOTE_LIRCD_ARGS=

Alles anzeigen

Input device:

Code

I: Bus=0019 Vendor=1050 Product=00b4 Version=0073
N: Name="Nuvoton w836x7hg Infrared Remote Transceiver"
P: Phys=nuvoton/cir0
S: Sysfs=/devices/pnp0/00:04/rc/rc0/input3
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=100013
B: KEY=fff 0 200108fc32e 237605100000000 0 700158000 419200004001 8e968000000000 10000000
B: MSC=10


I: Bus=0003 Vendor=9022 Product=d650 Version=0000
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:00:04.1-3/ir0
S: Sysfs=/devices/pci0000:00/0000:00:04.1/usb1/1-3/input/input4
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=3
B: KEY=6c0904 2470c100000000 0 800010000 19040000840 1e168000000001 f800000000000ffc

Alles anzeigen

Gerade ist LIRC protocol benutzt und ASRock MCE Remote funktioniert damit (asser die nicht funktionierde knopfe, da leutet auch nicht wenn man drauf press, meine meinung ist was in FB kapput).
Dann wollte ich XBOX360 Remote benutzten. Da der mir einfachen ir-einschalter funktioniert wollte ich denn mit ASRock CIR probieren. Und da sind probleme gekommen.
XBOX360 remote ist ein RC-6 remote, und sommit habe ich lirc protocol auf rc-6 geändert. Die mode2 oder ir-keytable -t gibt keine ausgabe.

Wenn ich protocol wieder auf LIRC umstelle um auf remote 1 und 2 drücke kommt so was bei mode2 und bei ir-keytable -v kommt noch immer nichts.

Code

# mode2 -d /dev/lirc0
pulse 150
space 3600
pulse 200
space 800
pulse 150
space 94500
pulse 200
space 250
pulse 50
space 5800
pulse 150
space 16750
pulse 50
space 82700
pulse 50
space 10100
pulse 50
space 13900
pulse 100
space 95250
pulse 50
space 2550
pulse 100
space 73850
pulse 200
space 6200
pulse 250
space 2900
pulse 100
space 95250
pulse 50
space 11000
pulse 50
space 12800
pulse 50
space 95250

Alles anzeigen

EIn evtest liefert das:

Code

[root@vdrbox ~]# evtest /dev/input/event3
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x1050 product 0xb4 version 0x73
Input device name: "Nuvoton w836x7hg Infrared Remote Transceiver"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
	Event code 28 (KEY_ENTER)
	Event code 103 (KEY_UP)
	Event code 105 (KEY_LEFT)
	Event code 106 (KEY_RIGHT)
	Event code 108 (KEY_DOWN)
	Event code 111 (KEY_DELETE)
	Event code 113 (KEY_MUTE)
	Event code 114 (KEY_VOLUMEDOWN)
	Event code 115 (KEY_VOLUMEUP)
	Event code 119 (KEY_PAUSE)
	Event code 128 (KEY_STOP)
	Event code 142 (KEY_SLEEP)
	Event code 161 (KEY_EJECTCD)
	Event code 164 (KEY_PLAYPAUSE)
	Event code 167 (KEY_RECORD)
	Event code 168 (KEY_REWIND)
	Event code 174 (KEY_EXIT)
	Event code 207 (KEY_PLAY)
	Event code 208 (KEY_FASTFORWARD)
	Event code 210 (KEY_PRINT)
	Event code 212 (KEY_CAMERA)
	Event code 224 (KEY_BRIGHTNESSDOWN)
	Event code 225 (KEY_BRIGHTNESSUP)
	Event code 226 (KEY_MEDIA)
	Event code 352 (KEY_OK)
	Event code 356 (KEY_POWER2)
	Event code 358 (KEY_INFO)
	Event code 365 (KEY_EPG)
	Event code 366 (KEY_PVR)
	Event code 368 (KEY_LANGUAGE)
	Event code 369 (KEY_TITLE)
	Event code 370 (KEY_SUBTITLE)
	Event code 372 (KEY_ZOOM)
	Event code 373 (KEY_MODE)
	Event code 377 (KEY_TV)
	Event code 385 (KEY_RADIO)
	Event code 386 (KEY_TUNER)
	Event code 387 (KEY_PLAYER)
	Event code 389 (KEY_DVD)
	Event code 392 (KEY_AUDIO)
	Event code 393 (KEY_VIDEO)
	Event code 398 (KEY_RED)
	Event code 399 (KEY_GREEN)
	Event code 400 (KEY_YELLOW)
	Event code 401 (KEY_BLUE)
	Event code 402 (KEY_CHANNELUP)
	Event code 403 (KEY_CHANNELDOWN)
	Event code 407 (KEY_NEXT)
	Event code 412 (KEY_PREVIOUS)
	Event code 425 (KEY_PRESENTATION)
	Event code 512 (KEY_NUMERIC_0)
	Event code 513 (KEY_NUMERIC_1)
	Event code 514 (KEY_NUMERIC_2)
	Event code 515 (KEY_NUMERIC_3)
	Event code 516 (KEY_NUMERIC_4)
	Event code 517 (KEY_NUMERIC_5)
	Event code 518 (KEY_NUMERIC_6)
	Event code 519 (KEY_NUMERIC_7)
	Event code 520 (KEY_NUMERIC_8)
	Event code 521 (KEY_NUMERIC_9)
	Event code 522 (KEY_NUMERIC_STAR)
	Event code 523 (KEY_NUMERIC_POUND)
  Event type 4 (EV_MSC)
	Event code 4 (MSC_SCAN)
  Event type 20 (EV_REP)
Properties:
Testing ... (interrupt to exit)


^C

Alles anzeigen

Hat jemand vieleicht ein vorschlag. Bin dankbar dafür..

crow · 14. Oktober 2012

Man braucht die nicht da die default sind, aber sollen auch nicht zu viele sein.
So wie vorgeschlagen wird ein start gesendet aber nie beendet (also shell prompt kommt nicht, sondern muss ich mit Ctrl+C beende), und auf TV kommts nichts aus X in mitte (also xorg startet):

Code

[vdr@vdrbox ~]$ /usr/bin/vdr -g /tmp -l 2 --lirc -P "softhddevice -d :0 -g 1920x1080+0+0 -s -a hw:0,3 -p hw:0,3"  -s /usr/lib/vdr/bin/shutdown-wrapper -t /dev/tty8 -w 90

im log:

Code

Oct 14 20:51:40 vdrbox vdr: [11159] VDR version 1.7.31 started
Oct 14 20:51:40 vdrbox vdr: [11159] codeset is 'UTF-8' - known
Oct 14 20:51:40 vdrbox vdr: [11159] loading plugin: /usr/lib/vdr/plugins/libvdr-softhddevice.so.1.7.31
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/setup.conf
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/sources.conf
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/diseqc.conf
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/scr.conf
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/channels.conf
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/timers.conf
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/svdrphosts.conf
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/remote.conf
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/keymacros.conf
Oct 14 20:51:40 vdrbox vdr: [11159] frontend 0/0 provides DVB-S,DVB-S2 with QPSK ("Conexant CX24116/CX24118")
Oct 14 20:51:40 vdrbox vdr: [11159] found 1 DVB device
Oct 14 20:51:40 vdrbox vdr: [11159] initializing plugin: softhddevice (0.5.2-GITde7c4b2a): A software and GPU emulated HD device
Oct 14 20:51:40 vdrbox vdr: [11159] setting primary device to 2
Oct 14 20:51:40 vdrbox vdr: [11159] SVDRP listening on port 6419
Oct 14 20:51:40 vdrbox vdr: [11159] setting current skin to "lcars"
Oct 14 20:51:40 vdrbox vdr: [11159] loading /var/lib/vdr/themes/lcars-default.theme
Oct 14 20:51:43 vdrbox vdr: [11159] switching to channel 1
Oct 14 20:51:45 vdrbox vdr: [11159] retuning due to modification of channel 1
Oct 14 20:51:45 vdrbox vdr: [11159] switching to channel 1

Alles anzeigen

Beiträge von crow

DVBSky S960 VDR 2.1.2 USALS und DiSEqC Motor

DVBSky S960 VDR 2.1.2 USALS und DiSEqC Motor

Tevii S650 USB IR-Empfänger

Tevii S650 USB IR-Empfänger

Tevii S650 USB IR-Empfänger

diseqc für VDR 2.1 umstellen

Tevii S650 USB IR-Empfänger

Tevii S650 USB IR-Empfänger

ASRock ION 330HT CIR und XBOX360 Remote

ASRock ION 330HT CIR und XBOX360 Remote

ASRock ION 330HT CIR und XBOX360 Remote

ASRock ION 330HT CIR und XBOX360 Remote

ASRock ION 330HT CIR und XBOX360 Remote

ASRock ION 330HT CIR und XBOX360 Remote

Rasperry Pi xine plugin

[ANNOUNCE] VDR developer version 1.7.38

ASRock ION 330HT CIR und XBOX360 Remote

ASRock ION 330HT CIR und XBOX360 Remote

ASRock ION 330HT CIR und XBOX360 Remote

SoftHDDevice erzeugt Tonaussetzer