Thanks peebee, but if what wuxiandianzi says is true I think we are a step closer. Actually /lib/modules/all-firmware/b43/lib/firmware is empty!!! (WRONG sorry, it's in /lib/firmware/b43),rerwin wrote:One thing I saw in reviewing the drivers thread is a conflict between b43 and ssb, which I am proposing to handle with a new preference, "ssb:b43". Since I cannot see what is happening in the cases you cite, I don't know whether that preference is related or not. Another issue in that thread suggests a timing factor, in that the troubleshooting advice was to unload and reload b43 a little later in the initialization sequence -- not sure whether that is still considered effective.
We might make more sense of it all with a little data to work from. Could you obtain from both the lupu variant and your failing puppy the files, /tmp/udevtrace.log, /var/log/messages and /lib/modules/.../modules.alias? And also the hardware ID of the device in question and the output from lsmod.
Before even doing that, could you tell me more about what is happening with the broadcom driver? Does b43 simply get ignored, or is another module loaded in its place? I am trying to determine whether it would be something for tempestuous to examine or for Barry.
wuxiandianzi, all firmware is decompressed. No need of compression as the xz compression of the main sfs takes care of it. This was introduced in woof about 3 months ago.
-
maxerro, answer is me.