Benji Mouse wrote: > Hi folks. I recently lost the hard disk in my year-old VDR system and have > had to rebuild from almost scratch. Everything is working except for the > remote/keyboard. I've gone over things time and time again, but don't see > anywhere that I've made a mistake. I've done quite a bit of searching (web > and mailing list) and haven't found anything really helpful. I'm hoping > someone here can point me in the right direction. > > Like I said in the subject, VDR will see the remote and keyboard long enough > to create the remote.conf file, but when configuration is complete and VDR > switches to normal 'show video' mode, both the remote and keyboard are > ignored. Note: If there are many non-vdr files in your video directory it may take a long time until vdr responds to user input. > Note that evtest output is normal, and that with IR debugging enabled, the > remote keypresses show up in the log as expected. > > Installation details (note- I've tried to rebuild the system the same as it > was prior to the crash): > * Vanilla installation of Debian Sarge, 2.6.8 kernel recompiled from > Debian-provided sources using the kernel config from the original (working) > system. > * In-kernel (non-CVS) DVB driver > * Full featured Nexus card with the grey remote > * VDR 1.3.20 compiled from source > * Remote plugin version 0.3.3 > * Loading hauppauge_grey.rc5 via av7110_loadkeys after inserting dvb-ttpci, > prior to running VDR > * Running VDR from the command line (not as a daemon) via ssh and screen. > > I don't see anything out of place in the syslog: > > Nov 29 22:13:31 localhost vdr[3539]: VDR version 1.3.20 started > Nov 29 22:13:31 localhost vdr[3539]: loading plugin: ./PLUGINS/lib/libvdr- > remote.so.1.3.20 > Nov 29 22:13:31 localhost vdr[3539]: loading /vdr_video/setup.conf > Nov 29 22:13:31 localhost vdr[3539]: loading /vdr_video/sources.conf > Nov 29 22:13:31 localhost vdr[3539]: loading /vdr_video/diseqc.conf > Nov 29 22:13:31 localhost vdr[3539]: loading /vdr_video/channels.conf > Nov 29 22:13:31 localhost vdr[3539]: loading /vdr_video/ca.conf > Nov 29 22:13:31 localhost vdr[3539]: loading /vdr_video/remote.conf > Nov 29 22:13:31 localhost vdr[3539]: probing /dev/dvb/adapter0/frontend0 > Nov 29 22:13:31 localhost vdr[3542]: tuner on device 1 thread started > (pid=3542, tid=16386) > Nov 29 22:13:31 localhost vdr[3543]: Section handler thread started > (pid=3543, tid=32771) > Nov 29 22:13:31 localhost vdr[3539]: probing /dev/dvb/adapter1/frontend0 > Nov 29 22:13:31 localhost vdr[3539]: found 1 video device > Nov 29 22:13:31 localhost vdr[3539]: initializing plugin: remote (0.3.3): > Remote control > Nov 29 22:13:31 localhost vdr[3539]: setting primary device to 1 > Nov 29 22:13:31 localhost vdr[3539]: SVDRP listening on port 2001 > Nov 29 22:13:31 localhost vdr[3539]: loading /vdr_video/themes/classic- > default.theme > Nov 29 22:13:31 localhost vdr[3539]: starting plugin: remote > Nov 29 22:13:31 localhost vdr[3539]: device /dev/input/event0: DVB on-card > IR receiver > Nov 29 22:13:31 localhost vdr[3539]: remote: using '/dev/input/event0' > Nov 29 22:13:31 localhost vdr[3539]: remote-event0: autorepeat supported > Nov 29 22:13:31 localhost vdr[3539]: remote-event0: exclusive access granted > Nov 29 22:13:31 localhost vdr[3539]: loading /vdr_video/themes/classic- > default.theme > Nov 29 22:13:31 localhost vdr[3545]: KBD remote control thread started > (pid=3545, tid=65541) > Nov 29 22:13:31 localhost vdr[3539]: remote control remote-event0 - keys > known > Nov 29 22:13:31 localhost vdr[3539]: remote control KBD - keys known > Nov 29 22:13:31 localhost vdr[3539]: switching to channel 177 > Nov 29 22:13:31 localhost vdr[3539]: setting audio track to 1 > > Here are some keypresses from the log - > > Nov 29 22:28:08 localhost kernel: #########000007e5######### addr 31 data > 0x25 (keycode 38) > Nov 29 22:28:08 localhost kernel: #########00000fe0######### addr 31 data > 0x20 (keycode 33) > Nov 29 22:28:09 localhost kernel: #########000007e1######### addr 31 data > 0x21 (keycode 34) > Nov 29 22:28:09 localhost kernel: #########00000fd1######### addr 31 data > 0x11 (keycode 18) > Nov 29 22:28:10 localhost kernel: #########000007d0######### addr 31 data > 0x10 (keycode 17) Hm - these values look like the built-in keymap of the remote plugin, not like codes of hauppauge_grey.rc5. > And the related entries from remote.conf > > remote-event0._Setup /proc/av7110_ir 00000000 31 > remote-event0.Ok 0000000100010026 > remote-event0.Up 0000000100010021 > remote-event0.Down 0000000100010022 > remote-event0.Left 0000000100010012 > remote-event0.Right 0000000100010011 Same codes as above. > I'm really running into a wall here. What am I missing? Are you sure that you posted the correct logs and remote.conf? - With your pre-loaded keymap the 'remote-event0._Setup' line should not exist. Key codes should be different. - With 'remote-event0._Setup' there should be a line like "remote-event0: keymap loaded '/proc/av7110_ir' flags xxxx" in your syslog. Anyway, it seems that during key-learning - hauppauge_grey.rc5 was not loaded and/or - you did not press a key when you were asked whether you'd like to use a pre-loaded keymap. Does this configuration work if you remove the av7110_loadkeys command? If you'd like to use your hauppauge_grey keymap: - stop vdr - remove all remote-event lines from remote.conf - make sure that the keymap is loaded - start vdr - key-learning will start - "Press any key to use a pre-loaded keymap" -> press a key! - complete key learning as usual HTH, Oliver -- -------------------------------------------------------- VDR Remote Plugin available at http://www.escape-edv.de/endriss/vdr/ --------------------------------------------------------
