Its the lirc_i2c.ko file that is the issue, was that regenerated with dkms? Are you running the 2.6.32-23-generic kernel?
This is my output, and it works ...
---
ii liblircclient0 0.8.6-0ubuntu4.1 infra-red remote control support - client li
ii lirc 0.8.6-0ubuntu4.1 infra-red remote control support
ii lirc-modules-source 0.8.6-0ubuntu4.1 infra-red remote control support - kernel mo
ii lirc-x 0.8.6-0ubuntu4.1 infra-red remote control support - X utiliti
Guy,
Its the lirc_i2c.ko file that is the issue, was that regenerated with dkms? Are you running the 2.6.32-23-generic kernel?
This is my output, and it works ...
---
ii liblircclient0 0.8.6-0ubuntu4.1 infra-red remote control support - client li
ii lirc 0.8.6-0ubuntu4.1 infra-red remote control support
ii lirc-modules-source 0.8.6-0ubuntu4.1 infra-red remote control support - kernel mo
ii lirc-x 0.8.6-0ubuntu4.1 infra-red remote control support - X utiliti
---
Jul 6 14:44:10 hyena kernel: [ 54.338335] lirc_dev: IR Remote Control driver registered, major 61 driver: sample_rate: 10
Jul 6 14:44:10 hyena kernel: [ 54.590933] lirc_i2c: chip 0x0 found @ 0x18 (Hauppauge IR)
Jul 6 14:44:10 hyena kernel: [ 54.590937] lirc_dev: lirc_register_
---
/lib/modules/ 2.6.32- 22-generic/ updates/ dkms/lirc_ i2c.ko 2.6.32- 22-generic/ kernel/ ubuntu/ lirc/lirc_ i2c/lirc_ i2c.ko 2.6.32- 23-generic/ updates/ dkms/lirc_ i2c.ko 2.6.32- 23-generic/ kernel/ ubuntu/ lirc/lirc_ i2c/lirc_ i2c.ko
/lib/modules/
/lib/modules/
/lib/modules/
---
uname -r
2.6.32-23-generic