| Summary: | app-misc/lirc-0.8.6-r2: either einfo is wrong or lirc | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Television related Applications in Gentoo's Portage <media-tv> |
| Status: | RESOLVED INVALID | ||
| Severity: | trivial | Keywords: | PMASKED |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Toralf Förster
2010-04-06 15:34:35 UTC
/dev/lircd is no device, but the socket over which lircd communicates with its clients. lircd itself does default to opening /dev/lirc0 (if not used with userspace drivers not needing a device node). How do you use lirc? Maybe you need to load the correct driver. I'm using this : n22 /etc/lirc # grep ^LIRCD_OPTS /etc/conf.d/lircd LIRCD_OPTS="-H devinput -d /dev/input/by-path/pci-0000:00:1a.7-event-ir" and it remote control is recognized, although no key code is known : 2010-04-08T11:56:24.000+02:00 n22 lircd-0.8.6[30523]: lircd(devinput) ready, using /var/run/lirc/lircd 2010-04-08T11:56:34.000+02:00 n22 lircd-0.8.6[30523]: accepted new client on /var/run/lirc/lircd 2010-04-08T11:56:34.000+02:00 n22 lircd-0.8.6[30523]: initializing '/dev/input/by-path/pci-0000:00:1a.7-event-ir' 2010-04-08T11:56:47.000+02:00 n22 lircd-0.8.6[30523]: accepted new client on /var/run/lirc/lircd 2010-04-08T11:57:13.333+02:00 n22 kernel: dib0700: Unknown remote controller key: 0014 1c e3 2010-04-08T11:57:13.738+02:00 n22 kernel: dib0700: Unknown remote controller key: 0014 1c e3 2010-04-08T11:57:15.647+02:00 n22 kernel: dib0700: Unknown remote controller key: 0014 1c e3 20 ... BTW it is a "Terratec Cinergy T USB XXS (HD)/ T3" stick, which has an in-build ir adapter: input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1a.7/usb7/7-1/input/input14 Udev would normally create a /dev/lirc0 for your device once the lirc module loads. The emerge doesn't have anything to do with the creation of /dev/lirc0 though. Also, you might be able to skip this due to your specification of the direct /dev/input/ device (dunno). Either way, the bug (as it was filed) is invalid and so I'm closing. I'm not sure if you are having issues with your setup or not, but if you are and you would like help with your configuration please don't hesitate to ask on #gentoo (irc) or in the forums. |