Well this is an RF remote -- no IR. And it's a USB receiver, not a PCI card. It's so frustrating, though, to see ati_remote listed quite clearly under /proc/bus/input
Code:
[skaven@shinji:/proc/bus/input]$ cat devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000078 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event1
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3
I: Bus=0003 Vendor=0bc7 Product=0004 Version=0100
N: Name="X10 Wireless Technology Inc USB Receiver"
P: Phys=usb-0000:00:02.1-2/input1
H: Handlers=kbd mouse1 event2
B: EV=7
B: KEY=108c0020 2000043 0 0 1b0000 0 8000 10180 91400811 9e1ec1 0 14003 40040ffc
B: REL=3
As you can see, the ATI controller is being recognized as mouse1 and kbd, with the PS/2 keyboard and mouse being regognized as mouse0 and kbd. The /dev/input/mice device node should be picking up on both the mouse interfaces, and naturally the kbd interface should be recognized as a keyboard.
Supremely frustrating, because there's no real way to debug this -- I mean, how do you debug whether the remote is transmitting a valid RF signal? How do you debug whether the receiver is even "hearing" anything?
I hate problems like this.