On Thu, 18 Sep 2008 17:33:12 -0500 Larry Finger <[EMAIL PROTECTED]> wrote:
> Celejar wrote: > > > > Okay, I built and installed CRDA, and I now get: > > > > Band 1: > > Frequencies: > > * 2412 MHz > > * 2417 MHz > > * 2422 MHz > > * 2427 MHz > > * 2432 MHz > > * 2437 MHz > > * 2442 MHz > > * 2447 MHz > > * 2452 MHz > > * 2457 MHz > > * 2462 MHz > > * 2467 MHz (disabled) > > * 2472 MHz (disabled) > > * 2484 MHz (disabled) > > > > [This is also what I get with an earlier kernel.] > > > > But the card *still* won't associate with the hidden essid AP; is there > > anything else I need to do after 'make, make install' CRDA? > > No, with this output, you have definitely connected with CRDA. Now > that you have CRDA working, I think you may have to bisect again. > Certainly, the passive scanning would have made it difficult, if not > impossible, to connect to a hidden essid. As you say, you now have the > same channel listing as you had with the earlier kernel, thus your > bisection may converge on a different patch. Fortunately, it shouldn't > take too long. You can go a couple of patches earlier than the > regulatory change with a 'git bisect good dbcabfe1a5cfa192e'. > > Another option would be to uninstall CRDA by deleting /sbin/crda and > setting the CONFIG_WIRELESS_OLD_REGULATORY variable to y. At that > point, everything should be exactly as in the kernels prior to > adopting CRDA. This works fine, so I'm happy. If a bisection will help the devs, though, I'll be glad to do it. > Larry Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
