Jarod Wilson <jarod@...> writes:
> On Oct 25, 2010, at 3:49 AM, Hanno Zulla wrote:
> > Hi,
> >> File a package request or something along those lines, I suppose. Not
> >> much that can be done about that on the lirc list. ;)
> > Did that already.
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601279
> Okay, good.
> >> Same person who found that v4l-utils package reported this as well.
> >> The code in the Ubuntu kernel is a bit dated, and I've already tried
> >> talking to Canonical kernel folk about updating assorted ir-core code
> >> in their kernel, but they rejected the idea (doesn't meet the Ubuntu
> >> "Stable Release Update" guidelines), but they may provide a separate
> >> package with (dkms?) modules in it at some point.
> > Ok, will file a bug report to the Ubuntu folks, as well.
> Also good.
> >> Alternatively,
> >> there's a 2.6.36 kernel build for Ubuntu available somewhere, and
> >> (same person again) told me that ir-keytable works just fine with the
> >> imon driver in that kernel.
> > Could you give me a way to contact that person? I'd like to try that, as
> > well.
> I believe they were just installing the kernel from here:
> Hesitant to give out anyone else's contact info, but did let that user know
that others were asking about the
> same issues on the list.
> > Btw, I also tried to revert to the old lirc_imon module, but the
> > existing lirc_imon module from staging which is found in the official
> > Ubuntu Maverick kernel would sabotage that effort.
> No it wouldn't. You can either replace it or just install a second copy in a
path with higher depmod
> precedence. (Note that lirc_imon is largely unmaintained at the moment
> > imon support is definitely broken at this point in Ubuntu Maverick.
> For some users, yourself included, yes. It does work fine for others, and the
issue you're seeing has long
> since been fixed upstream. Personally, I think Ubuntu is a bit too rigid in
their update policies here, but
> then again, it seems they don't have the kernel expertise or manpower to
handle much in the way of anything
> that isn't in the matching stable tree for their kernel, so its probably a
sane self-preservation policy.
I have been looking for a solution to use the ASROCK 330 HT with the remote and
the 2.6.37 kernel.
I run mythtv frontend 0.24 on that machine (using the mythbuntu distro). The
kernel is the ppa version (2.6.37-020637). I also installed from git the v4l-dvb
and v4l-utils and used the ir-keytable -t to monitor scancodes. Also, I
programmed lirc to respond to eventx.
Now the problem is that the codes are picked up apropriately from the ir-
keytable output, including press and release of buttons. However, mythtv jumps
twice for each press and does not respond to all keys (only arrows and clear
work well). Further, if I remove lirc from installation, I have the codes on ir-
keytable -t and there is no jump on the mythtv, i.e. normal response occurs
with the arrow and clear buttons, but nothing else works. I am used to program
mythtv keys but cannot get responses from the remote. I would be happy to uyse
only the in-kernel event process without lirc but how to program mythtv? How to
define shutdown from the power key event? Is this whole behaviour normal and if
so, any place where I can learn howto?