ATi Remote Wonder in Linux? - Tilted Forum Project Discussion Community

skaven · 11-13-2005, 09:54 PM

I recently got an ATi TV Wonder card w/remote for use in a MythTV box I'm building up. The tuner card works great, and from what I've read on the internet, the TV wonder is supposed to "just work"... it's supposed to show up as a HID in newer 2.6 kernels and thus mimic a mouse and keyboard.

Unfortunately I'm getting nothing at all from my Remote Wonder. Nada.

I've tried plugging in mutliple USB mice and keyboards and my system has no trouble accepting input from multiple ones at the same time, so I don't believe that's the problem.

dmesg shows that the ati_remote module loads up and initializes properly when I plug in the RF receiver.

However, I get nothing at all from the remote.

As other people on the internet have had seemingly zero trouble at all getting their Remote Wonders to work, I'm curious whether I've got a bum transmitter, or if I'm just doing something wrong with the configuration. I'd rather not have to install windows on the box just to verify that my hardware actually works...

Anybody else gotten one of these to work before in Linux?

ratbastid · 11-14-2005, 05:43 AM

I don't know anything about this particular piece of hardware, but I know a litle about device drivers, and I can speculate as well as anybody.

If dmesg tells you it sees the IR receiver, that's a good sign that everything's set up right about the card itself. You might check the batteries in the remote? Because it does sound like an issue somewhere between the remote and the receiver.

I have a universal "learning" remote that reads other remote's IR patterns so it can pretend to be that remote. I've used that to test remotes before--if my u-remote can read them, I know that's not where my problem is. Maybe you could find one of those?

skaven · 11-14-2005, 09:47 PM

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.

cyrnel · 11-14-2005, 10:36 PM

Have you tried checking for input with evtest? My myth box has been down for a bit or I'd be more help.

skaven · 11-15-2005, 04:41 PM

I checked with xev and it isn't capturing anything...does evtest dig deeper than xev?

cyrnel · 11-15-2005, 04:56 PM

Yes. xev is sort of a superset X version of showkey. evtest watches the specific device. If you get something with evtest you know the hardware is okay. If not, it probably isn't or the driver isn't playing nicely.

skaven · 11-15-2005, 06:33 PM

Well I managed to locate evtest (its in the lineakd package), and lo and behold...looks like the receiver is working quite nicely, but not receiving a single thing the transmitter is sending.

While I'm happy to have a new debugging tool...I'm disappointed that this most likely means that my remote is busted...

cyrnel · 11-15-2005, 07:05 PM

Sorry, it's been awhile since I last debugged these things. I was thinking it arrived with 2.6.5 & the gang. Must get my box back in shape...

You tried a hammer already?

11-13-2005, 09:54 PM	#1 (permalink)
skaven Insane Location: Austin, TX	ATi Remote Wonder in Linux? I recently got an ATi TV Wonder card w/remote for use in a MythTV box I'm building up. The tuner card works great, and from what I've read on the internet, the TV wonder is supposed to "just work"... it's supposed to show up as a HID in newer 2.6 kernels and thus mimic a mouse and keyboard. Unfortunately I'm getting nothing at all from my Remote Wonder. Nada. I've tried plugging in mutliple USB mice and keyboards and my system has no trouble accepting input from multiple ones at the same time, so I don't believe that's the problem. dmesg shows that the ati_remote module loads up and initializes properly when I plug in the RF receiver. However, I get nothing at all from the remote. As other people on the internet have had seemingly zero trouble at all getting their Remote Wonders to work, I'm curious whether I've got a bum transmitter, or if I'm just doing something wrong with the configuration. I'd rather not have to install windows on the box just to verify that my hardware actually works... Anybody else gotten one of these to work before in Linux?

11-14-2005, 09:47 PM	#3 (permalink)
skaven Insane Location: Austin, TX	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.

11-14-2005, 10:36 PM	#4 (permalink)
cyrnel Adequate Location: In my angry-dome.	Have you tried checking for input with evtest? My myth box has been down for a bit or I'd be more help. __________________ There are a vast number of people who are uninformed and heavily propagandized, but fundamentally decent. The propaganda that inundates them is effective when unchallenged, but much of it goes only skin deep. If they can be brought to raise questions and apply their decent instincts and basic intelligence, many people quickly escape the confines of the doctrinal system and are willing to do something to help others who are really suffering and oppressed." -Manufacturing Consent: Noam Chomsky and the Media, p. 195

11-15-2005, 04:56 PM	#6 (permalink)
cyrnel Adequate Location: In my angry-dome.	Yes. xev is sort of a superset X version of showkey. evtest watches the specific device. If you get something with evtest you know the hardware is okay. If not, it probably isn't or the driver isn't playing nicely. __________________ There are a vast number of people who are uninformed and heavily propagandized, but fundamentally decent. The propaganda that inundates them is effective when unchallenged, but much of it goes only skin deep. If they can be brought to raise questions and apply their decent instincts and basic intelligence, many people quickly escape the confines of the doctrinal system and are willing to do something to help others who are really suffering and oppressed." -Manufacturing Consent: Noam Chomsky and the Media, p. 195

11-15-2005, 07:05 PM	#8 (permalink)
cyrnel Adequate Location: In my angry-dome.	Sorry, it's been awhile since I last debugged these things. I was thinking it arrived with 2.6.5 & the gang. Must get my box back in shape... You tried a hammer already? __________________ There are a vast number of people who are uninformed and heavily propagandized, but fundamentally decent. The propaganda that inundates them is effective when unchallenged, but much of it goes only skin deep. If they can be brought to raise questions and apply their decent instincts and basic intelligence, many people quickly escape the confines of the doctrinal system and are willing to do something to help others who are really suffering and oppressed." -Manufacturing Consent: Noam Chomsky and the Media, p. 195

11-14-2005, 05:43 AM	#2 (permalink)
ratbastid Darth Papa Location: Yonder	I don't know anything about this particular piece of hardware, but I know a litle about device drivers, and I can speculate as well as anybody. If dmesg tells you it sees the IR receiver, that's a good sign that everything's set up right about the card itself. You might check the batteries in the remote? Because it does sound like an issue somewhere between the remote and the receiver. I have a universal "learning" remote that reads other remote's IR patterns so it can pretend to be that remote. I've used that to test remotes before--if my u-remote can read them, I know that's not where my problem is. Maybe you could find one of those?

11-15-2005, 04:41 PM	#5 (permalink)
skaven Insane Location: Austin, TX	I checked with xev and it isn't capturing anything...does evtest dig deeper than xev?

11-15-2005, 06:33 PM	#7 (permalink)
skaven Insane Location: Austin, TX	Well I managed to locate evtest (its in the lineakd package), and lo and behold...looks like the receiver is working quite nicely, but not receiving a single thing the transmitter is sending. While I'm happy to have a new debugging tool...I'm disappointed that this most likely means that my remote is busted...