[Gutsy] Ati_remote module isn't working

Same her (gutsy). I have to run manually
rmmod lirc_dev
rmmod lirc_atiusb
to get it working

I guess you (I don't know ubuntu internals) need to change udev rules.

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

In Hardy, ati remote works out of the box.

I am having similar issues in hardy.

I have only lirc_atiusb loaded (ati_remote is blacklisted) and irw just hangs without receiving any button presses. I tried to run lircd manually "lircd -n --device=/dev/lirc0" and connect with irw but no luck. lircd outputs "accepted new client on /dev/lircd" when irw is ran but no output on irw.

Any ideas?

Works in hardy... I had the wrong /etc/lircd.conf

irw works for me, with lirc_atiusb and lirc_dev loaded (ati_remote blacklisted).

However, mythtv does not work even with a ~/mythtv/lircrc and ~/.lircrc for my mythtv user. These files worked on 7.10.

I have an ATI Wonder Remote.

I'm using Hardy (Latest Alpha/Updates).

I have to manually ln -s /dev/lirc0 /dev/lirc for lircd to run.

lircd -n shows (when mythtv is starting)
lircd-0.8.3pre1[6686]: accepted new client on /dev/lircd

However, pushing buttons does not work. My lircrc file is attached.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

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.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]