[pvrusb2] IR receiver does not see anything

[Mike Isely]

On Mon, 14 May 2007, Siddhartha Jain wrote:

> Success finally!! I missed loading the i2c_dev module. Once I followed
> this order of loading modules, everything worked.
> modprobe i2c_dev (i2c_core was already loaded for the motherboardboard
> i2c device)
> modprobe i2c-algo-bit
> modprobe lirc_i2c
> 
> The real i2c IR device shows up as /dev/lirc1, so run lircd to listen on that:
> /usr/local/lirc/sbin/lircd -d /dev/lirc1
> 
> What worked:
> - WinTV_PVR-USB2 (fourth version with IR blaster and the new PVR-350
> kind of remote)
> http://www.mythtv.org/wiki/index.php/PVR-350_Remote_Quick_Guide
> 
> - Kernel 2.6.21 with the in-tree pvrusb2 module on CentOS 4.4
> - lirc 0.8.2pre2
> 
> Here is what you see in /var/log/messages:
> ======================================
> i2c /dev entries driver
> lirc_dev: IR Remote Control driver registered, at major 61
> lirc_i2c: no version for "lirc_unregister_plugin" found: kernel tainted.
> bttv: driver version 0.9.17 loaded
> bttv: using 8 buffers with 2080k (520 pages) each for capture
> cx2388x v4l2 driver version 0.0.6 loaded
> lirc_i2c: chip found @ 0x18 (Hauppauge IR)
> lirc_dev: lirc_register_plugin: sample_rate: 10
> lirc_i2c: chip found @ 0x71 (Hauppauge IR (PVR150))
> lirc_dev: lirc_register_plugin: sample_rate: 10
> ======================================
> 
> The device found @ 0x18 is the fake one emulated by the pvrusb2 driver.
> 
> Hope this helps others,
> 
> - Siddhartha
> 

Siddhartha:

Thanks for tracking this down - and describing the solution!

  -Mike

-- 
                        |         Mike Isely          |     PGP fingerprint
     Spammers Die!!     |                             | 03 54 43 4D 75 E5 CC 92
                        |   isely @ pobox (dot) com   | 71 16 01 E2 B5 F5 C1 E8
                        |                             |