thank you for all the details. so, what you're experiencing is something related to part of the information here (about 'ir_core' and 'rc_core'):
that i've just commented in another e-mail:
"what Jarod Wilson told you is correct in general, but there is one big "but" - we deliberately keep 'ir_core' instead of the new 'rc_core' (as far as i know Jarod Wilson is one of the developers of 'rc_core'), because on our tests with 'rc_core' even on the latest kernels there are constant crashes of the whole system when the new 'rc_core' is in use and that's why we kept the old 'ir_core' - for better user-experience. so, when 'rc_core' reached the necessary stability then we can re-consider to use the new 'rc_core' instead the old 'ir_core'. also, the message you see about 'ir_core' is just a warning and doesn't indicate any error as it might sound from the Jarod's comment."
so, now the whole dilemma is that if we use the new remote control infrastructure, which will result in working 'mceusb' for you then using the 'cx23885' remote control results in unstablility of the whole system and that's what most of our Linux customers use. it seems the only way is 'rc_core' stability with other chips like 'cx23885' to be improved first. i understand that from different points of view it looks different, but from our point of view 'rc_core' broke the stability of 'cx23885' remote control support and that applies not only for TBS hardware, but for all hardware out there that relies on 'cx23885' driver code and thus it's general regression.
* Loading LIRC modules [ OK ]
* Unable to load LIRC kernel modules. Verify your
* selected kernel modules in /etc/lirc/hardware.conf
Aug 20 20:24:55 mythtv-backend kernel: [ 1654.369774] mceusb: disagrees about version of symbol __ir_input_register
Aug 20 20:24:55 mythtv-backend kernel: [ 1654.369785] mceusb: Unknown symbol __ir_input_register (err -22)
Users browsing this forum: No registered users and 2 guests