On Mon, 5 Apr 2010, Raymond Norton wrote: > It chooses /dev/lirc on its own when I issue those commands. I created a > symlink, but received other errors (can't recall what they were now). /dev/lircd is usually a symlink itself (to /var/run/lirc/lircd), which technically isn't really a device file. You might want to try mode2 --device /dev/lircd and see if that works. The only file I actually modified is /etc/lirc/lircd.conf, where I told it to load my custom remote file (which I created with irrecord). You might want to check /etc/lirc/hardware.conf and make sure that's pointing to the correct hardware driver, too, and make sure lircd is running with the correct driver. > What specific steps got it working for you? > > > > Yaron wrote: >> On Mon, 5 Apr 2010, Raymond Norton wrote: >> >>> For my initial setup I am using a commandIR receiver (commandir.com), >>> and a sanyo RB-SL22 remote. I was getting "missing /dev/lirc" errors >> >> Try telling it to use /dev/lircd instead of /dev/lirc. That was basically >> the biggest deal I had, other than telling it which remote file to use. >> >> >> -Yaron >> >> -- >> >> _______________________________________________ >> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >> tclug-list at mn-linux.org >> http://mailman.mn-linux.org/mailman/listinfo/tclug-list >> > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > -Yaron --