[Marcin]

I loaded the kernel modules:
ati_remote  (modprobe ati_remote)
rc_medion_x10_or2x (modprobe rc_medion_x10_or2x)
and I have:

Code: [Select]

root@MLDOS:~# lsmod
Module                  Size  Used by
rc_medion_x10_or2x     12288  0
ati_remote             16384  0
rc_core                45056  2 ati_remote,rc_medion_x10_or2x
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
snd_hda_codec_hdmi     65536  1
snd_hda_codec_realtek   155648  1
snd_hda_codec_generic    81920  1 snd_hda_codec_realtek
ledtrig_audio          12288  1 snd_hda_codec_generic
cfg80211              987136  0
stv090x                73728  2
snd_hda_intel          40960  0
ddbridge              167936  20
snd_intel_dspcfg       12288  1 snd_hda_intel
nvidia              10543104  57
cxd2099                16384  1 ddbridge
snd_hda_codec         126976  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
wmi_bmof               12288  0
dvb_core              122880  1 ddbridge
snd_hda_core           90112  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_pcm               131072  5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
mc                     49152  1 dvb_core
i2c_nforce2            12288  0
coretemp               12288  0
snd_timer              36864  2 snd_pcm
wmi                    28672  1 wmi_bmof
sch_fq_codel           16384  2
fuse                  147456  1
configfs               40960  1
nfnetlink              16384  2
root@MLDOS:~#



[clausmuus]

Maybe the remote will be registered as real keyboard (and not as HID keyboard). Or it will be only registered as lirc device. Only HID devices can be configured by the setup.
If it's a real keyboard, then at minimum the number keys should work.
You can also call "evtest" to see if your remote was activated, and also test with that tool, if key press events are received.

[Marcin]

You're right.
Perhaps someone knows how to show this to the system so it can be selected in the settings.

[clausmuus]

what do you want to select in the settings?

[Marcin]

Just like in the picture?

[clausmuus]

That is only possible for remote controls that are registered as HID keyboards.

[Marcin]

Evtest dont see remote. I check all 8 devices.

Code: [Select]

root@MLDOS:~# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      Power Button
/dev/input/event1:      Power Button
/dev/input/event2:      USB USB Keyboard
/dev/input/event3:      USB USB Keyboard Consumer Control
/dev/input/event4:      USB USB Keyboard System Control
/dev/input/event5:      HDA NVidia HDMI/DP,pcm=3
/dev/input/event6:      keyd virtual keyboard
/dev/input/event7:      keyd virtual pointer
Select the device event number [0-7]:



[Marcin]

Can lirc help me in this situation?

[clausmuus]

Maybe, maybe not. The big question is, what kind of device is it (the receiver). Lirc can only help, if it's a lirc supported device.

Often such integrated receivers need special software. In such a case we can't help you.
So, if you find a documentation, how to enable exactly this device on linux systems, we can maybe help you.

[rfehr]

Could you take a picture of the receiver?

[cs-7]

Can lirc help me in this situation?

If I've got you right, the remote is working in MLD 5.3, so have you checked if lirc is running and checked the config files. Maybe this give a hint how to get it working.

[Marcin]

Yes, of course.

[rfehr]

Yes, of course.

But that's not the receiver, it's the sender.

[Marcin]

Soory.

[rfehr]

Soory.

Oh, the MCC-100, that's really old.

I don't think anyone has ever tested it with the MLD 6.5.