This bug is old.
The loast release (0.9.4c - zesty) deals with this. Actually the default
configuration (--driver devinput --device auto) should cover the
devinput case. Here is also new documentation on how to setup the
default driver (also available at http://lirc.org/html/configuration-
guide.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lirc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787735
Title:
Snapst
On Tue, Jun 7, 2011 at 8:43 AM, Jarod Wilson wrote:
> On Jun 7, 2011, at 12:31 AM, Dan Christian wrote:
>
>> Ya, but that's not something an ordinary user knows how to figure out.
>> I couldn't find any docs on how to setup devinput, what it is, or
>> when to use it.
>
> http://lirc.org/html/devin
On Jun 7, 2011, at 12:31 AM, Dan Christian wrote:
> Ya, but that's not something an ordinary user knows how to figure out.
> I couldn't find any docs on how to setup devinput, what it is, or
> when to use it.
http://lirc.org/html/devinput.html
> It's not at all clear from the documentation how
Ya, but that's not something an ordinary user knows how to figure out.
I couldn't find any docs on how to setup devinput, what it is, or
when to use it.
It's not at all clear from the documentation how to find and debug
each of these steps:
Which driver (the docs say the atilibusb driver is right
I'm still quite sure ati_remote + lircd's devinput driver works just
fine for the firefly hardware when you're talking to the right event
device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787735
T
Nope. Nothing worked for me. The one thing I didn't try was building
lirc 0.9.0 from source (Ubuntu shipps 0.8.7).
I bought a media center edition remote:
http://www.newegg.com/Product/Product.aspx?Item=N82E16880121003&Tpk=80-121-003
There is a bug with it doubling every button press, but the so
@Dan Christian - did you ever get it working?
I'm in the same boat except I can tell from your posts that you are a few
grades above me in your linux knowledge. I can follow what you did, but I
wouldn't know the commands on my own without someone showing me like you have
in your posts.
I did a
ati_remote apparently doesn't have everything in the driver properly
wired up for udev to create the persistent symlink in by-id/, so you'll
have to use some other means of discovery. You can point straight to a
/dev/input/eventX device, or by name or phys, per
http://lirc.org/html/devinput.html.
I think you are saying that REMOTE_DEVICE should be set to one of these:
$ ls /dev/input/by-id/usb-Logitech_USB_Receiver-*
/dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd@
/dev/input/by-id/usb-Logitech_USB_Receiver-event-mouse@
/dev/input/by-id/usb-Logitech_USB_Receiver-if01-event-mouse@
/dev/
You need to fill in REMOTE_DEVICE, per my prior comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787735
Title:
Snapstream Firefly non-functional
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
Still not working. Here is what I did:
rm /etc/modprobe.d/lirc-blacklist
modprobe ati-remote
$ lsmod | grep ati
ati_remote 13942 0
pata_atiixp13165 0
Here is what dmesg says when ati-remote is loaded:
[ 3893.666788] usbcore: registered new interface driver ati_remote
Okay, dmesg looks much better. I'm assuming some "helpful" Ubuntu lirc
package bit is adding that blacklist file. Remove it. Let ati_remote
load. Instruct lircd to use the 'devinput' driver, with device
'/dev/input/by-id/', and the lircd.conf.devinput config
provided by lirc. Dunno how or if that's
I didn't create /etc/modprobe.d/lirc-blacklist, some package did (I had
assumed it was lirc, but I can't find it in the package manifest and I'm
not sure how to search for what package owns what file).
I'm not sure what you're saying about ati_remote. The lirc
configuration has been noting but co
Also, from dmesg:
[ 31.654252] lirc_dev: IR Remote Control driver registered, major 61
[ 31.654621] ir_lirc_codec: Unknown symbol lirc_dev_fop_poll (err 0)
[ 31.655146] ir_lirc_codec: Unknown symbol lirc_dev_fop_open (err 0)
[ 31.655242] ir_lirc_codec: disagrees about version of symbol li
Ah, so you've blacklisted ati_remote, ok, that makes more sense then.
But why do that? Let ati_remote load, and then use lircd's devinput
mode. (Not that atilibusb shouldn't work too).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
$ lsusb
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 046d:c505 Logite
lsusb and dmesg output after a clean boot please. My suspicion: the in-
kernel ati_remote driver is already bound to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787735
Title:
Snapstream Firefl
** Attachment added: "hardware.conf as determined by mythbuntu control center"
https://bugs.launchpad.net/bugs/787735/+attachment/2141291/+files/hardware.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
19 matches
Mail list logo
