When I merged lirc-0.7.0-r1 there was no /dev/lirc file, and for example irrecord complained about fault of /dev/lirc file. After doing: "mknod /dev/lirc u 61 0" everything works ok. I think that this can be fault of "--enable-sandboxed" option. As we can read at http://www.lirc.org/html/technical.html : "--enable-sandboxed Prevents any changes out of the installation directory on "make install": * will not create device nodes on /dev/ * will not run depmod" Reproducible: Always Steps to Reproduce: Expected Results: In my opinion ebuild should create /dev/lirc device file.
Was there a /dev/lircd/lirc0 ?
No there was no /dev/lircd/lirc0 or even /dev/lircd/ dir.
ok, after loading the correct module, there should be a /dev/lirc0 file, any chance?
ensima-gentoo root # lsmod|grep lirc ensima-gentoo lirc # ensima-gentoo root # ls /dev/lirc* ensima-gentoo lirc # ensima-gentoo root # irrecord test123 irrecord - application for recording IR-codes for usage with lirc Copyright (C) 1998,1999 Christoph Bartelmus(lirc@bartelmus.de) irrecord: could not init hardware (lircd running ? --> close it, check permissions) From /var/log/messages: Mar 6 20:34:36 ensima-gentoo irrecord: could not get file information for /dev/lirc Mar 6 20:34:36 ensima-gentoo irrecord: default_init(): No such file or directory Mar 6 20:35:31 ensima-gentoo irrecord: could not get file information for /dev/lirc Mar 6 20:35:31 ensima-gentoo irrecord: default_init(): No such file or directory ensima-gentoo root # modprobe lirc_serial ensima-gentoo root # lsmod|grep lirc lirc_serial 11488 0 lirc_dev 11596 1 lirc_serial ensima-gentoo root # irrecord test123 (got same errors in /var/log/messages as above) ensima-gentoo root # mknod /dev/lirc c 61 0 ensima-gentoo root # ensima-gentoo root # ls /dev/lirc* crw-r--r-- 1 root root 61, 0 mar 6 20:37 /dev/lirc Now irrecord works fine, I can test my remote, and it works (dots are appearing).
what kernel do you use?
gentoo 2.6.10-gentoo-r6
try a newer kernel and lirc-0.7.1
Is anything happening with this bug report? I emerged lirc this morning and see the same problem. The emerge seems to have created lircd but nothing else: myth12 ~ # ls -al /dev/lirc* srw-rw-rw- 1 root root 0 Jun 19 01:24 /dev/lircd myth12 ~ # therefore I cannot complete the installation of a remote in this state. I'm using 2.6.11-gentoo-r3 from the 2005.0 installation CD but rebuilt to handle the hardware in the system. I'm investigating if this is somehow a kernel config issue. I think I've followed the Gentoo Wiki on MthTV. This lircd stuff is on a frontend only machine where I'd like to use a streamzap remote control. Possibly this is just another udev issue? Thanks!
please try again, i added a udev patch
I can confirm that the udev rule works. Could you add this also to 0.7.0 and 0.7.1? I use this on a xbox, and 0.7.0 is the latest version working properly there. To make conf.d/lirc conform with the udev rules, please also have a look at: http://bugs.gentoo.org/show_bug.cgi?id=104677
(In reply to comment #10) > I can confirm that the udev rule works. Closing.
