ati_remote2: doesn't seem to work well

[coffee]

I have installed an ATI Remote Wonder 2.
lsusb sees it: Bus 003 Device 003: ID 0471:0602 Philips
dmesg indicates me some things:
[4295642.664000] usb 3-2: new full speed USB device using ohci_hcd and address 3
[4295642.803000] input: ATI Remote Wonder II as /class/input/input4
If I press a button on the remote, dmesg give me something like this:
[4295669.212000] ati_remote2 3-2:1.1: Unknown mode byte (00 3f 02 73)

I tried to launch xev to get a reply from the remote (as it is said for the ati_remote module) and it reply nothing.

[Michael R. Head (burner)]

I've found that I have to press a button on the remote, then unplug and replug it to get it to function properly.

[Michael R. Head (burner)]

BTW: when it works, it just acts like a keyboard and mouse in X. I don't need to run any extra programs.

[Gaëtan Petit (gaetanp)]

i have the same device here and no problem

[evuraan (evuraan)]

I've the same issue (at times) in Ubuntu gutsy - manual disconnect and then a reconnect resolves it.

But thats not how a "remote" should work, right? Or might as well use a long stick from the couch to press the buttons, while worrying about the $ 30.00+ I blew on this remote.

$ uname -a
Linux anudell 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 7.10
Release: 7.10
Codename: gutsy

[evuraan (evuraan)]

As a work around, I've modified my /etc/rc.local like this:

( cd /sys/bus/usb/drivers/ati_remote2; ls |grep -vi [a-z]|sort| head -1 > /tmp/ati.id ) &
[ -s "/tmp/ati.id" ] && {
ati="`cat /tmp/ati.id`"
echo -n "$ati" > /sys/bus/usb/drivers/ati_remote2/unbind
echo -n "$ati" > /sys/bus/usb/drivers/ati_remote2/bind
}

What it does is, unbinds and then binds the remote every time the OS boots up, eliminating a physical disconnect. and then a reconnect.

 During the 10 consecutive reboots I've tested with this mod in, the remote has worked OK for me.

Hopefully that continues to be the case, if not, I'll report here.

[evuraan (evuraan)]

:(

 That does not work.

So we're back where we started, this remote needs to be physically unplugged and replugged to get it to function properly.

[seisen1 (seisen-deactivatedaccount-deactivatedaccount)]

Can you please test this in the latest version of Ubuntu, Hardy Heron, to see if its still a problem?

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 37359