| Summary: | app-misc/lirc-0.8.2: missing device nodes | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Peter Bienstman (RETIRED) <pbienst> |
| Component: | Current packages | Assignee: | Television related Applications in Gentoo's Portage <media-tv> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | jesse, neil, Peter.Bienstman |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Peter Bienstman (RETIRED)
2007-08-15 17:59:26 UTC
lircd creates that node. lircd is not running on your machine. Closing as INVALID, as this is a configuration and no lirc bug. If your hardware does not need a special lirc-driver/kernel-module (as you write) you will never get a /dev/lirc/0. Just look at lirc readme/documentation and change /etc/conf.d/lirc accordingly. Reading your two messages, I am now confused whether I need /dev/lirc/0 or not. Anyhow, if I try this in /etc/conf.d/lircd LIRCD_OPTS="-d /dev/lircd " I get pbienst portage # /etc/init.d/lircd restart * Caching service dependencies ... [ ok ] * Starting lircd ... lircd: refusing to connect to myself lircd: device and output must not be the same file: /dev/lircd Now with LIRCD_OPTS="-d /dev/lirc/0 ": /etc/init.d/lircd restart * Caching service dependencies ... [ ok ] * Starting lircd ... [ ok ] Now following the manual at lirc.org: pbienst portage # chmod 666 /dev/lircd pbienst portage # mode2 mode2: error opening /dev/lirc/0 mode2: No such file or directory I also want to stress that this worked before the upgrade, and that I am not the only one to have this problem, although in my case downgrading to 0.8.1 did not work: http://forums.gentoo.org/viewtopic-t-551953-highlight-.html Something strange I did notice, is that although the /etc/init.d/lircd restart came up ok, there was no lircd process running afterwards. Thanks for looking into this! (In reply to comment #3) > Reading your two messages, I am now confused whether I need /dev/lirc/0 or not. > > Anyhow, if I try this in /etc/conf.d/lircd > > LIRCD_OPTS="-d /dev/lircd " > > I get > > pbienst portage # /etc/init.d/lircd restart > * Caching service dependencies ... [ ok > ] > * Starting lircd ... > lircd: refusing to connect to myself > lircd: device and output must not be the same file: /dev/lircd > Well, telling you that 1. /dev/lircd is used for connection between lircd and user-programs. > Now with LIRCD_OPTS="-d /dev/lirc/0 ": > 2. you dont get /dev/lirc/0 if you dont use a lirc-kernel-module. Maybe you should try it without any options in LIRCD_OPTS. As pctv uses a serial port in normal mode you could try -d /dev/ttySX with X being 0-3. > > Now with LIRCD_OPTS="-d /dev/lirc/0 ": > > 2. you dont get /dev/lirc/0 if you dont use a lirc-kernel-module. Then why does e.g. mode2 keep trying to access /dev/lirc/0? pbienst portage # mode2 mode2: error opening /dev/lirc/0 mode2: No such file or directory > Maybe you should try it without any options in LIRCD_OPTS. > As pctv uses a serial port in normal mode you could try -d /dev/ttySX with > X being 0-3. Tried these 5 options, no success... Also went through dmesg, and this is the only strange thing I could find: spurious 8259A interrupt: IRQ7. Comprehension: Loading a lirc-driver kernel module does create /dev/lirc0 or /dev/lirc/0 depending on udev-version/lirc-ebuild-version. mode2 will open the correct one most of the time automatically, as lircd will do. So normally you should not need to specify -d /dev/lirc/0. lircd then opens this device, and creates the socket /dev/lircd to which the applications connect - so "-d /dev/lircd" is wrong in every case! You should look out for a description of your ir-receiver hardware as we cannot know how to configure it. The only thing I can add is that the very same configuration for my PCTV remote worked before I upgraded. So, at first sight, this looks more like a bug than a configuration issue... 0.8.2-r2 do not work properly with /etc/make.conf: LIRC_DEVICES="pctv" /etc/conf.d/lircd: LIRCD_OPTS="--driver=pinsys --device=/dev/ttyS1" 0.8.1 work properly Please add more info what exactly fails. Else we can just ask our local oracle. (In reply to comment #9) > Please add more info what exactly fails. > Else we can just ask our local oracle. I assume this comment is directed to 'gtlinuxman'. I hope you find my original bug report detailed enough :-) Please remove the 'RESOLVED NEEDINFO' status. Peter (In reply to comment #10) > (In reply to comment #9) > > Please add more info what exactly fails. > > Else we can just ask our local oracle. > > I assume this comment is directed to 'gtlinuxman'. I hope you find my original > bug report detailed enough :-) > > Please remove the 'RESOLVED NEEDINFO' status. > Ok, but still missing infos :/ So this is what lirc is supposed to do: 1. Reading info from some source (like /dev/ttyS* /dev/lirc/0 /dev/lirc0 or /dev/usb*) 2. Decoding it in some way. 3. Providing that info to applications via /dev/lircd or some tcp socket. So you see /dev/lircd has nothing todo with reading from hardware. And if you have no lirc kernel module you dont need LIRCD_OPTS="-d /dev/lirc/0". So delete this and tell me where it fails. Depending on the remote you may have to supply lirc with some /dev/input/* device. Maybe something like /dev/input/by-path/pci-0000:00:0a.0--event-ir. I uncommented everything in /etc/confd/lircd and then restarted the daemon. It starts fine and the process runs in the background. This is now with 0.8.3-pre1 and 2.6.23-gentoo-r9. However, mode2 still does not work: >chmod 666 /dev/lircd >mode2 mode2: error opening /dev/lirc/0 mode2: No such file or directory More info: >ls /dev/input/by-path/ pci-0000:00:1d.1-usb-0:2:1.0-event-kbd platform-i8042-serio-1-mouse pci-0000:00:1d.1-usb-0:2:1.1-event- platform-pcspkr-event-spkr platform-i8042-serio-1-event-mouse dmesg |grep -i lirc comes up empty (In reply to comment #12) > I uncommented everything in /etc/confd/lircd and then restarted the daemon.It > starts fine and the process runs in the background. This is now with 0.8.3-pre1 > and 2.6.23-gentoo-r9. Why do you uncomment settings you don't understand? Just comment all or add settings you know of. > > However, mode2 still does not work: > > >chmod 666 /dev/lircd > >mode2 > mode2: error opening /dev/lirc/0 > mode2: No such file or directory You cannot use mode2 when you dont use a lirc kernel driver!! And you don't need to. > > More info: > > >ls /dev/input/by-path/ > pci-0000:00:1d.1-usb-0:2:1.0-event-kbd platform-i8042-serio-1-mouse > pci-0000:00:1d.1-usb-0:2:1.1-event- platform-pcspkr-event-spkr > platform-i8042-serio-1-event-mouse > Depends if your pctv hardware uses the linux input-layer or ttyS* port. And maybe on your udev version. > dmesg |grep -i lirc comes up empty > See above - you dont use a lirc kernel driver: So why should the string lirc appear in the kernel log. status? |