Pietro sent me mail, but for the purpose of record keeping it's better to put my response here, too:
Pietro Battiston [2009-02-14 10:53 -0000]: > I would volunteer to write a jockey handler (based on an existing list > of supported laptops) for that, but I'd like to know if you think it's a > little overkill to use jockey for something: > - free > - with no particular conflicts with anything Is that true? The description of the bug says you need to rmmod b43. Maybe that was true for intrepid, but not for the Jaunty kernel any more? > - that is simply a workaround, waiting for a proper fix (from the > kernel) If those three reasons are true, a jockey handler sounds like the wrong solution to me (as much as I like jockey :-) ). But if a driver which we ship by default does not get activated by default, then that's simply a bug, and not something the user should need to worry about. In other words, jockey should allow you to do a qualified decision, but shouldn't be a place with lots of "unbreak my computer" buttons. Besides, it wouldn't really help with the problem in the first place. Just as the kernel, jockey needs to detect the hardware and match it to a driver. For kernel modules, the main tool is modalias matching (which seems to fail for acer-wmi). Now, jockey handlers can do arbitrary other things to detect availability (e. g. sl-modem parses output of "aplay -l"), but I expect for that kernel module we just need to fix the modaliases to match on more DMI strings? Or what else needs to happen? IMHO those workarounds should be put into a modprobe.d/ script. See /etc/modprobe.d/isapnp for an existing example how to provide additional modaliases for a kernel module. -- acer_wmi is not used by default (on Fujitsu Siemens Amilo A1650G) https://bugs.launchpad.net/bugs/248635 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
