[linux-dvb] Re: Bug in remote driver to AverMedia DVB-T USB 2.0

Michael Krufky mkrufky at m1k.net
Thu Oct 6 21:22:05 CEST 2005


Göran Källqvist wrote:
> Hi!
> I read about the bug in the driver to AverMedia DVB-T USB. I'm experiencing a 
> problem with this driver (the version was downloaded in the end of August, 
> I'm not certain if the mentioned bug should be fixed there). Anyway, I'v 
> managed to get the remote working with lirc (when I realized that the 
> AverMedia remote attached to /dev/input/event and not /dev/lirc). I was able 
> to get the right remote codes when running irw, etc. BUT when I booted the 
> computer next time the system gave the AverMedia USB-box another event slot 
> (it was /dev/input/event3 when I tested it, and that was the value I wrote 
> in /etc/lirc/hardware.conf). Now, however it had got slot event4. The result 
> was that the dvb-usb kept writing "dvb-usb: error while querying for an 
> remote control event." several times per second, both in the terminal and to 
> syslog and daemon.log. End result: the hard drive was written until it was 
> full and the system crashed :-(. I had to remove the USB TV-box and remove 
> the files, and remove the call at boot time to lirc.
> So, my question(s): is it possible to stop the driver polling for the remote 
> after a certain time to avoid this? Or, is it possible to force the kernel 
> (or whatever) to give the USB-box a certain event slot?
> Have anyone heard of this phenomenon earlier?
> Greeting Göran Källqvist, Sweden
> BTW: I'm running Knoppmyth, latest version. Compiled a new kernel (2.6.13) to 
> be able to use the DVB-T USB 2.0.

Sounds like udev needs some guidance...

We fixed this in video4linux cvs for the PCI boards using the method  below:


         - Makes the input event device created by the V4L drivers for
           the infrared remote matchable by udev rules.

         Signed-off-by: Rudo Thomas <rudo at matfyz.cz>
         Signed-off-by: Mauro Carvalho Chehab <mchehab at brturbo.com.br>


===================================================================
RCS file: /cvs/video4linux/video4linux/saa7134-input.c,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- video4linux/saa7134-input.c	2005/07/15 21:44:14	1.22
+++ video4linux/saa7134-input.c	2005/09/02 22:00:49	1.23
@@ -1,5 +1,5 @@
  /*
- * $Id: saa7134-input.c,v 1.22 2005/07/15 21:44:14 mchehab Exp $
+ * $Id: saa7134-input.c,v 1.23 2005/09/02 22:00:49 mchehab Exp $
   *
   * handle saa7134 IR remotes via linux kernel input layer.
   *
@@ -569,6 +569,7 @@
  		ir->dev.id.vendor  = dev->pci->vendor;
  		ir->dev.id.product = dev->pci->device;
  	}
+	ir->dev.dev = &dev->pci->dev;
  #endif

  	/* all done */


I'm not sure where to apply the change for your device... It's 
*probably* a no-brainer.  Would the appropriate maintainer please apply 
something like this to the usb video stuff?

...or would the interested party forward this to the appropriate 
maintainer?  (look it up in the MAINTAINERS file inside the kernel source)

...or maybe this belongs to video4linux -- not sure.  I dont have the 
time to research it right now.

-Mike Krufky



More information about the linux-dvb mailing list