[1] 2 3 >>> MLD-6.x / General / Remote Medion X10 for MCC-100
 

Online Marcin

  • Member
  • **
  • Posts: 60
    • View Profile
Remote Medion X10 for MCC-100
« on: February 09, 2026, 21:46:35 »
Hi,


What packages should I install to see my remote Medion X10 in the MLD-6.5 x86_64?
I use Reycom REC 100S2/CI.

MLD 6.5_x86_64 - Reycom REC 100 S2-CI

Online Marcin

  • Member
  • **
  • Posts: 60
    • View Profile
Remote Medion X10 for MCC-100
« Reply #1 on: February 10, 2026, 16:17:45 »
After installing vdr-plugin-remote VDR shows errors:

Code: [Select]
# apt-get install vdr-plugin-remote vdr-plugin-remote-locale-pl-pl
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  vdr-plugin-remote vdr-plugin-remote-locale-pl-pl
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 17.4 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://mld6.minidvblinux.de/nightbuild/deb/core2-64 ./ vdr-plugin-remote 0.7.0-r167-8.2 [15.7 kB]
Get:2 https://mld6.minidvblinux.de/nightbuild/deb/core2-64 ./ vdr-plugin-remote-locale-pl-pl 0.7.0-r167-8.2 [1676 B]
Create a snapshot of '/mnt/root/@root' in '/mnt/root/2026-02-10 16:02'
Delete subvolume 268 (no-commit): '/mnt/root/2026-02-10 12:45'
Fetched 17.4 kB in 0s (36.6 kB/s)
Selecting previously unselected package vdr-plugin-remote.
(Reading database ... 45%(Reading database ... 19600 files and directories currently installed.)
Preparing to unpack .../vdr-plugin-remote_0.7.0-r167-8.2_amd64.deb ...
Unpacking vdr-plugin-remote (0.7.0-r167-8.2) ...
Selecting previously unselected package vdr-plugin-remote-locale-pl-pl.
Preparing to unpack .../vdr-plugin-remote-locale-pl-pl_0.7.0-r167-8.2_amd64.deb ...
Unpacking vdr-plugin-remote-locale-pl-pl (0.7.0-r167-8.2) ...
Setting up vdr-plugin-remote (0.7.0-r167-8.2) ...
Setting up vdr-plugin-remote-locale-pl-pl (0.7.0-r167-8.2) ...


Errors from VDR log.
Code: [Select]

Feb 10 16:08:32 MLDOS vdr[2169]: [2169] ERROR: /dev/input/ir: No such file or directory
Feb 10 16:08:36 MLDOS vdr[2169]: [2169] remote: fatal error - unable to open input device


Dmesg next:

Code: [Select]
root@MLDOS:~# dmesg | grep -i lirc                                                           
root@MLDOS:~#     

Code: [Select]
oot@MLDOS:~# ir-keytable                                                                   
/sys/class/rc/: No such file or directory                                                   
No devices found
root@MLDOS:~#                                 


Code: [Select]
root@MLDOS:~# lsmod
Module                  Size  Used by
algif_aead             12288  0
algif_skcipher         12288  0
algif_hash             12288  0
af_alg                 24576  3 algif_hash,algif_skcipher,algif_aead
stv6110x               12288  2
lnbp21                 12288  2
cfg80211              987136  0         
stv090x                73728  2         
snd_hda_codec_hdmi     65536  1   
ddbridge              167936  21 
snd_hda_codec_realtek   155648  1 
cxd2099                16384  1 ddbridge   
snd_hda_codec_generic    81920  1 snd_hda_codec_realtek 
dvb_core              122880  1 ddbridge   
wmi_bmof               12288  0       
ledtrig_audio          12288  1 snd_hda_codec_generic 
coretemp               12288  0               
mc                     49152  1 dvb_core
snd_hda_intel          40960  0   
snd_intel_dspcfg       12288  1 snd_hda_intel
nvidia              10543104  57   
snd_hda_codec         126976  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_core           90112  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_code_realtek
snd_pcm               131072  5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_timer              36864  2 snd_pcm   
i2c_nforce2            12288  0
wmi                    28672  1 wmi_bmof
sch_fq_codel           16384  2
configfs               40960  1   
fuse                  147456  1
nfnetlink              16384  2       
root@MLDOS:~#
« Last Edit: February 10, 2026, 16:47:24 by Marcin »
MLD 6.5_x86_64 - Reycom REC 100 S2-CI

Offline franky

  • MLD-Developer
  • Expert Member
  • ******
  • Posts: 522
    • View Profile
Remote Medion X10 for MCC-100
« Reply #2 on: February 10, 2026, 16:40:55 »
Hi,

all my external X10 USB receivers are working fine with MLD 6.5.
For a X10 receiver no extra packages are needed.
Remote controls can be configured in the MLD - WebIF under "Settings" - "Remote"
You should find your X10 Receiver there as "X10 WTI RF receiver"
With the button "Edit Keymap" you can map the Remote keys to the VDR functions.


Online clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 21251
    • View Profile
    • ClausMuus.de
Remote Medion X10 for MCC-100
« Reply #3 on: February 10, 2026, 16:41:02 »
Du you use a remote control receiver, that need the remote plugin? This plugin is only for such a special receiver.
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 6.5 - lirc yaUsbIR - 4 x DD-Sat - Intel N100M - 4GB RAM - 64GB SSD + 12TB HDD + 22TB HDD - Lian Li PC-C37B - Samsung LE40A559

Online Marcin

  • Member
  • **
  • Posts: 60
    • View Profile
Remote Medion X10 for MCC-100
« Reply #4 on: February 10, 2026, 16:55:37 »
On my MLDHD I see only this:

MLD 6.5_x86_64 - Reycom REC 100 S2-CI

Online Marcin

  • Member
  • **
  • Posts: 60
    • View Profile
Remote Medion X10 for MCC-100
« Reply #5 on: February 10, 2026, 16:57:47 »
It's like that MLDHD doesn't see this remote.
« Last Edit: February 10, 2026, 16:59:26 by Marcin »
MLD 6.5_x86_64 - Reycom REC 100 S2-CI

Offline cs-7

  • Adv. Member
  • ***
  • Posts: 104
    • View Profile
Remote Medion X10 for MCC-100
« Reply #6 on: February 10, 2026, 17:02:28 »
As far as I know, this remote is not an IR-remote, it's a RF-remote.There should bei a matching USB receiver, otherwise the PC can't listen to this remote.

Addition:
Oh, just looked up the Reycom REC 100S2/CI, looks like the RF receiver is build in.
« Last Edit: February 10, 2026, 17:19:32 by cs-7 »
Server-VDR: VM (x86) MLD-6.5 / Client-VDR: RPI4, Argon ONE M.2, MLD-6.5 / SAT: DD Octopus Net, SCR LNB, Satman 65

Online Marcin

  • Member
  • **
  • Posts: 60
    • View Profile
Remote Medion X10 for MCC-100
« Reply #7 on: February 10, 2026, 17:21:28 »
MLDHD 5.3 – recognizes the remote control, see below. I have now checked that the remote control is working.

Code: [Select]
Feb 10 16:12:38 (MLD) user.info kernel: [   73.176808] Registered IR keymap rc-medion-x10-or2x
Feb 10 16:12:38 (MLD) user.info kernel: [   73.177361] input: X10 WTI RF receiver as /devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.0/rc/rc0/input7
Feb 10 16:12:38 (MLD) user.info kernel: [   73.177634] rc rc0: X10 WTI RF receiver as /devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.0/rc/rc0
Feb 10 16:12:38 (MLD) user.info kernel: [   73.178000] input: X10 WTI RF receiver mouse as /devices/pci0000:00/0000:00:04.0/usb3/3-3/3-3:1.0/input/input8
Feb 10 16:12:38 (MLD) user.info kernel: [   73.178969] usbcore: registered new interface driver ati_remote
MLD 6.5_x86_64 - Reycom REC 100 S2-CI

Offline cs-7

  • Adv. Member
  • ***
  • Posts: 104
    • View Profile
Remote Medion X10 for MCC-100
« Reply #8 on: February 10, 2026, 17:56:44 »
According to the MLD 5.3 output, there should be a usb device. In MLD 6.5 is "lsub" showing the device? You have to install usbutils to have text output, without usbutils you get only a numerical output.
Server-VDR: VM (x86) MLD-6.5 / Client-VDR: RPI4, Argon ONE M.2, MLD-6.5 / SAT: DD Octopus Net, SCR LNB, Satman 65

Online Marcin

  • Member
  • **
  • Posts: 60
    • View Profile
Remote Medion X10 for MCC-100
« Reply #9 on: February 10, 2026, 18:13:40 »
I have this:

Code: [Select]
root@MLDOS:~# lsusb                                                                         
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub                               
Bus 001 Device 002: ID 0bc7:000c X10 Wireless Technology, Inc. Transceiver (ACPI-compliant) 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub                               
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub                               
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub                               
Bus 004 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard                     
root@MLDOS:~#                                                                               

MLD 6.5_x86_64 - Reycom REC 100 S2-CI

Offline cs-7

  • Adv. Member
  • ***
  • Posts: 104
    • View Profile
Remote Medion X10 for MCC-100
« Reply #10 on: February 10, 2026, 18:22:16 »
Just a guess, can you try loading the kernel module ati_remote  (modprobe ati_remote) and check the output of dmesg.
Server-VDR: VM (x86) MLD-6.5 / Client-VDR: RPI4, Argon ONE M.2, MLD-6.5 / SAT: DD Octopus Net, SCR LNB, Satman 65

Online Marcin

  • Member
  • **
  • Posts: 60
    • View Profile
Remote Medion X10 for MCC-100
« Reply #11 on: February 10, 2026, 18:36:38 »
Code: [Select]
usbcore: registered new interface driver ati_remote 
MLD 6.5_x86_64 - Reycom REC 100 S2-CI

Offline cs-7

  • Adv. Member
  • ***
  • Posts: 104
    • View Profile
Remote Medion X10 for MCC-100
« Reply #12 on: February 10, 2026, 18:39:42 »
I'm sorry, this was maybe misleading. My system also loads the diver and there is no rf device.
Is the X10 device listed in "cat /proc/bus/input/devices"?
Server-VDR: VM (x86) MLD-6.5 / Client-VDR: RPI4, Argon ONE M.2, MLD-6.5 / SAT: DD Octopus Net, SCR LNB, Satman 65

Online Marcin

  • Member
  • **
  • Posts: 60
    • View Profile
Remote Medion X10 for MCC-100
« Reply #13 on: February 10, 2026, 18:44:33 »
Code: [Select]
root@MLDOS:~# cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0

I: Bus=0003 Vendor=1a2c Product=2d23 Version=0110
N: Name="USB USB Keyboard"
P: Phys=usb-0000:00:06.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.0/0003:1A2C:2D23.0001/input/input5
U: Uniq=
H: Handlers=sysrq kbd leds event2
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff800000000007ff febeffdff3cfffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=1a2c Product=2d23 Version=0110
N: Name="USB USB Keyboard Consumer Control"
P: Phys=usb-0000:00:06.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.1/0003:1A2C:2D23.0002/input/input6
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=1f
B: KEY=33eff 0 0 483ffff17aff32d bfd4444600000000 1 130c730b17c000 267bfad9415fed 9e168000004400 10000002
B: REL=1040
B: ABS=100000000
B: MSC=10

I: Bus=0003 Vendor=1a2c Product=2d23 Version=0110
N: Name="USB USB Keyboard System Control"
P: Phys=usb-0000:00:06.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.1/0003:1A2C:2D23.0002/input/input7
U: Uniq=
H: Handlers=kbd event4
B: PROP=0
B: EV=13
B: KEY=c000 10000000000000 0
B: MSC=10

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA NVidia HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:08.0/sound/card0/input8
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0003 Vendor=0fac Product=0ade Version=0000
N: Name="keyd virtual keyboard"
P: Phys=
S: Sysfs=/devices/virtual/input/input9
U: Uniq=
H: Handlers=sysrq rfkill kbd event6
B: PROP=0
B: EV=100003
B: KEY=10000000000000 0 ffffffffffffff0f ffffffffffffffff ffffffffffffffff fffffffffffffffe

I: Bus=0003 Vendor=0fac Product=1ade Version=0000
N: Name="keyd virtual pointer"
P: Phys=
S: Sysfs=/devices/virtual/input/input10
U: Uniq=
H: Handlers=mouse0 event7
B: PROP=0
B: EV=f
B: KEY=ff0000 0 0 0 0
B: REL=147
B: ABS=3

root@MLDOS:~#




There is no remote here?

MLD 6.5_x86_64 - Reycom REC 100 S2-CI

Offline cs-7

  • Adv. Member
  • ***
  • Posts: 104
    • View Profile
Remote Medion X10 for MCC-100
« Reply #14 on: February 10, 2026, 18:55:33 »
I'm not an expert but I think no the remote ist not listed in the input devices and this is maybe the reason why the remote is not recognized by the MLD interface. On the other hand the device is recognized by the usb subsystem and listed in the lsusb output.
Server-VDR: VM (x86) MLD-6.5 / Client-VDR: RPI4, Argon ONE M.2, MLD-6.5 / SAT: DD Octopus Net, SCR LNB, Satman 65

[1] 2 3 >>> MLD-6.x / General / Remote Medion X10 for MCC-100
 



Users Online Users Online

Marcin and 2 Guests are viewing this topic.