On Feb 20, 2008 4:54 PM, Nicolas Will <<a href="mailto:nico@youplala.net">nico@youplala.net</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c"><br>On Wed, 2008-02-20 at 16:39 +0900, Matthew Vermeulen wrote:<br>> On Feb 20, 2008 7:09 AM, Nicolas Will <<a href="mailto:nico@youplala.net">nico@youplala.net</a>> wrote:<br>
><br>><br>> On Wed, 2008-02-20 at 06:10 +0900, Matthew Vermeulen wrote:<br>> > Hi all... I'm seeing exactly the same problems everyone else<br>> is (log<br>> > flooding etc) except that I can't seem to get any keys<br>
> picked by lirc<br>> > or /dev/input/event7 at all...<br>> ><br>> > Would this patch help in this case?<br>><br>><br>> It would help with the flooding, most probably, though there<br>
> was a patch<br>> for that available before.<br>><br>> As for LIRC not picking up the event, I would be tempted to<br>> say no, it<br>> won't help.<br>><br>
> Are you certain that your LIRC is configured properly? Are you<br>> certain<br>> that your event number is the right one?<br>><br>><br>> Nico<br>><br>> I believe so... in so far as I can tell... I sent an email to this<br>
> list about a week ago describing my problems, but there was no<br>> response. (subject: Compro Videomate U500). I've copied it below:<br>><br>> Hi all,<br>><br>> I've still been trying to get the inluded remote with my USB DVB-T<br>
> Tuner working. It's a Compro Videomate U500 - it useses the dibcom<br>> 7000 chipset. After upgrading to Ubuntu 8.04 (hardy) I can now see the<br>> remote when I do a "cat /proc/bus/input/devices":<br>
><br>> I: Bus=0003 Vendor=185b Product=1e78 Version=0100<br>> N: Name="IR-receiver inside an USB DVB receiver"<br>> P: Phys=usb-0000:00:02.1-4/ir0<br>> S: Sysfs=/devices/pci0000:00/0000 :00:02.1/usb1/1-4/input/input7<br>
> U: Uniq=<br>> H: Handlers=kbd event7<br>> B: EV=3<br>> B: KEY=10afc332 2842845 0 0 0 4 80018000 2180 40000801 9e96c0 0 800200<br>> ffc<br><br></div></div>Weird.<br><br>You went through all this, I guess:<br>
<br><a href="http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Remote_control" target="_blank">http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500#Remote_control</a><br><br>And you are running a recent v4l-dvb tree, I assume.<br>
<div class="Ih2E3d"><br>><br>> However, I get now output running irrecord:<br><br></div>I was never too lucky with irrecord on my system, IIRC.<br><div><div></div><div class="Wj3C7c"><br>Nico<br></div></div></blockquote>
<div>Ok - just thought I'd try the patch on the latest tree and see what happens... as expected, it put an end to the syslog flooding - but nothing really has improved... I still see a single error line in the syslog every time I press a key - so obviously the kernel is seeing something happen, but deciding it's unknown and not taking it any further. Something must be wrong with some mappings somewhere.. :S Here's the syslog output anyway - there is one line for every key press:<br>
<br>Feb 20 22:07:07 matthew-desktop kernel: [38161.388548] dib0700: Unknown remote controller key: 12 7E 1 0<br>Feb 20 22:07:09 matthew-desktop kernel: [38162.678839] dib0700: Unknown remote controller key: 18 7C 1 0<br>
Feb 20 22:07:10 matthew-desktop kernel: [38162.906413] dib0700: Unknown remote controller key: 18 7C 1 0<br>Feb 20 22:07:14 matthew-desktop kernel: [38165.183338] dib0700: Unknown remote controller key: 1C 4D 1 0<br>Feb 20 22:07:18 matthew-desktop kernel: [38167.156040] dib0700: Unknown remote controller key: 1F 7D 1 0<br>
Feb 20 22:07:21 matthew-desktop kernel: [38168.598632] dib0700: Unknown remote controller key: 19 43 1 0<br><br>This is very annoying because it seems that polling the syslog every 150ms might even give you something if you could work it out ;) Anyway.. any ideas where to now...?<br>
<br>Cheers,<br><br>Matt<br></div></div><br>-- <br>Matthew Vermeulen<br><a href="http://www.matthewv.id.au/">http://www.matthewv.id.au/</a><br>MatthewV @ <a href="http://irc.freenode.net">irc.freenode.net</a>