From: arandamandi <mes...@ti...> - 2009-03-10 22:29:34
|
Until yesterday lirc works fine Today i have upgraded to kernel 2.6.28.7,try lirc from cvs...and nothing works. Modules loaded if i try irw no answers or really slow (answer only one code per time 00000014e6110000 00 5 lircd.conf.conf )and lircd go to 100% cpu. I try also latest stable 0.48 but nothing.. I use lirc_atiusb module. -- View this message in context: http://www.nabble.com/Lirc-broken--tp22444988p22444988.html Sent from the LIRC mailing list archive at Nabble.com. |
From: Jarod W. <ja...@wi...> - 2009-03-10 23:41:35
|
arandamandi wrote: > Until yesterday lirc works fine > Today i have upgraded to kernel > 2.6.28.7,try lirc from cvs...and nothing > works. > Modules loaded if i try > irw no answers or really slow > (answer only one code per time > 00000014e6110000 00 5 lircd.conf.conf > )and lircd go to 100% cpu. > I try also latest stable 0.48 > but nothing.. > I use lirc_atiusb module. I have an inkling what might be up. Christoph has been merging the changes Janne and myself have been making in a git tree prepping lirc for the upstream kernel back into lirc cvs (but painstakingly trying to maintain backwards compatibility). The recent kfifo changes merged back into lirc_dev.{c,h} may well still need to be accounted for in lirc_atiusb.c. Might be worth trying out the 0.8.5pre1 snap to see if that's still working or not (its pre-kfifo merge, so if that's the problem, it ought to). --jarod |
From: Jarod W. <ja...@wi...> - 2009-03-11 00:25:30
|
Jarod Wilson wrote: > arandamandi wrote: >> Until yesterday lirc works fine >> Today i have upgraded to kernel >> 2.6.28.7,try lirc from cvs...and nothing >> works. >> Modules loaded if i try >> irw no answers or really slow >> (answer only one code per time >> 00000014e6110000 00 5 lircd.conf.conf >> )and lircd go to 100% cpu. >> I try also latest stable 0.48 >> but nothing.. >> I use lirc_atiusb module. > > I have an inkling what might be up. Christoph has been merging the > changes Janne and myself have been making in a git tree prepping lirc > for the upstream kernel back into lirc cvs (but painstakingly trying to > maintain backwards compatibility). The recent kfifo changes merged back > into lirc_dev.{c,h} may well still need to be accounted for in > lirc_atiusb.c. Might be worth trying out the 0.8.5pre1 snap to see if > that's still working or not (its pre-kfifo merge, so if that's the > problem, it ought to). Hrm, no, don't see anything on the kfifo front that still needed merging, Christoph is quite thorough... :) (Doesn't mean this issue isn't kfifo-related though) --jarod |
From: <li...@ba...> - 2009-03-11 07:44:03
|
Hi! Jarod Wilson "ja...@wi..." wrote: [...] >>> 2.6.28.7,try lirc from cvs...and nothing >>> works. [...] > (Doesn't mean this issue isn't kfifo-related though) Indeed, seems to be kfifo related. I've disabled the kfifo code for now and hope I can take a look later today. Christoph |
From: VDR U. <use...@gm...> - 2009-03-11 00:45:42
|
On Tue, Mar 10, 2009 at 4:41 PM, Jarod Wilson <ja...@wi...> wrote: >> Until yesterday lirc works fine >> Today i have upgraded to kernel >> 2.6.28.7,try lirc from cvs...and nothing >> works. >> Modules loaded if i try >> irw no answers or really slow >> (answer only one code per time >> 00000014e6110000 00 5 lircd.conf.conf >> )and lircd go to 100% cpu. >> I try also latest stable 0.48 >> but nothing.. >> I use lirc_atiusb module. > > I have an inkling what might be up. Christoph has been merging the > changes Janne and myself have been making in a git tree prepping lirc > for the upstream kernel back into lirc cvs (but painstakingly trying to > maintain backwards compatibility). The recent kfifo changes merged back > into lirc_dev.{c,h} may well still need to be accounted for in > lirc_atiusb.c. Might be worth trying out the 0.8.5pre1 snap to see if > that's still working or not (its pre-kfifo merge, so if that's the > problem, it ought to). I can confirm that the cvs from today does not work with kernel 2.6.28.7... I'm seeing things like: read invalid data from device /dev/lirc and Mar 10 17:03:38 test lircd-0.8.5-CVS[2741]: accepted new client on /dev/lircd Mar 10 17:03:38 test lircd-0.8.5-CVS[2741]: removed client The good news is that I downloaded lirc-0.8.5pre1 as you suggested and lirc is working fine now. So, whatever changed between lirc-0.8.5pre1 and todays cvs, something got broken. I'm using Debian Testing btw. Lemme know if I can be of any more help. Best regards, -Derek |
From: arandamandi <mes...@ti...> - 2009-03-11 13:37:50
|
Jarod Wilson wrote: > > arandamandi wrote: >> Until yesterday lirc works fine >> Today i have upgraded to kernel >> 2.6.28.7,try lirc from cvs...and nothing >> works. >> Modules loaded if i try >> irw no answers or really slow >> (answer only one code per time >> 00000014e6110000 00 5 lircd.conf.conf >> )and lircd go to 100% cpu. >> I try also latest stable 0.48 >> but nothing.. >> I use lirc_atiusb module. > > I have an inkling what might be up. Christoph has been merging the > changes Janne and myself have been making in a git tree prepping lirc > for the upstream kernel back into lirc cvs (but painstakingly trying to > maintain backwards compatibility). The recent kfifo changes merged back > into lirc_dev.{c,h} may well still need to be accounted for in > lirc_atiusb.c. Might be worth trying out the 0.8.5pre1 snap to see if > that's still working or not (its pre-kfifo merge, so if that's the > problem, it ought to). > > --jarod > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > I try 0.8.5pre1 and works perfect. Thanks -- View this message in context: http://www.nabble.com/Lirc-broken--tp22444988p22455257.html Sent from the LIRC mailing list archive at Nabble.com. |
From: Jarod W. <ja...@wi...> - 2009-03-11 14:13:14
|
On Tuesday 10 March 2009 20:45:21 VDR User wrote: > On Tue, Mar 10, 2009 at 4:41 PM, Jarod Wilson <ja...@wi...> wrote: > >> Until yesterday lirc works fine > >> Today i have upgraded to kernel > >> 2.6.28.7,try lirc from cvs...and nothing > >> works. > >> Modules loaded if i try > >> irw no answers or really slow > >> (answer only one code per time > >> 00000014e6110000 00 5 lircd.conf.conf > >> )and lircd go to 100% cpu. > >> I try also latest stable 0.48 > >> but nothing.. > >> I use lirc_atiusb module. > > > > I have an inkling what might be up. Christoph has been merging the > > changes Janne and myself have been making in a git tree prepping lirc > > for the upstream kernel back into lirc cvs (but painstakingly trying to > > maintain backwards compatibility). The recent kfifo changes merged back > > into lirc_dev.{c,h} may well still need to be accounted for in > > lirc_atiusb.c. Might be worth trying out the 0.8.5pre1 snap to see if > > that's still working or not (its pre-kfifo merge, so if that's the > > problem, it ought to). > > I can confirm that the cvs from today does not work with kernel > 2.6.28.7... I'm seeing things like: > > read invalid data from device /dev/lirc > > and > > Mar 10 17:03:38 test lircd-0.8.5-CVS[2741]: accepted new client on /dev/lircd > Mar 10 17:03:38 test lircd-0.8.5-CVS[2741]: removed client > > The good news is that I downloaded lirc-0.8.5pre1 as you suggested and > lirc is working fine now. So, whatever changed between lirc-0.8.5pre1 > and todays cvs, something got broken. > > I'm using Debian Testing btw. Lemme know if I can be of any more help. What receiver was that with? My imon, mceusb and mceusb2 receivers all work with the kfifo changes, haven't tried my own remote wonder 2 yet. -- Jarod Wilson ja...@wi... |
From: VDR U. <use...@gm...> - 2009-03-11 14:28:23
|
On Wed, Mar 11, 2009 at 7:12 AM, Jarod Wilson <ja...@wi...> wrote: >> I can confirm that the cvs from today does not work with kernel >> 2.6.28.7... I'm seeing things like: >> >> read invalid data from device /dev/lirc >> >> and >> >> Mar 10 17:03:38 test lircd-0.8.5-CVS[2741]: accepted new client on /dev/lircd >> Mar 10 17:03:38 test lircd-0.8.5-CVS[2741]: removed client >> >> The good news is that I downloaded lirc-0.8.5pre1 as you suggested and >> lirc is working fine now. So, whatever changed between lirc-0.8.5pre1 >> and todays cvs, something got broken. >> >> I'm using Debian Testing btw. Lemme know if I can be of any more help. > > What receiver was that with? My imon, mceusb and mceusb2 receivers all work > with the kfifo changes, haven't tried my own remote wonder 2 yet. I'm using a serial IR receiver. |
From: Jarod W. <ja...@wi...> - 2009-03-12 17:18:50
|
On Wednesday 11 March 2009 10:28:13 VDR User wrote: > On Wed, Mar 11, 2009 at 7:12 AM, Jarod Wilson <ja...@wi...> wrote: > >> I can confirm that the cvs from today does not work with kernel > >> 2.6.28.7... I'm seeing things like: > >> > >> read invalid data from device /dev/lirc > >> > >> and > >> > >> Mar 10 17:03:38 test lircd-0.8.5-CVS[2741]: accepted new client on /dev/lircd > >> Mar 10 17:03:38 test lircd-0.8.5-CVS[2741]: removed client > >> > >> The good news is that I downloaded lirc-0.8.5pre1 as you suggested and > >> lirc is working fine now. So, whatever changed between lirc-0.8.5pre1 > >> and todays cvs, something got broken. > >> > >> I'm using Debian Testing btw. Lemme know if I can be of any more help. > > > > What receiver was that with? My imon, mceusb and mceusb2 receivers all work > > with the kfifo changes, haven't tried my own remote wonder 2 yet. > > I'm using a serial IR receiver. So lirc_serial was a known-busted entity with kfifos, but with some minor changes, I've got it working locally now. Should get into cvs RSN... -- Jarod Wilson ja...@wi... |
From: VDR U. <use...@gm...> - 2009-03-12 18:20:59
|
On Thu, Mar 12, 2009 at 10:18 AM, Jarod Wilson <ja...@wi...> wrote: > So lirc_serial was a known-busted entity with kfifos, but with some minor > changes, I've got it working locally now. Should get into cvs RSN... That's the kinda news I like to hear! :) |