[mythtv-users] MCE remote & LIRC on Debian Etch

Jake jakeisawake at gmail.com
Thu Jan 22 07:31:25 UTC 2009


> where I can make the remote work using 'automagic' tools, I have a file
> named "/dev/lirc0" that seems to 'be' the remote as far as the system is
> concerned, but this is not the case on the Debian machine I am working with
> (if I do a "ls /dev/l*" I get "lircd" "lircm" and a bunch of "loop*"
> listings, and other unrelated items).

so you don't have /dev/lirc0 probably because the module isn't loaded.
 you can always check if a module is loaded by doing lsmod | grep
name_of_module so in this case lsmod | grep lirc* and see what is
loaded.

>
> Where you ask if the "module is loaded," I have to assume the answer is no,
> but I was hoping to learn how to make that determination more certainly.
>

to load a module just do modprobe name_of_module so assuming you've
built lirc_mceusb2 you'd modprobe lirc_mceusb2.  if that loads
sucessfully it should create /dev/lirc0 so check to make sure it
exists now using your ls from before.

> when I try /usr/local/sbin/lircd -n --device=/dev/lirc0 as you suggest, I
> get:
>
> BedroomFE:/home/josh# /usr/local/sbin/lircd -n --device=/dev/lirc0
> bash: /usr/local/sbin/lircd: No such file or directory
> BedroomFE:/home/josh#
>

if the device exists this should work fine.

> so that's not much help.
>
>
> I do have a "lircd.conf" file in /etc/lirc/, and it contains the only
> uncommented lines:
>
>  remote:
> include /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb
>
> and the file it's pointing to does exist, and is populated with what looks
> like hexadecimal code which I assume describe buttons, etc.

that should be fine.

>
> Sorry if my response is less than inspiring, or leans toward annoying, but
> I'm just trying to work through this, and I'm simply asking the questions
> that come to mind.
>

np, everyone gotta learn at some point.


More information about the mythtv-users mailing list