Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I've been banging my head against lirc for some time now, and am
getting frustrated. Has anyone got lirc_i2c or the old lirc_haup to
work with RH7? Well, are the current versions functional for anyone?
=46rom reading the mailing list, it seems like Gerd Knorr's recent patch
would have fixed the problems with=20
Here is what I have:
- Red Hat Linux 7
- self-compiled kernel 2.2.17 with i2c-2.5.2 patched in
- newest lirc CVS version of today
Now, here is what I do (configuration files already set):
$ cvs checkout lirc
$ ./autogen.sh && ./configure
$ make && make install
$ modprobe lirc_i2c
Before all that I have removed obsolete lirc modules from /lib/modules
and double-checked that nothing lirc-specific is currently loaded. Now
everything works fine until irw. When I run it, lircd dies silently,
causing irw to exit. Actually, any program connecting to lirc socket
seems to make lircd die.
Now, the strange thing, suggesting this might be a RH7 problem, is
that when I fetched some older versions of lirc from the CVS and tried
them, I faced the same problem with versions that (if I remember
correctly) worked flawlessly!
What might be going wrong here?
+358 50 34 64 256
Matti Airas "mairas@..." wrote:
> everything works fine until irw. When I run it, lircd dies silently,
> causing irw to exit. Actually, any program connecting to lirc socket
> seems to make lircd die.
Check /var/log/lircd and /var/log/messages for debug messages.
On Thu, 19 Oct 2000, Christoph Bartelmus wrote:
> Matti Airas "mairas@..." wrote:
> > everything works fine until irw. When I run it, lircd dies silently,
> > causing irw to exit. Actually, any program connecting to lirc socket
> > seems to make lircd die.
> Check /var/log/lircd and /var/log/messages for debug messages.
Oh, I actually didn't notice /var/log/lircd. Since lircd startup
notification was injected to /var/log/messages, I thought the rest of
the messages would end up there as well...
Here goes /var/log/lircd:
Oct 20 07:42:05 huuli.mairas.net lircd-0.6.3: lircd ready
Oct 20 07:42:06 huuli.mairas.net lircd-0.6.3: could not open lirc
Oct 20 07:42:06 huuli.mairas.net lircd-0.6.3: default_init(): No such device
Oct 20 07:42:06 huuli.mairas.net lircd-0.6.3: caught signal
The file is full of such entries. There are no suspicious entries in
/var/log/messages, and the lirc modules are loaded correctly. I might
take a look at the default_init() problem this weekend, it is the only
clue so far after all...
I'm still open for suggestions. :-)
+358 50 34 64 256