[mythtv-users] lirc does not work on kernel 22.214.171.124-83.fc14.i686
Derek & Cindi Cass
cass at casscoenterprises.com
Thu Mar 24 14:25:34 UTC 2011
On Thu, 2011-03-24 at 02:03 -0400, Jarod Wilson wrote:
> On Mar 23, 2011, at 10:22 PM, Gabe Rubin wrote:
> > Hi list,
> > I was using kernel version 126.96.36.199-74.fc14.i686, but upgraded to
> > 188.8.131.52-83.fc14.i686. Now I am unable to use lirc. irw registers
> > no key presses, I notice that while under older kernels, I had a
> > device named /dev/lirc0, this is no longer created under
> > 184.108.40.206-83.fc14.i686. What can I do to correct this? I can't
> > simply roll back to the older kernel because I no longer the nvidia
> > kmdl for that, and it is no longer on atrpms. I am using the PVR-350
> > receiver and a harmony remote configured to mimic the remote that came
> > with the PVR-350.
> modprobe ir-kbd-i2c, use lirc in devinput mode, been covered on this
> list a few times in the past month or two.
> (lirc_i2c is dead, removed from the kernel, and its not coming back)
Jarod, ir-kbd-i2c only applies to Hauppauge remotes. What about mceusb
type remotes? I specifically have the Microsoft IR Keyboard, and I
can't get anything to work at all on this same kernel. Should I expect
to be able to at least get the remote control keys to work? I've tried
the new lirc-mod-mce-0.4.0 posted in January to no avail.
[mythtv at mythbox ~]$ lsmod | grep mceusb
mceusb 17220 0
rc_core 17007 9
Do I need to use devinput and maybe blacklist mceusb? I'm guessing that
this isn't going to work too well at this point as the lirc-mod-mce code
ends up in the lirc default driver, but the in-kernel decoding will use
the devinput driver.
More information about the mythtv-users