This looks like a perfect configuration. Should work. ;-)
That's what I thought too :-/
The keyboard exhibits the same behavior as the remote (works through config, but not after). Unless the keyboard is somehow dependant on the remote keymap, wouldn't this indicate something more than just a remote keymap issue?
Keyboard and remote control should be independent.
Let's try to simplify the configuration. Please test whether vdr can be controlled using the keyboard if you do _not_ load the remote plugin.
The behavior is the same - it works during the configuration step, but not afterward.
I wonder what's different between the input handling of the remote configuration step, and the input handling of the running program, and what I could've done to make them behave differently.
Any suggestions on where to go from here?
When I load dvb-ttpci and run av7110_loadkeys with hauppauge_grey, evtest says it sees a 'DVB on-card IR receiver' and displays the keymay for the remote. Fine. Once I start VDR, do the remote setup, and exit, evtest still shows 'DVB on-card IR receiver' , but the keymap displayed is for the keyboard. Is this expected?
I guess you saw the keymap of the remote plugin, not the keymap of the keyboard: The remote plugin replaced your keymap because it wasn't told to keep the pre-loaded keymap...
That makes sense. Thanks.
Benj
On 12/1/05, Benji Mouse benji.the.mouse@gmail.com wrote: <snip>
I wonder what's different between the input handling of the remote configuration step, and the input handling of the running program, and what I could've done to make them behave differently.
Any suggestions on where to go from here?
Sorry I didn't mention this before. If I had noticed it, I would have. It just now occurred to me that something else is wrong. And, I think it shows that the problem that I'm dealing with isn't an input problem at all - it's just a symptom.
When starting VDR, the info banner showing the channel, what's on, etc. is normally displayed for a few seconds. Well it just occurred to me that it's not being displayed at all. When I start VDR, I get the video playing, and that's it - no interface.
I've also discovered that SVDRP isn't working. The log says that it's running on port 2001, but netstat doesn't show anything listening on 2001.
I started looking through the code, and it looks like the input routines and the SVDRP socket construction are all tied to the interface class. This leads me to believe that fixing whatever is causing the interface not to show up may fix the input and SVDRP problems.
Another interesting thing - If I don't load ANY plugins, SVDRP will start (netstat shows it listening on 2001). Of course it won't accept any input, but at least the socket is there. If I load a plugin (remote, for example, but I've verified it with others, also) the socket doesn't show up.
I'm going to keep digging around on my own, but if anyone has any suggestions, I would greatly appreciate them.
Thanks,
Benj.
Benji Mouse wrote:
On 12/1/05, Benji Mouse benji.the.mouse@gmail.com wrote:
<snip> > > I wonder what's different between the input handling of the remote > configuration step, and the input handling of the running program, and > what I could've done to make them behave differently. > > Any suggestions on where to go from here? >
Sorry I didn't mention this before. If I had noticed it, I would have. It just now occurred to me that something else is wrong. And, I think it shows that the problem that I'm dealing with isn't an input problem at all - it's just a symptom.
When starting VDR, the info banner showing the channel, what's on, etc. is normally displayed for a few seconds. Well it just occurred to me that it's not being displayed at all. When I start VDR, I get the video playing, and that's it - no interface.
I've also discovered that SVDRP isn't working. The log says that it's running on port 2001, but netstat doesn't show anything listening on 2001.
I started looking through the code, and it looks like the input routines and the SVDRP socket construction are all tied to the interface class. This leads me to believe that fixing whatever is causing the interface not to show up may fix the input and SVDRP problems.
Another interesting thing - If I don't load ANY plugins, SVDRP will start (netstat shows it listening on 2001). Of course it won't accept any input, but at least the socket is there. If I load a plugin (remote, for example, but I've verified it with others, also) the socket doesn't show up.
I'm going to keep digging around on my own, but if anyone has any suggestions, I would greatly appreciate them.
Hm - just a wild guess: Please verify that you have export LD_ASSUME_KERNEL=2.4.1 line in your start vdr script (runvdr or whatever you use).
Oliver
-
Benji Mouse -
Oliver Endriss