[gustavgans]

Hallo liebe Community,
ich habe hier eine Sundtek SkyTV Ultimate Dual UHD, die MLD auch prima erkennt und
die auch der VDR problemlos verwendet. Beim Systemstart wird auch der IR-Empfänger
erkannt und als "input" gesetzt.
Sundtek hat mich nun leider hierher verwiesen, also frag ich auch nach.
In den MLD Einstellungen für die Fernbedienung gibt's als "Geräte" erstmal gpio, und
nur dafür gilt wohl die Möglichkeit, die Tastenzuordnung zu bearbeiten. Nun hab ich
aber halt nix an einem GPIO. Notfalls kommt da doch ein IR-Empfänger dran, wenn nichts
anderes geht, aber eigentlich möchte ich den verwenden, der ja nun schon da ist, also
Sundtek.
Die haben mir schon gesagt, dass sie nur "NEC" können, keine RC6 etc. Macht nichts, die
passende Fernbedienung sollte ich haben.
Die haben mir auch bereits gesagt, dass der Treiber zum OS hin eine Tastatur emuliert.
Was die mir nicht sagen können ist, wie ich denn meine FB einrichten kann. Zu allererst
müsste ich mal prüfen können, ob denn der Empfänger überhaupt was sieht. Die Tasten dann
einzeln zu definieren scheint ja nicht zu gehen (oder gibt's da eine versteckte .conf?),
nur eins der vier Standardprofile ist wählbar. Aber irgend wo müsste man doch sehen
können, ob/dass der IR-Empfänger von Sundtek überhaupt etwas empfängt.
Hat Jemand einen Tipp für mich?

[rfehr]

Du kannst doch die FB über das WebIf der MLD anlernen

[gustavgans]

Hmm beu dem Sundtek scheint das nicht zu gehen. Im WebIF ist ja neben dem Feld, wo ich den GPIO setzen kann, ein Button zum Anlernen, aber egal was ich gemacht habe:Der sat mir immer "keine Taste gedrückt". Sundtek meinte, dass die ein KBD emulieren, da kann dann die lirc Sache wohl nichts sehen, das geht wohl irgend wie anders...

[Doc Schnuggels]

Hi
Es gibt ein USB Empfänger Kit von mir mit einem RP2040 Zero
Der kann den RP5 auch einschalten
Der Empfänger hat sich mit MLD 6,5 auf einen Raspberry 5 bewährt
Einige User hier im Forum benutzen schon die Kombination
Der Zero wird im Web Interface von MLD erkannt und kann ganz easy mit Deiner Fernbedienung angelernt werden
Auf Wunsch schon fertig angelernt von mir mit einer passender neuen Fernbedienung
Siehe hier
https://www.minidvblinux.de/forum/index.php/topic,10964.msg88547.html#msg88547
Und hier speziell für RP 5
https://www.minidvblinux.de/forum/index.php/topic,10896.msg87635.html#msg87635
Gruß Helmut alias Doc Schnuggels oder emma53 im yaVDR Forum !!

[clausmuus]

Beim Sundtek Empfänger war bisher immer eine Fernbedienung dabei, und für diese lässt sich das passende Profil auswählen (eines der vier).
Außerdem ist das dann so vorkonfiguriert, dass die Belegung Fernbedienung direkt past. Trotzdem sollte es eigentlich möglich sein, die Belegung zu ändern.
Wenn ich mich richtig erinnere wird der Sundtek Empfänger auch erkannt und zum Anlernen angeboten. Da das bei Dir nicht der Fall ist, vermute ich dass der beim SkyTV Ultimate Dual UHD eine andere ID als bei den älteren Empfängern hat.

Du kannst mit dem Tool evtest (das ist im Paket evtest) prüfen ob die Tastendrücke ankommen. Außerdem könntest Du mal das Paket usbutils installieren und dann lsusb aufrufen und die Ausgabe hier posten. Vermutlich kann ich dann sehen welche ID ich im Webif zusätzlich einbauen muss, damit auch Dein Empfänger angelernt werden kann.

[gustavgans]

@Doc Schnuggels: Danke für den Hinweis. Ich möchte erstmal die Sundtek quälen. Wenn das nicht hinzubekommen ist, dann hänge ich als nächstes nen TSOP4438 o.ä. an einen GPIO - der RPi hat ja genügend davon... Insofern glaube ich nicht, dass ich die 2040-basierte, ich nenn sie mal Luxusversion, bräuchte. Aber falls doch, dann hab ich jedenfalls jetzt den Weg dorthin - dankeschön.

[gustavgans]

@clausmuus:
Witzigerweise taucht die Sundtek-Remote in lsusb gar nicht auf, aber in der Hardware wird sie sehr wohl erkannt und als /dev/input/event9 auf "input:6" verlinkt. Bei der "Einkanaligen" SkyTV liefert Sundtek ne FB mit, bei der Dual nicht. Also muss ich "meine" verwenden, aber solange die NEC blinkt sollte es, so Sundtek, gehen.
Ich zitiere hier mal lsusb (incl. usbutils - die sind eh längst da, ohne sie versteht man ja kaum was... - könnten ins Standard-Install auch direkt rein, oder?) und lshw (nicht wundern über usb-keyboard&mouse, die sind noch da weil ich sie bei Bootproblemen ja brauche...):

Code: [Select]

root@MLD:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 13ba:0017 PCPlay PS/2 Keyboard+Mouse Adapter
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 2659:1802 Sundtek Dual S2
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s
root@MLD:~# lshw
mld
    description: Computer
    product: Raspberry Pi 5 Model B Rev 1.1
    serial: 3373535155ad5344
    width: 64 bits
    capabilities: smp cp15_barrier setend swp tagged_addr_disabled
  *-core
       description: Motherboard
       physical id: 0
     *-cpu:0
          description: CPU
          product: cpu
          physical id: 1
          bus info: cpu@0
          size: 2400MHz
          capacity: 2400MHz
          capabilities: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc
dcpop asimddp cpufreq
        *-cache
             description: L1 Cache
             physical id: 0
             size: 64KiB
     *-cpu:1
          description: CPU
          product: cpu
          physical id: 2
          bus info: cpu@1
          size: 2400MHz
          capacity: 2400MHz
          capabilities: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc
dcpop asimddp cpufreq
        *-cache
             description: L1 Cache
             physical id: 0
             size: 64KiB
     *-cpu:2
          description: CPU
          product: cpu
          physical id: 3
          bus info: cpu@2
          size: 2400MHz
          capacity: 2400MHz
          capabilities: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc
dcpop asimddp cpufreq
        *-cache
             description: L1 Cache
             physical id: 0
             size: 64KiB
     *-cpu:3
          description: CPU
          product: cpu
          physical id: 4
          bus info: cpu@3
          size: 2400MHz
          capacity: 2400MHz
          capabilities: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc
dcpop asimddp cpufreq
        *-cache
             description: L1 Cache
             physical id: 0
             size: 64KiB
     *-cpu:4 DISABLED
          description: CPU
          product: l2-cache-l0
          physical id: 5
          bus info: cpu@4
     *-cpu:5 DISABLED
          description: CPU
          product: l2-cache-l1
          physical id: 6
          bus info: cpu@5
     *-cpu:6 DISABLED
          description: CPU
          product: l2-cache-l2
          physical id: 7
          bus info: cpu@6
     *-cpu:7 DISABLED
          description: CPU
          product: l2-cache-l3
          physical id: 8
          bus info: cpu@7
     *-cpu:8 DISABLED
          description: CPU
          product: l3-cache
          physical id: 9
          bus info: cpu@8
     *-memory
          description: System memory
          physical id: a
          size: 2002MiB
     *-pci
          description: PCI bridge
          product: Broadcom Inc. and subsidiaries
          vendor: Broadcom Inc. and subsidiaries
          physical id: 0
          bus info: pci@0000:00:00.0
          version: 30
          width: 32 bits
          clock: 33MHz
          capabilities: pci pm pciexpress normal_decode bus_master cap_list
          configuration: driver=pcieport
          resources: irq:41 memory:1f00000000-1f005fffff
        *-network
             description: Ethernet controller
             physical id: 0
             bus info: pci@0000:01:00.0
             version: 00
             width: 32 bits
             clock: 33MHz
             capabilities: pm pciexpress msix bus_master cap_list
             configuration: driver=rp1 latency=0
             resources: irq:41 memory:1f00410000-1f00413fff memory:1f00000000-1f003fffff memory:1f00400000-1f
0040ffff
  *-usbhost:0
       product: xHCI Host Controller
       vendor: Linux 6.6.63-v8-16k xhci-hcd
       physical id: 1
       bus info: usb@1
       logical name: usb1
       version: 6.06
       capabilities: usb-2.00
       configuration: driver=hub slots=2 speed=480Mbit/s
     *-usb
          description: Keyboard
          product: Generic USB K/B System Control
          physical id: 2
          bus info: usb@1:2
          logical name: input4
          logical name: /dev/input/event4
          logical name: input4::capslock
          logical name: input4::compose
          logical name: input4::kana
          logical name: input4::numlock
          logical name: input4::scrolllock
          logical name: input5
          logical name: /dev/input/event5
          logical name: /dev/input/mouse0
          logical name: input6
          logical name: /dev/input/event6
          version: 0.01
          capabilities: usb-1.10 usb
          configuration: driver=usbhid maxpower=100mA speed=1Mbit/s
  *-usbhost:1
       product: xHCI Host Controller
       vendor: Linux 6.6.63-v8-16k xhci-hcd
       physical id: 2
       bus info: usb@2
       logical name: usb2
       version: 6.06
       capabilities: usb-3.00
       configuration: driver=hub slots=1 speed=5000Mbit/s
  *-usbhost:2
       product: xHCI Host Controller
       vendor: Linux 6.6.63-v8-16k xhci-hcd
       physical id: 3
       bus info: usb@3
       logical name: usb3
       version: 6.06
       capabilities: usb-2.00
       configuration: driver=hub slots=2 speed=480Mbit/s
     *-usb
          description: Generic USB device
          product: Dual S2
          vendor: Sundtek
          physical id: 2
          bus info: usb@3:2
          version: 0.00
          serial: U260423161927
          capabilities: usb-2.00
          configuration: driver=usbfs maxpower=400mA speed=480Mbit/s
  *-usbhost:3
       product: xHCI Host Controller
       vendor: Linux 6.6.63-v8-16k xhci-hcd
       physical id: 4
       bus info: usb@4
       logical name: usb4
       version: 6.06
       capabilities: usb-3.00
       configuration: driver=hub slots=1 speed=5000Mbit/s
     *-usb
          description: Mass storage device
          product: USB3.0 Device
          vendor: Intenso
          physical id: 1
          bus info: usb@4:1
          version: 2.14
          serial: DD56419883998
          capabilities: usb-3.00 scsi
          configuration: driver=uas maxpower=896mA speed=5000Mbit/s
  *-mmc0
       description: MMC Host
       physical id: 5
       logical name: mmc0
     *-device
          description: SD Card
          product: SDABC
          vendor: Unknown (111)
          physical id: b369
          logical name: /dev/mmcblk0
          version: 1.0
          date: 12/2024
          serial: 2852135424
          size: 14GiB (15GB)
          capabilities: sd gpt-1.00 partitioned partitioned:gpt
          configuration: guid=bbd3ff83-b7a5-4b55-8023-4866a7c9c1e7 logicalsectorsize=512 sectorsize=512
        *-volume:0
             description: Windows FAT volume
             vendor: mkfs.fat
             physical id: 1
             logical name: /dev/mmcblk0p1
             logical name: /boot
             version: FAT32
             serial: e789-b4f8
             size: 283MiB
             capacity: 284MiB
             capabilities: fat initialized
             configuration: FATs=2 filesystem=fat mount.fstype=vfat mount.options=rw,noatime,fmask=0022,dmask
=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro name=boot state=mounted
        *-volume:1
             description: EFI partition
             physical id: 2
             logical name: /dev/mmcblk0p2
             logical name: /
             logical name: /var/lib/containers/storage/overlay
             serial: 1705125f-499b-4495-b3fa-81340fe300a0
             capacity: 14GiB
             configuration: mount.fstype=btrfs mount.options=rw,noatime,ssd,discard=async,space_cache=v2,subv
olid=256,subvol=/@root name=root state=mounted
  *-mmc1
       description: MMC Host
       physical id: 6
       logical name: mmc1
     *-device
          description: SDIO Device
          physical id: 1
          bus info: mmc@1:0001
          serial: 0
          capabilities: sdio
        *-interface:0
             description: Wireless interface
             product: 4345
             vendor: Broadcom
             physical id: 1
             bus info: mmc@1:0001:1
             logical name: mmc1:0001:1
             logical name: wlan0
             serial: 88:a2:9e:e0:53:4c
             capabilities: ethernet physical wireless
             configuration: broadcast=yes driver=brcmfmac driverversion=7.45.234 firmware=01-996384e2 ip=192.
168.1.42 multicast=yes wireless=IEEE 802.11
        *-interface:1
             product: 4345
             vendor: Broadcom
             physical id: 2
             bus info: mmc@1:0001:2
             logical name: mmc1:0001:2
        *-bt
             description: BlueTooth interface
             product: 4345
             vendor: Broadcom
             physical id: 3
             bus info: mmc@1:0001:3
             logical name: mmc1:0001:3
             capabilities: wireless bluetooth
             configuration: wireless=BlueTooth
  *-sound:0
       description: vc4hdmi0
       physical id: 7
       logical name: card0
       logical name: /dev/snd/controlC0
       logical name: /dev/snd/pcmC0D0p
  *-sound:1
       description: vc4hdmi1
       physical id: 8
       logical name: card1
       logical name: /dev/snd/controlC1
       logical name: /dev/snd/pcmC1D0p
  *-graphics
       product: vc4drmfb
       physical id: 9
       logical name: /dev/fb0
       capabilities: fb
       configuration: depth=16 resolution=1920,1080
  *-input:0
       product: vc4-hdmi-0 HDMI Jack
       physical id: a
       logical name: input0
       logical name: /dev/input/event0
  *-input:1
       product: vc4-hdmi-1 HDMI Jack
       physical id: b
       logical name: input1
       logical name: /dev/input/event1
  *-input:2
       product: pwr_button
       physical id: c
       logical name: input2
       logical name: /dev/input/event2
       capabilities: platform
  *-input:3
       product: gpio_ir_recv
       physical id: d
       logical name: input3
       logical name: /dev/input/event3
       capabilities: platform
  *-input:4
       product: keyd virtual keyboard
       physical id: e
       logical name: input7
       logical name: /dev/input/event7
       logical name: input7::capslock
       logical name: input7::compose
       logical name: input7::kana
       logical name: input7::misc
       logical name: input7::mute
       logical name: input7::numlock
       logical name: input7::scrolllock
       logical name: input7::sleep
       logical name: input7::suspend
       capabilities: usb
  *-input:5
       product: keyd virtual pointer
       physical id: f
       logical name: input8
       logical name: /dev/input/event8
       logical name: /dev/input/js0
       logical name: /dev/input/mouse1
       capabilities: usb
  *-input:6
       product: Sundtek Remote Control
       physical id: 10
       logical name: input9
       logical name: /dev/input/event9
       capabilities: usb
  *-network
       description: Ethernet interface
       physical id: 11
       logical name: eth0
       serial: 88:a2:9e:e0:53:4b
       capacity: 1Gbit/s
       capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=macb driverversion=6.6.63-v8-16k link=no multic
ast=yes port=twisted pair
root@MLD:~#  Ich schicke dies hier schonmal, ohne evtest bereits benutzt zu haben, mach ich aber noch. Aber wenn der Sundtek-remote noch gar ncht eingebunden ist, würde das ja auch nix ergeben...
In lshw ist auch die lustige Einsortierung des RPi5 wlan in den Baum "mmc1" zu sehen. Muss man auch erstmal drauf kommen, aber darum geht's hier ja nicht.

[gustavgans]

@clausmuus:
Nachtrag: Hier die "Ergebnisse" zu evtest. Bitte entschuldige meine Unwissenheit was ich weiter tun könnte: Alles sieht ansich prima aus: Der /dev/input/event9 wird vom System bearbeitet. Ich muss jetzt mal langsam rausfinden, ob denn überhaupt irgend eine meiner zig Fernbedienungen NEC Protokoll/Frequenz blinkt, denn da das Gerät ja bereits überwacht wird kann ich mit evtest nicht lauschen. Ich möchte nicht ausgerechnet den keyd killen, denn dann geht ja vielleicht gar keine Eingabe mehr... oder kann ich evtest sonstwie den Zugriff geben?
Es folgt evtest, fuser, und zur Identifikation der Prozesse ein Ausschnitt aus ps.

Code: [Select]

root@MLD:~# evtest --grab /dev/input/event9
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x2659 product 0x1 version 0x1
Input device name: "Sundtek Remote Control"
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)
    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 84 (?)
    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 101 (KEY_LINEFEED)
    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)
    Event code 111 (KEY_DELETE)
    Event code 112 (KEY_MACRO)
    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 118 (KEY_KPPLUSMINUS)
    Event code 119 (KEY_PAUSE)
    Event code 120 (KEY_SCALE)
    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 139 (KEY_MENU)
    Event code 140 (KEY_CALC)
    Event code 141 (KEY_SETUP)
    Event code 142 (KEY_SLEEP)
    Event code 143 (KEY_WAKEUP)
    Event code 144 (KEY_FILE)
    Event code 145 (KEY_SENDFILE)
    Event code 146 (KEY_DELETEFILE)
    Event code 147 (KEY_XFER)
    Event code 148 (KEY_PROG1)
    Event code 149 (KEY_PROG2)
    Event code 150 (KEY_WWW)
    Event code 151 (KEY_MSDOS)
    Event code 152 (KEY_SCREENLOCK)
    Event code 153 (KEY_DIRECTION)
    Event code 154 (KEY_CYCLEWINDOWS)
    Event code 155 (KEY_MAIL)
    Event code 156 (KEY_BOOKMARKS)
    Event code 157 (KEY_COMPUTER)
    Event code 158 (KEY_BACK)
    Event code 159 (KEY_FORWARD)
    Event code 160 (KEY_CLOSECD)
    Event code 161 (KEY_EJECTCD)
    Event code 162 (KEY_EJECTCLOSECD)
    Event code 163 (KEY_NEXTSONG)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 165 (KEY_PREVIOUSSONG)
    Event code 166 (KEY_STOPCD)
    Event code 167 (KEY_RECORD)
    Event code 168 (KEY_REWIND)
    Event code 169 (KEY_PHONE)
    Event code 170 (KEY_ISO)
    Event code 171 (KEY_CONFIG)
    Event code 172 (KEY_HOMEPAGE)
    Event code 173 (KEY_REFRESH)
    Event code 174 (KEY_EXIT)
    Event code 175 (KEY_MOVE)
    Event code 176 (KEY_EDIT)
    Event code 177 (KEY_SCROLLUP)
    Event code 178 (KEY_SCROLLDOWN)
    Event code 179 (KEY_KPLEFTPAREN)
    Event code 180 (KEY_KPRIGHTPAREN)
    Event code 181 (KEY_NEW)
    Event code 182 (KEY_REDO)
    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 195 (?)
    Event code 196 (?)
    Event code 197 (?)
    Event code 198 (?)
    Event code 199 (?)
    Event code 200 (KEY_PLAYCD)
    Event code 201 (KEY_PAUSECD)
    Event code 202 (KEY_PROG3)
    Event code 203 (KEY_PROG4)
    Event code 204 (KEY_DASHBOARD)
    Event code 205 (KEY_SUSPEND)
    Event code 206 (KEY_CLOSE)
    Event code 207 (KEY_PLAY)
    Event code 208 (KEY_FASTFORWARD)
    Event code 209 (KEY_BASSBOOST)
    Event code 210 (KEY_PRINT)
    Event code 211 (KEY_HP)
    Event code 212 (KEY_CAMERA)
    Event code 213 (KEY_SOUND)
    Event code 214 (KEY_QUESTION)
    Event code 215 (KEY_EMAIL)
    Event code 216 (KEY_CHAT)
    Event code 217 (KEY_SEARCH)
    Event code 218 (KEY_CONNECT)
    Event code 219 (KEY_FINANCE)
    Event code 220 (KEY_SPORT)
    Event code 221 (KEY_SHOP)
    Event code 222 (KEY_ALTERASE)
    Event code 223 (KEY_CANCEL)
    Event code 224 (KEY_BRIGHTNESSDOWN)
    Event code 225 (KEY_BRIGHTNESSUP)
    Event code 226 (KEY_MEDIA)
    Event code 227 (KEY_SWITCHVIDEOMODE)
    Event code 228 (KEY_KBDILLUMTOGGLE)
    Event code 229 (KEY_KBDILLUMDOWN)
    Event code 230 (KEY_KBDILLUMUP)
    Event code 231 (KEY_SEND)
    Event code 232 (KEY_REPLY)
    Event code 233 (KEY_FORWARDMAIL)
    Event code 234 (KEY_SAVE)
    Event code 235 (KEY_DOCUMENTS)
    Event code 236 (KEY_BATTERY)
    Event code 237 (KEY_BLUETOOTH)
    Event code 238 (KEY_WLAN)
    Event code 239 (KEY_UWB)
    Event code 241 (KEY_VIDEO_NEXT)
    Event code 242 (KEY_VIDEO_PREV)
    Event code 243 (KEY_BRIGHTNESS_CYCLE)
    Event code 244 (KEY_BRIGHTNESS_ZERO)
    Event code 245 (KEY_DISPLAY_OFF)
    Event code 246 (KEY_WIMAX)
    Event code 247 (KEY_RFKILL)
    Event code 352 (KEY_OK)
    Event code 353 (KEY_SELECT)
    Event code 354 (KEY_GOTO)
    Event code 355 (KEY_CLEAR)
    Event code 356 (KEY_POWER2)
    Event code 357 (KEY_OPTION)
    Event code 358 (KEY_INFO)
    Event code 359 (KEY_TIME)
    Event code 360 (KEY_VENDOR)
    Event code 361 (KEY_ARCHIVE)
    Event code 362 (KEY_PROGRAM)
    Event code 363 (KEY_CHANNEL)
    Event code 364 (KEY_FAVORITES)
    Event code 365 (KEY_EPG)
    Event code 366 (KEY_PVR)
    Event code 367 (KEY_MHP)
    Event code 368 (KEY_LANGUAGE)
    Event code 369 (KEY_TITLE)
    Event code 370 (KEY_SUBTITLE)
    Event code 371 (KEY_ANGLE)
    Event code 372 (KEY_ZOOM)
    Event code 373 (KEY_MODE)
    Event code 374 (KEY_KEYBOARD)
    Event code 375 (KEY_SCREEN)
    Event code 376 (KEY_PC)
    Event code 377 (KEY_TV)
    Event code 378 (KEY_TV2)
    Event code 379 (KEY_VCR)
    Event code 380 (KEY_VCR2)
    Event code 381 (KEY_SAT)
    Event code 382 (KEY_SAT2)
    Event code 383 (KEY_CD)
    Event code 384 (KEY_TAPE)
    Event code 385 (KEY_RADIO)
    Event code 386 (KEY_TUNER)
    Event code 387 (KEY_PLAYER)
    Event code 388 (KEY_TEXT)
    Event code 389 (KEY_DVD)
    Event code 390 (KEY_AUX)
    Event code 391 (KEY_MP3)
    Event code 392 (KEY_AUDIO)
    Event code 393 (KEY_VIDEO)
    Event code 394 (KEY_DIRECTORY)
    Event code 395 (KEY_LIST)
    Event code 396 (KEY_MEMO)
    Event code 397 (KEY_CALENDAR)
    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 404 (KEY_FIRST)
    Event code 405 (KEY_LAST)
    Event code 406 (KEY_AB)
    Event code 407 (KEY_NEXT)
    Event code 408 (KEY_RESTART)
    Event code 409 (KEY_SLOW)
    Event code 410 (KEY_SHUFFLE)
    Event code 411 (KEY_BREAK)
    Event code 412 (KEY_PREVIOUS)
    Event code 413 (KEY_DIGITS)
    Event code 414 (KEY_TEEN)
    Event code 415 (KEY_TWEN)
    Event code 416 (KEY_VIDEOPHONE)
    Event code 417 (KEY_GAMES)
    Event code 418 (KEY_ZOOMIN)
    Event code 419 (KEY_ZOOMOUT)
    Event code 420 (KEY_ZOOMRESET)
    Event code 421 (KEY_WORDPROCESSOR)
    Event code 422 (KEY_EDITOR)
    Event code 423 (KEY_SPREADSHEET)
    Event code 424 (KEY_GRAPHICSEDITOR)
    Event code 425 (KEY_PRESENTATION)
    Event code 426 (KEY_DATABASE)
    Event code 427 (KEY_NEWS)
    Event code 428 (KEY_VOICEMAIL)
    Event code 429 (KEY_ADDRESSBOOK)
    Event code 430 (KEY_MESSENGER)
    Event code 431 (KEY_DISPLAYTOGGLE)
    Event code 432 (KEY_SPELLCHECK)
    Event code 433 (KEY_LOGOFF)
    Event code 434 (KEY_DOLLAR)
    Event code 435 (KEY_EURO)
    Event code 436 (KEY_FRAMEBACK)
    Event code 437 (KEY_FRAMEFORWARD)
    Event code 438 (KEY_CONTEXT_MENU)
    Event code 439 (KEY_MEDIA_REPEAT)
    Event code 440 (KEY_10CHANNELSUP)
    Event code 441 (KEY_10CHANNELSDOWN)
    Event code 442 (KEY_IMAGES)
    Event code 448 (KEY_DEL_EOL)
    Event code 449 (KEY_DEL_EOS)
    Event code 450 (KEY_INS_LINE)
    Event code 451 (KEY_DEL_LINE)
    Event code 464 (KEY_FN)
    Event code 465 (KEY_FN_ESC)
    Event code 466 (KEY_FN_F1)
    Event code 467 (KEY_FN_F2)
    Event code 468 (KEY_FN_F3)
    Event code 469 (KEY_FN_F4)
    Event code 470 (KEY_FN_F5)
    Event code 471 (KEY_FN_F6)
    Event code 472 (KEY_FN_F7)
    Event code 473 (KEY_FN_F8)
    Event code 474 (KEY_FN_F9)
    Event code 475 (KEY_FN_F10)
    Event code 476 (KEY_FN_F11)
    Event code 477 (KEY_FN_F12)
    Event code 478 (KEY_FN_1)
    Event code 479 (KEY_FN_2)
    Event code 480 (KEY_FN_D)
    Event code 481 (KEY_FN_E)
    Event code 482 (KEY_FN_F)
    Event code 483 (KEY_FN_S)
    Event code 484 (KEY_FN_B)
    Event code 497 (KEY_BRL_DOT1)
    Event code 506 (KEY_BRL_DOT10)
    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 2 (EV_REL)
  Event type 4 (EV_MSC)
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    250
    Repeat code 1 (REP_PERIOD)
      Value     33
Properties:     
Testing ... (interrupt to exit)
***********************************************
  This device is grabbed by another process.
  No events are available to evtest while the
  other grab is active.
  In most cases, this is caused by an X driver,
  try VT-switching and re-run evtest again.
  Run the following command to see processes with
  an open fd on this device
 "fuser -v /dev/input/event9"
***********************************************

root@MLD:~fuser /dev/input/event9
1010 1053       
root@MLD:~# ps
PID   USER     TIME  COMMAND
    1 root      0:03 {systemd} /sbin/init
    2 root      0:00 [kthreadd]
,,,
  742 root      0:00 [rc0]
...
 1001 root      0:00 {keyd.sh} /bin/sh /usr/bin/keyd.sh
 1010 root      0:00 /usr/lib/systemd/systemd-logind
 1016 root      0:19 node /usr/bin/webif
 1048 root      0:00 /usr/bin/shellinaboxd --css /etc/shellinabox/white-on-black.css --user=root --disable-s
 1049 root      0:00 /usr/bin/shellinaboxd --css /etc/shellinabox/white-on-black.css --user=root --disable-s
 1053 root      0:00 keyd
 1142 root      0:00 /usr/bin/conmon --api-version 1 -c 3e7bf85a09437dd7667d87b2e93475e3145ca77d50a054a89116
 1162 root      0:00 {start-container} /bin/bash /usr/bin/start-container
 1214 root      0:00 su squeezeboxserver -s /bin/sh -c /usr/bin/perl /lms/slimserver.pl --prefsdir /config/p
 1215 499       0:00 sh -c /usr/bin/perl /lms/slimserver.pl --prefsdir /config/prefs --logdir /config/logs -
 1216 499       0:20 /usr/bin/perl /lms/slimserver.pl --prefsdir /config/prefs --logdir /config/logs --cache
 1255 root      0:00 {appstarter.sh} /bin/sh /usr/bin/appstarter.sh
 1345 root      0:00 {frontend.sh} /bin/sh /usr/share/vdr/frontend.sh start
 1350 root      0:00 {50_softhddevice} /bin/sh /usr/share/vdr/frontend.d/50_softhddevice-drm-gles.sh start
 1419 root      0:00 sleep infinity
 1461 499       0:00 /usr/bin/perl /lms/gdresized.pl
 1470 root      1h30 /usr/bin/mediasrv -d --pluginpath=/usr/lib/sundtek
 1471 root      0:00 /usr/bin/mediasrv -d --pluginpath=/usr/lib/sundtek
 1495 root      2d08 /usr/bin/vdr
...
13138 root      0:00 ps
root@MLD:~#
Ich frage nochmal bei Sundtek nach, denn es wäre schon schade, wenn da nicht irgend eine LED auf dem Board ist, an der ich sehen kann ob der Empfänger denn was empfängt. DASS meine FBs etwas senden habe ich (Mobilfonkameratest...) immerhin geprüft, aber auf dem Sundtek Board ist's dunkel - abgesehen von den blauen LEDs, welche signalisieren, dass die beiden DVB-Kanäle aktiv sind.