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
i have the same device here and no problem
--
ati_remote2: doesn't seem to work well
https://launchpad.net/bugs/37359
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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 a
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
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/a
:(
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.
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubun
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Confirmed
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubunt
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscrib
Can you please test this in the latest version of Ubuntu, Hardy Heron,
to see if its still a problem?
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubun
Can you please test this in the latest version of Ubuntu, Hardy Heron,
to see if its still a problem?
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubun
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 a
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
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/a
:(
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.
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubun
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Confirmed
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubunt
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscrib
i have the same device here and no problem
--
ati_remote2: doesn't seem to work well
https://launchpad.net/bugs/37359
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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
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
Can you please test this in the latest version of Ubuntu, Hardy Heron,
to see if its still a problem?
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubun
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 a
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
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/a
:(
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.
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubun
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Confirmed
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubunt
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscrib
i have the same device here and no problem
--
ati_remote2: doesn't seem to work well
https://launchpad.net/bugs/37359
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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 a
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
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/a
:(
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.
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubun
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Confirmed
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubunt
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscrib
Can you please test this in the latest version of Ubuntu, Hardy Heron,
to see if its still a problem?
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubun
i have the same device here and no problem
--
ati_remote2: doesn't seem to work well
https://launchpad.net/bugs/37359
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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 a
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
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/a
:(
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.
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubun
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Confirmed
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubunt
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscrib
Can you please test this in the latest version of Ubuntu, Hardy Heron,
to see if its still a problem?
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubun
i have the same device here and no problem
--
ati_remote2: doesn't seem to work well
https://launchpad.net/bugs/37359
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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
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
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 a
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mail
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/a
:(
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.
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubun
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Confirmed
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubunt
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscrib
i have the same device here and no problem
--
ati_remote2: doesn't seem to work well
https://launchpad.net/bugs/37359
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Can you please test this in the latest version of Ubuntu, Hardy Heron,
to see if its still a problem?
--
ati_remote2: doesn't seem to work well
https://bugs.launchpad.net/bugs/37359
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubun
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
54 matches
Mail list logo
