I tried today to get my Hauppauge remote working with my Nova-T card. I'm using Gentoo so I got the 2.6.10-gentoo-r4 kernel, patched it with the latest v4l diff and compiled it. After rebooting I now have /dev/input/event2 but I can't seem to get lirc working. I also realised that I don't have a Hauppauge Grey remote but a Hauppauge Silver which is apparently different.
Anyway, I found that irw was printing all sorts of control characters when I pressed various buttons. That was until I found that it wasn't irw but direct keyboard input from the dvb driver - it prints stuff even if lirc isn't running. The only button that works as it should is OK which seems to map to Enter. Part of /proc/bus/input/devices: I: Bus=0001 Vendor=0070 Product=9002 Version=0001 N: Name="cx88 IR (Hauppauge Nova-T DVB-T" P: Phys=pci-0000:00:0c.2/ir0 H: Handlers=kbd event2 B: EV=100003 B: KEY=108fc000 100022 0 0 0 0 18000 4180 801 9e0000 7bb80 0 10000000 Now maybe I haven't RTFM properly and maybe I'm just getting a little impatient to get it working but I can't seem to bridge the gap between what the dvb driver is providing and where this maps to MythTV or even if lirc is involved along the way. Anyone who can shed some light or point me in the right direction will make me a happy man ;) -- Rob On Monday 24 January 2005 18:33, Ashley Bostock wrote: > You'll find this number might change depending what you have plugged > in to the box, for example if I boot my mythbox with a keyboard > connected to it (normally has nothing connected) then the remote > doesnt work as the keyboard has taken the first /dev/input/event > number and the remote is now been assigned a different one. > > Just thought I'd mention it incase you find your remote stops working > out of the blue... > > Ash. > > > On Mon, 24 Jan 2005 14:56:01 +0000, Mark Howells <[EMAIL PROTECTED]> wrote: > > On Thu, 20 Jan 2005 14:08:29 +0200, Kalle Pokki <[EMAIL PROTECTED]> wrote: > > > Mark Howells wrote: > > > > > > > > >Also, pressing keys other than 0-9 doesn't cause any events at event0 > > > >either - so even using lirc I'd be know better off at the moment... :( > > > > > > Are you sure it is event0 you should be watching? You can check > > > /proc/bus/input/devices to find out the correct event number. Mine is > > > event5, for example. > > > > Doh! (event2) I recently switched from a 2.4 to 2.6 kernel and I've > > been using event0 for so long I forgot to check. Thanks for that. > > > > Mark > > > > > > _______________________________________________ > > mythtv-users mailing list > > mythtv-users@mythtv.org > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > > > > > _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users