Actually I think there's a wider issue here - modprobe failing due to unsupported module options provided by configuration, kernel or modprobe command-lines.
I can envisage other scenarios where a change in the kernel build configuration removes the availability of a module parameter and causes other modules to fail to load. It's trivial for modprobe to check the options against what the module supports and instead of failing, simply warn about the unsupported option but continue to load the module without the unsupported option. Attaching a debdiff for module-init-tools to achieve this. ** Attachment added: "debdiff: wanr don't fail on unsupported module parameters" http://launchpadlibrarian.net/24134396/module-init-tools_3.7%7Epre9-3.debdiff ** Also affects: module-init-tools (Ubuntu) Importance: Undecided Status: New -- Wifi driver will fail to load if regulatory domain set in module options https://bugs.launchpad.net/bugs/343026 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
