From: Adam W. <awi...@ma...> - 2007-08-29 05:09:51
|
Much to my chagrin, lirc has stopped working :\. We (Mandriva) are shipping kernel 2.6.22 in our next release. I found out a few months back that lirc 0.8.2 does not work with kernel 2.6.22, so I've stuck to a 2.6.17 kernel for now. But now we've updated our lirc modules / userspace stuff to latest CVS, which is supposed to work with 2.6.22, so I thought I'd test it out. It's not working... with a configuration that previously worked with kernel 2.6.17 and lirc 0.8.2, what now happens is that irw shows nothing. There's no error messages - the modules load, lircd loads and from its log messages seems to be working properly - but irw just doesn't show anything. Also, if I stop lircd and try mode2 or irrecord, they get nothing either. Hardware is a Hauppauge receiver that came with a WinTV PCI card, and a Jensen universal remote which I wrote a config file for myself a couple of years ago. Of course, there has to be one really inexplicable thing, and that is...somehow it's now stopped working in 2.6.17 too :\. Unfortunately I can't get back to my exact working configuration from 2.6.17 any more, because we no longer have 0.8.2 lirc packages (Cooker is now at 0.8.3 CVS, and 2007 Spring - our last stable release - shipped with a 0.8.1 CVS snapshot). So I'd rather just focus on getting the current setup working. Configuration files: http://www.happyassassin.net/extras/lircd (/etc/sysconfig/lircd) http://www.happyassassin.net/extras/lircd.conf (/etc/lircd.conf) device file locations are correct - /dev/lirc/0 is correct for our distro. Does anyone have any ideas or suggestions for figuring out what's going wrong? Thanks. -- adamw |
From: Eric S. <sa...@sa...> - 2007-08-29 05:13:42
|
Adam Williamson wrote: > Much to my chagrin, lirc has stopped working :\. > > We (Mandriva) are shipping kernel 2.6.22 in our next release. I found > out a few months back that lirc 0.8.2 does not work with kernel 2.6.22, > so I've stuck to a 2.6.17 kernel for now. But now we've updated our lirc > modules / userspace stuff to latest CVS, which is supposed to work with > 2.6.22, so I thought I'd test it out. It's not working... > > with a configuration that previously worked with kernel 2.6.17 and lirc > 0.8.2, what now happens is that irw shows nothing. There's no error > messages - the modules load, lircd loads and from its log messages seems > to be working properly - but irw just doesn't show anything. Hm, not a lot of help but just as a datapoint, Jarod just tossed lirc into the Fedora 8 test kernels, on 2.6.23-rc$FOO, and reported success... so it does work somewhere at least. :) -Eric |
From: <spa...@co...> - 2007-08-29 16:22:00
|
>>>>> "E" == Eric Sandeen <sa...@sa...> writes: E> Adam Williamson wrote: >> Much to my chagrin, lirc has stopped working :\. >> >> We (Mandriva) are shipping kernel 2.6.22 in our next release. I >> found out a few months back that lirc 0.8.2 does not work with >> kernel 2.6.22, so I've stuck to a 2.6.17 kernel for now. But now >> we've updated our lirc modules / userspace stuff to latest CVS, >> which is supposed to work with 2.6.22, so I thought I'd test it >> out. It's not working... >> >> with a configuration that previously worked with kernel 2.6.17 and >> lirc 0.8.2, what now happens is that irw shows nothing. There's no >> error messages - the modules load, lircd loads and from its log >> messages seems to be working properly - but irw just doesn't show >> anything. E> Hm, not a lot of help but just as a datapoint, Jarod just tossed E> lirc into the Fedora 8 test kernels, on 2.6.23-rc$FOO, and E> reported success... so it does work somewhere at least. :) No problems here with latest cvs, and 2.6.22.5 Good luck |
From: Jarod W. <ja...@wi...> - 2007-08-29 18:43:41
|
On Wednesday 29 August 2007 01:13:44 am Eric Sandeen wrote: > Adam Williamson wrote: > > Much to my chagrin, lirc has stopped working :\. > > > > We (Mandriva) are shipping kernel 2.6.22 in our next release. I found > > out a few months back that lirc 0.8.2 does not work with kernel 2.6.22, > > so I've stuck to a 2.6.17 kernel for now. But now we've updated our lirc > > modules / userspace stuff to latest CVS, which is supposed to work with > > 2.6.22, so I thought I'd test it out. It's not working... > > > > with a configuration that previously worked with kernel 2.6.17 and lirc > > 0.8.2, what now happens is that irw shows nothing. There's no error > > messages - the modules load, lircd loads and from its log messages seems > > to be working properly - but irw just doesn't show anything. > > Hm, not a lot of help but just as a datapoint, Jarod just tossed lirc > into the Fedora 8 test kernels, on 2.6.23-rc$FOO, and reported > success... so it does work somewhere at least. :) And I'll add that I've tested it successfully with both lirc_mceusb and lirc_i2c receivers... What lirc driver does that old WinTV PCI card use? If I'm thinking clearly, that's an old bttv card that may well need lirc_gpio, which is indeed busted w/the latest kernels due to some bttv bits it relied upon being removed from the bttv code. -- Jarod Wilson ja...@wi... |
From: Adam W. <awi...@ma...> - 2007-08-29 16:51:32
|
On Wed, 2007-08-29 at 11:21 -0500, A. P. Kennedy wrote: > >>>>> "E" == Eric Sandeen <sa...@sa...> writes: > > E> Adam Williamson wrote: > >> Much to my chagrin, lirc has stopped working :\. > >> > >> We (Mandriva) are shipping kernel 2.6.22 in our next release. I > >> found out a few months back that lirc 0.8.2 does not work with > >> kernel 2.6.22, so I've stuck to a 2.6.17 kernel for now. But now > >> we've updated our lirc modules / userspace stuff to latest CVS, > >> which is supposed to work with 2.6.22, so I thought I'd test it > >> out. It's not working... > >> > >> with a configuration that previously worked with kernel 2.6.17 and > >> lirc 0.8.2, what now happens is that irw shows nothing. There's no > >> error messages - the modules load, lircd loads and from its log > >> messages seems to be working properly - but irw just doesn't show > >> anything. > > E> Hm, not a lot of help but just as a datapoint, Jarod just tossed > E> lirc into the Fedora 8 test kernels, on 2.6.23-rc$FOO, and > E> reported success... so it does work somewhere at least. :) > > > No problems here with latest cvs, and 2.6.22.5 Well, thanks guys, it's great to know it works for everyone else ;). Care to send me your hardware? ;) -- adamw |
From: Adam W. <awi...@ma...> - 2007-08-29 19:41:04
|
On Wed, 2007-08-29 at 14:43 -0400, Jarod Wilson wrote: > On Wednesday 29 August 2007 01:13:44 am Eric Sandeen wrote: > > Adam Williamson wrote: > > > Much to my chagrin, lirc has stopped working :\. > > > > > > We (Mandriva) are shipping kernel 2.6.22 in our next release. I found > > > out a few months back that lirc 0.8.2 does not work with kernel 2.6.22, > > > so I've stuck to a 2.6.17 kernel for now. But now we've updated our lirc > > > modules / userspace stuff to latest CVS, which is supposed to work with > > > 2.6.22, so I thought I'd test it out. It's not working... > > > > > > with a configuration that previously worked with kernel 2.6.17 and lirc > > > 0.8.2, what now happens is that irw shows nothing. There's no error > > > messages - the modules load, lircd loads and from its log messages seems > > > to be working properly - but irw just doesn't show anything. > > > > Hm, not a lot of help but just as a datapoint, Jarod just tossed lirc > > into the Fedora 8 test kernels, on 2.6.23-rc$FOO, and reported > > success... so it does work somewhere at least. :) > > And I'll add that I've tested it successfully with both lirc_mceusb and > lirc_i2c receivers... > > What lirc driver does that old WinTV PCI card use? If I'm thinking clearly, > that's an old bttv card that may well need lirc_gpio, which is indeed busted > w/the latest kernels due to some bttv bits it relied upon being removed from > the bttv code. Well, it's getting odder and odder: I've hit that classic point where you're wondering how it ever worked *before*. If it helps to identify the card exactly, see this: bttv : Brooktree Corporation|Bt878 Video Capture [MULTIMEDIA_VIDEO] (vendor:109e device:036e subv:0070 subd:13eb) bt878 : Brooktree Corporation|Bt878 Audio Capture [MULTIMEDIA_OTHER] (vendor:109e device:0878 subv:0070 subd:13eb) When it was working, I had both lirc_i2c and lirc_serial being loaded. I've since noticed that if I don't load lirc_serial , I get no /dev/lirc/0 . lirc_i2c loads without problems but creates no device nodes. lirc_serial creates /dev/lirc/0 (and /dev/lirc/lirc0 as a symlink to it) when it's loaded. This doesn't make any sense to me as I'm 99% sure lirc_i2c is supposed to be the driver for this card, and 99% sure lirc_serial is *not* (after all, it's not connected to a serial port in any way shape or form - the TV card's PCI and the receiver connects to it via a 2.5mm connector). I have no IR transceiver connected to any serial port on this machine. I don't *think* lirc_gpio was being loaded at any point in proceedings, but hey, it's an interesting data point. I'll boot back to 2.6.17 and try loading it there. This is getting odder and odder...and, yes, I now have no idea how it ever worked any more. I just know it did. sigh :) (anyone know of a universal remote which also acts as a generic USB wireless keyboard or something so I can do an end run around this whole problem? heh) -- adamw |
From: Jarod W. <ja...@wi...> - 2007-08-30 01:13:05
Attachments:
PGP.sig
|
On Aug 29, 2007, at 15:39, Adam Williamson wrote: > On Wed, 2007-08-29 at 14:43 -0400, Jarod Wilson wrote: >> On Wednesday 29 August 2007 01:13:44 am Eric Sandeen wrote: >>> Adam Williamson wrote: >>>> Much to my chagrin, lirc has stopped working :\. >>>> >>>> We (Mandriva) are shipping kernel 2.6.22 in our next release. I >>>> found >>>> out a few months back that lirc 0.8.2 does not work with kernel >>>> 2.6.22, >>>> so I've stuck to a 2.6.17 kernel for now. But now we've updated >>>> our lirc >>>> modules / userspace stuff to latest CVS, which is supposed to >>>> work with >>>> 2.6.22, so I thought I'd test it out. It's not working... >>>> >>>> with a configuration that previously worked with kernel 2.6.17 >>>> and lirc >>>> 0.8.2, what now happens is that irw shows nothing. There's no error >>>> messages - the modules load, lircd loads and from its log >>>> messages seems >>>> to be working properly - but irw just doesn't show anything. >>> >>> Hm, not a lot of help but just as a datapoint, Jarod just tossed >>> lirc >>> into the Fedora 8 test kernels, on 2.6.23-rc$FOO, and reported >>> success... so it does work somewhere at least. :) >> >> And I'll add that I've tested it successfully with both >> lirc_mceusb and >> lirc_i2c receivers... >> >> What lirc driver does that old WinTV PCI card use? If I'm thinking >> clearly, >> that's an old bttv card that may well need lirc_gpio, which is >> indeed busted >> w/the latest kernels due to some bttv bits it relied upon being >> removed from >> the bttv code. > > Well, it's getting odder and odder: I've hit that classic point where > you're wondering how it ever worked *before*. > > If it helps to identify the card exactly, see this: > > bttv : Brooktree Corporation|Bt878 Video Capture > [MULTIMEDIA_VIDEO] (vendor:109e device:036e subv:0070 subd:13eb) > bt878 : Brooktree Corporation|Bt878 Audio Capture > [MULTIMEDIA_OTHER] (vendor:109e device:0878 subv:0070 subd:13eb) > > When it was working, I had both lirc_i2c and lirc_serial being loaded. > I've since noticed that if I don't load lirc_serial , I get > no /dev/lirc/0 . lirc_i2c loads without problems but creates no device > nodes. lirc_serial creates /dev/lirc/0 (and /dev/lirc/lirc0 as a > symlink > to it) when it's loaded. Not quite sure what's fubar'd there, but loading just lirc_i2c and starting up lircd on one of my boxes yields the following: $ ll /dev/lirc* lrwxrwxrwx 1 root root 5 2007-08-28 22:01 /dev/lirc -> lirc0 crw------- 1 root root 61, 0 2007-08-28 21:54 /dev/lirc0 srw-rw-rw- 1 root root 0 2007-08-28 22:01 /dev/lircd That'd be for a dongle hooked to a WinTV PVR-250 and a 2.6.23-rc3- git10 kernel. No clue why device nodes aren't getting created on your end, though I've not tried with a 2.6.22.z kernel lately... Broken udev, perhaps? > This doesn't make any sense to me as I'm 99% sure lirc_i2c is supposed > to be the driver for this card, and 99% sure lirc_serial is *not* Sounds about right. -- Jarod Wilson ja...@wi... |
From: Adam W. <awi...@ma...> - 2007-08-29 20:09:40
|
On Wed, 2007-08-29 at 12:39 -0700, Adam Williamson wrote: > I don't *think* lirc_gpio was being loaded at any point in proceedings, > but hey, it's an interesting data point. I'll boot back to 2.6.17 and > try loading it there. Nope, that's not it. I tried, it says flat out it doesn't support my card type. So it's not that. -- adamw |
From: Adam W. <awi...@ma...> - 2007-08-30 02:53:40
|
On Wed, 2007-08-29 at 21:13 -0400, Jarod Wilson wrote: > > When it was working, I had both lirc_i2c and lirc_serial being loaded. > > I've since noticed that if I don't load lirc_serial , I get > > no /dev/lirc/0 . lirc_i2c loads without problems but creates no device > > nodes. lirc_serial creates /dev/lirc/0 (and /dev/lirc/lirc0 as a > > symlink > > to it) when it's loaded. > > Not quite sure what's fubar'd there, but loading just lirc_i2c and > starting up lircd on one of my boxes yields the following: > > $ ll /dev/lirc* > lrwxrwxrwx 1 root root 5 2007-08-28 22:01 /dev/lirc -> lirc0 > crw------- 1 root root 61, 0 2007-08-28 21:54 /dev/lirc0 > srw-rw-rw- 1 root root 0 2007-08-28 22:01 /dev/lircd > > That'd be for a dongle hooked to a WinTV PVR-250 and a 2.6.23-rc3- > git10 kernel. No clue why device nodes aren't getting created on your > end, though I've not tried with a 2.6.22.z kernel lately... Broken > udev, perhaps? It's possible, and it'd explain why it doesn't work on 2.6.17.14 any more either. Maybe I'll try with an old udev... -- adamw |
From: Adam W. <awi...@ma...> - 2007-08-30 04:33:52
|
On Wed, 2007-08-29 at 23:06 -0400, Jarod Wilson wrote: > On Aug 29, 2007, at 22:54, Adam Williamson wrote: > > A question - what do you get in /var/log/messages after doing this? > > On modprobe of lirc_i2c: > > Aug 28 21:54:04 apollo kernel: lirc_dev: IR Remote Control driver > registered, major 61 > Aug 28 21:54:04 apollo kernel: bttv: driver version 0.9.17 loaded > Aug 28 21:54:04 apollo kernel: bttv: using 8 buffers with 2080k (520 > pages) each for capture > Aug 28 21:54:05 apollo kernel: cx2388x v4l2 driver version 0.0.6 loaded > Aug 28 21:54:05 apollo kernel: lirc_i2c: chip 0x10020 found @ 0x18 > (Hauppauge IR) > Aug 28 21:54:05 apollo kernel: lirc_dev: lirc_register_plugin: > sample_rate: 10 Heh, well, I bet someone out there had guessed this already, but it turned out to be that oldest of standbys - the Entirely Coincidental Hardware Issue. My TV card had to pick *just* the day this whole new-version-of-lirc thing happened to get unseated or go temporarily nuts or something. Shut down system, open case, re-seat TV card, remove and re-plug IR receiver connector, reboot, and Bob's your uncle - perfect IR functionality with kernel 2.6.22 and the CVS lirc. Sigh. I could've been chasing this one for months. Sorry to waste everyone's time, at least the good news is all the software is working and we'll have working lirc in Mandriva 2008 =). And also I was able to remove a bunch of cruft from my lirc / modprobe config files, heh. -- adamw |
From: Adam W. <awi...@ma...> - 2007-08-30 07:51:28
|
On Wed, 2007-08-29 at 21:32 -0700, Adam Williamson wrote: > Heh, well, I bet someone out there had guessed this already, but it > turned out to be that oldest of standbys - the Entirely Coincidental > Hardware Issue. My TV card had to pick *just* the day this whole > new-version-of-lirc thing happened to get unseated or go temporarily > nuts or something. > > Shut down system, open case, re-seat TV card, remove and re-plug IR > receiver connector, reboot, and Bob's your uncle - perfect IR > functionality with kernel 2.6.22 and the CVS lirc. Sigh. I could've been > chasing this one for months. > > Sorry to waste everyone's time, at least the good news is all the > software is working and we'll have working lirc in Mandriva 2008 =). And > also I was able to remove a bunch of cruft from my lirc / modprobe > config files, heh. The monologue continues =) It's not actually that simple. Following the previous mail, it stopped working again. So now it seems like it stops working after either some time passes or <something> happens. It then will not work again - despite resets or reloading of the module - until I do a cold boot (I've also been removing the power cord for 30 seconds, not sure if that's required, I should test). Until I do this, whenever I load the lirc_i2c module (no matter what kernel or exactly what version of lirc I'm using) it loads but does not detect the hardware. I am now testing whether this happens with the older version of the lirc_i2c module in our 2.6.17 kernel. If it doesn't, then it would seem to be a problem introduced recently in lirc. If it does, then the problem lies elsewhere. Will report with more details tomorrow. -- adamw |
From: Adam W. <awi...@ma...> - 2007-08-30 21:34:09
|
On Thu, 2007-08-30 at 00:50 -0700, Adam Williamson wrote: > The monologue continues =) > > It's not actually that simple. Following the previous mail, it stopped > working again. > > So now it seems like it stops working after either some time passes or > <something> happens. It then will not work again - despite resets or > reloading of the module - until I do a cold boot (I've also been > removing the power cord for 30 seconds, not sure if that's required, I > should test). Until I do this, whenever I load the lirc_i2c module (no > matter what kernel or exactly what version of lirc I'm using) it loads > but does not detect the hardware. > > I am now testing whether this happens with the older version of the > lirc_i2c module in our 2.6.17 kernel. If it doesn't, then it would seem > to be a problem introduced recently in lirc. If it does, then the > problem lies elsewhere. Will report with more details tomorrow. Yep, indeedy: I left the system up overnight running the 2.6.17 with its old included lirc_i2c, and it's still working right now. I am going to run the tests a couple more times, but it seems that right now the status is this: current CVS lirc_i2c does something nasty to the hardware after being up for a while (around a half hour to an hour, it seems). It stops working and is then unusable until a cold boot (possibly requiring PSU disconnect) is performed, no matter what kernel and what version of lirc_i2c you try. As soon as a cold boot is performed, any version of lirc_i2c can get at the hardware again. The older lirc_i2c in our 2.6.17 kernel does not do this. I don't think 0.8.2 did, either. Can anyone of any changes in lirc that might have this effect? It's quite nasty. -- adamw |
From: <li...@ba...> - 2007-08-31 06:48:00
|
Hi! Adam Williamson "awi...@ma..." wrote: [...] > current CVS lirc_i2c does something nasty to the hardware after being up > for a while (around a half hour to an hour, it seems). It stops working [...] > Can anyone of any changes in lirc that might have this effect? It's > quite nasty. I don't think any of the changes in CVS can have this effect. It's much more likely that the I2C code has some changes which will cause this. I suggest that you ask the I2C developers. Christoph |
From: Adam W. <awi...@ma...> - 2007-08-31 09:18:52
|
On Fri, 2007-08-31 at 08:04 +0200, Christoph Bartelmus wrote: > Hi! > > Adam Williamson "awi...@ma..." wrote: > [...] > > current CVS lirc_i2c does something nasty to the hardware after being up > > for a while (around a half hour to an hour, it seems). It stops working > [...] > > Can anyone of any changes in lirc that might have this effect? It's > > quite nasty. > > I don't think any of the changes in CVS can have this effect. It's much > more likely that the I2C code has some changes which will cause this. > I suggest that you ask the I2C developers. Ah, good point. I shall. Thanks. -- adamw |