Hello Pauls, pauls [2009-03-05 0:15 -0000]: > Yes, I had inserted this same line in intrepid /etc/modprobe.d/wl and it > was working for me there, so it's definitely a change in jaunty.
OK, marked as jaunty regression. > I'm confused by the output of "lshw -C network" which shows this for the > ethernet: > > product: BCM4401-B0 100Base-TX > bus info: p...@0000:03:00.0 > configuration: broadcast=yes driver=b44 driverversion=2.0 > ip=65.191.200.226 latency=64 module=ssb multicast=yes That driver/module is indeed confusing. But then again I don't know lshw at all. > Isnt' the ssb module the reason that the STA "wl" module won't ever get > called? Presumably, yes. Either ssb, or b43. > Apparently, the "blacklist ssb" statement isn't working (more > below). Do we need some blacklist statement for "b43-pci-bridge" > (whatever that is, since it's no a module in /lib/modules/). No, that'll only work for modules. But maybe you can give me the output of "lsmod" (lsmod > /tmp/modules.txt and attach that file here). Maybe there's yet another one by now. > Here's the contents of /etc/modules OK, nothing here. > After rebooting there is no modprobe.log. Interesting. So it seems that yet another module is pulling in any of those as a dependency. Maybe the lsmod output will tell me which. If not, we have to use some stronger weapons, like replacing /sbin/modprobe with a shell wrapper which logs loaded modules and $PPID to a file. I'll get to that later. -- jockey fails to enable broadcom STA driver https://bugs.launchpad.net/bugs/333903 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
