Description of problem: The lirc dev of i2c IR (HVR 1110) is no longer detected Version-Release number of selected component (if applicable): Is working with kernel-PAE-2.6.35.9-64.fc14 Not detected by kernel-PAE-2.6.35.10-72.fc14.i686 and kernel-PAE-2.6.35.10-74.fc14.i686 How reproducible: On every reboot. Steps to Reproduce: 1. reboot 2. dmesg Actual results: dmesg on new kernel contains only: [ 27.347368] lirc_dev: IR Remote Control driver registered, major 250 [ 27.350985] IR LIRC bridge handler initialized [ 27.352150] tuner 4-004b: chip found @ 0x96 (saa7133[0]) [ 27.387014] tda829x 4-004b: setting tuner address to 61 [ 27.589070] tda829x 4-004b: type set to tda8290+75a Expected results: dmesg on working kernel: [ 27.356566] lirc_dev: IR Remote Control driver registered, major 250 [ 27.361030] tda829x 4-004b: type set to tda8290+75a [ 27.388486] IR LIRC bridge handler initialized [ 30.083060] Registered IR keymap rc-hauppauge-new [ 30.083212] input: i2c IR (HVR 1110) as /devices/virtual/rc/rc0/input5 [ 30.083292] rc0: i2c IR (HVR 1110) as /devices/virtual/rc/rc0 [ 30.083296] ir-kbd-i2c: i2c IR (HVR 1110) detected at i2c-4/4-0071/ir0 [saa7133[0]] Additional info:
Mauro, do you know of any upstream ir-kbd-i2c changes that would account for this?
There are two hauppauge IR's, and only one is supported by rc-hauppauge-new. Maybe that is the problem. Andreas, Could you please modprobe saa7134 with IR debug enabled, and post the results when you type something on the IR to this bugzilla?
Sorry, you should be enabling debug at ir-kbd-i2c, as this device uses an I2C IR chip.
Hmm... from your logs, it seems that ir-kbd-i2c didn't even detected anything at I2C address 0x71. That's weird. Forget comments #2 and #3. Or there's a regression at ir-kbd-i2c, related to its probe function, or saa7134 is not detecting anything at I2C address 0x71. Could you please modprobe saa7134 with two debug options: modprobe saa7134 i2c_debug=1 i2c_scan=1 This should print a message if something is found at address 0x71.
Created attachment 473532 [details] parts of dmsg concerning saa7134
Hi Mauro, thank you for investigating time into solving this problem. Since I failed to unload the saa7134 module I added the options to /etc/modprobe.d/... The corresponding part of dmesg is in the previous message.
I *think* the fix for this was merged upstream (courtesy of Andy Walls), and should be included in F14 kernel build 2.6.35.10-78.fc14.
Hello Jason, could you be more specific regarding the fix code from Andy Walls ? I'm having the same error with a Hauppauge HVR-1150 (the successor of the 1120) and would like to try and help fix it.
(In reply to comment #8) > Hello Jason, could you be more specific regarding the fix code from Andy Walls > ? I'm having the same error with a Hauppauge HVR-1150 (the successor of the > 1120) and would like to try and help fix it. I meant, *Jarod* - I apologize for the confusion...
Actually, there's one additional saa7134 patch that may be necessary that Mauro just authored for upstream. Andy's piece was to add back ir-kbd-i2c accepting 0x71 as a valid receiver address, but there's also something that was broken with the ir_raw_event_store_edge() function, which some saa7134 cards use to store up raw IR events for decode. Fix for the latter, not yet merged in Fedora 14's kernel: https://patchwork.kernel.org/patch/492791/
kernel-2.6.35.11-83.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.11-83.fc14
kernel-2.6.35.11-83.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.