Just installed this, and it broke my working lirc install.
I selected Linux input layer (/dev/input/eventX), and /etc/lirc/hardware.conf
was rewritten with DRIVER=.
It was DRIVER=dev/input before upgrading.
/usr/share/doc/lirc/lirc.hwdb contains:
Linux input layer
lirc (0.8.2-0ubuntu3) gutsy; urgency=low
* Add 14_lirc_i2c.dpatch to fix lirc-i2c on 2.6.22 kernel
for PVR-150 and HVR-1300. (LP: #128650)
* Add 15_macmini.dpatch to fix macmini support. (LP: #126955)
* Add 16_lirc-gpio.dpatch to fix GPIO by backporting deprecated
functions, until
On Sun, 2007-07-22 at 19:24 +, Oliver Gerlich wrote:
Brian: it seems that m-a is not so much immature as only badly integrated
in Ubuntu...
No, I disagree. I don't think it's any different than it is in Debian.
It's just the way the tool works. It's sub-optimal (if you don't want
to use
Brian: it seems that m-a is not so much immature as only badly integrated in
Ubuntu... Feature-wise you can run m-a a-i lirc and get working LIRC modules
installed (it asks a few times in the process for a y whether you want to
install kernel-headers and bla bla, and then automatically installs
I've added a much better solution to gutsy regarding kernel modules.
They are now part of the linux-ubuntu-modules package (and consequently
rebuilt automatically when the new kernels are rolled out)
See:
https://bugs.launchpad.net/ubuntu/+bug/121676 for including DKMS in
Ubuntu.
--
Installing Lirc support should be simpler
https://bugs.launchpad.net/bugs/65174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I don't think our immediate requirement is configuration guis and the
such. Our immediate requirement is a better-than-modules-assistant (i.e
not having to build and install from source) method of getting lirc
drivers. While I'm on the subject, why is m-a so immature? I mean
compared to DKMS
Just tell me when your ready. :) I would be happy to do it for Gutsy
+1.
--
Installing Lirc support should be simpler
https://bugs.launchpad.net/bugs/65174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I can create a gui for the device setup. I program in python. I also
have a generic IRC reader... one that is recommended by lirc project.
If you can tell me how to implement this device without having to
recompile from source, I would be more than happy to make a gui frontend
to do all that. :D
This bug will be addressed upstream by a sub project of the Ubuntu Media
Center Team.
https://wiki.ubuntu.com/RemoteControls
I have already started to discuss with Christoph Bartelmus (LIRC project
leader) and Jon Smirl, who has started some work.
Kernel hackers needed. If you're interested
I Agree.
It was a pain to build lirc-modules-source, because the misleading
documentation in README, README.Debian, and debconf.
But if the documentation were correct, it would be difficult for linux-newbies
to compile stuff, so a lirc-modules package for the current kernel is needed!
--
I'd say a good idea would be to make lirc-modules-source depend on
modules-assistant and to recommend Kees' instructions via a debconf
message window.
Currently, lirc-modules-source does not build the lirc modules for 2.6.x
correctly, and also places them into the wrong location, here on feisty
Adding a kernel-tracking lirc-modules package has been proposed to the kernel
team, and perhaps in future versions of Ubuntu, lirc will be included in the
kernel rebuild process. For the time being, using m-a should be used to
rebuild the modules as needed:
sudo m-a -v -t prepare
sudo m-a
I fully agree. I have spent several hours for the last four days trying
to get lirc working but to no avail. And the hardware is fine, as my
previous KnoppMyth installation had it working at first boot. I'm a nerd
and I can't get it running... so I'm pretty sure a newbie (or should I
say Human
** Summary changed:
- Installing Lirc support is a real pain in the ass
+ Installing Lirc support should be simpler
--
Installing Lirc support should be simpler
https://launchpad.net/bugs/65174
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Agreed. I think the inclusion of a lirc-modules package would go a long
way and would definitely be the first step.
For instance, see bug 53111, bug 47997, bug 44726, and numerous forum
threads for the headache that configuring the LIRC modules causes.
Also, udev rules for hotplugging would
16 matches
Mail list logo
