On Friday 14 December 2007 02:12:25 Ray Lee wrote: > Digging a little farther into it, it looks like b43 is barfing partway > through init as the firmware file it's looking for has changed names. > Perhaps that's the issue. I'll take a longer look at this all > tomorrow.
http://www.linuxwireless.org/en/users/Drivers/b43#firmwareinstallation > Well, it only hit the main kernel October 10th. That means no final > point release of the kernel.org kernel has even had it included! So > testing-wise, you still haven't hit the hordes yet. Scheduling a > removal of bcm43xx (as painful as that code is [*]), seems either > premature or very optimistic. So, how about scheduling the removal > once you get a feel for the bug reports that'll come in once 2.6.24 is > released. So you volunteer to maintain bcm43xx? Fine. Thanks a lot. > [*] Yeah, even as a user the code is painful. It *still* locks my > keyboard if I happen to disable the wireless while it's scanning. The > sooner bcm43xx is dead, the better. But b43 is quite obviously not a > full replacement for everyone. I'm pretty sure it is. Please carefully read the instructions on http://www.linuxwireless.org/en/users/Drivers/b43 especially for firmware installation. It will work very well. -- Greetings Michael. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/