Jockey has done the right thing (unbind/bind) for a long time now, and
nobody else complained about this.
** Changed in: module-init-tools (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
Status: New => Won't Fix
--
test availability of firmware for bcm43xx
https://bugs.launchp
Scott just told me the secret runes to unbind/bind the module to reload
the firmware, so this is not really necessary any more. We could still
do it for reducing confusion for people who look at lsmod and wonder why
it doesn't work, though.
** Changed in: module-init-tools (Ubuntu)
Importance:
** Attachment added: "module-check-firmware"
http://launchpadlibrarian.net/8149692/module-check-firmware
--
test availability of firmware for bcm43xx
https://bugs.launchpad.net/bugs/121504
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
This is the install script.
** Attachment added: "/sbin/module-check-firmware"
http://launchpadlibrarian.net/8149678/module-check-firmware
** Attachment removed: "/sbin/module-check-firmware"
http://launchpadlibrarian.net/8149678/module-check-firmware
--
test availability of firmware for
This is /etc/modprobe.d/bcm43xx. To keep it a little more generic we
should probably call this /etc/modprobe.d/needs_firmware.
** Attachment added: "modprobe.d script"
http://launchpadlibrarian.net/8149669/bcm43xx
--
test availability of firmware for bcm43xx
https://bugs.launchpad.net/bugs/12
