The signals are picked up by a tranceiver that's identified by
lsusb
asBus 005 Device 002: ID 0bc7:0006 X10 Wireless Technology, Inc. Wireless Transceiver (ACPI-compliant)
The important bit is the ID of 0bc7:0006, and it's this that lets google do most of the work.
First of all, it's misidentifed by the system, and the wrong module - ati-remote - is added. To get rid of this, we have to add a line (as root) to
/etc/modprobe.d/blacklist.conf
blacklist ati_remote
will ensure that the module isn't loaded.Once that's done, it's just a matter of specifying the right driver in
/etc/sysconfig/lirc
The line
LIRC_DRIVER=""
has to be changed to readLIRC_DRIVER="atilibusb"
Again, you have to be root to do this.
Then it's just a matter of starting lirc and you're away;
/etc/rc.d/init.d/lirc restart
will do this.
As for the remote, it's just a matter of getting the right config file. This can be done tediously over many hours with
irrecord
or, if you prefer, you can just use mine.I didn't make this myself; I found many moons ago on a German Ubuntu forum, so many thanks to the anonymous nerd who put it together. It's at http://pastebin.com/8NJV80Lu.
Put this (as root again) into
/etc/lirc/lircd.conf
and you're ready to go.
No comments:
Post a Comment