Stephen Sinclair wrote: >> No bcm43xx card works at higher than 11 MBs. Whenever any >> of the higher rates are selected, the TX signal strength drops >> considerably. > > Okay, I thought it was something similar. > > >> As you have git cloned the wireless-2.6 tree, it is very simple to do >> a git pull to update your source. You really should do that as a number >> of bugs that would cause your crashes and hangs have been fixed in the >> past couple of months. > > I finally got around to it, thanks. In fact, with my untrained git > skills I managed to mess it up due to the patches i'd applied earlier. > (PCI-E and manually enabling 4311.) > > Anyways, I ended up just re-cloning the wireless-2.6 tree using cg-clone.
For future reference, the command 'git checkout -F' will destroy any changes you have made and revert your git tree to the last one pulled. >> I'm pretty sure the problem is with the x86_64 version that I'm running >> No interrupts are delivered to the software. > > I've been meaning to set up a partition with a 64-bit installation of > Ubuntu or something, so when I manage to do that I'll let you know. > > > On to the results: > > I compiled and installed wireless-2.6 with no problems. Bcm43xx was > detected, and you are right, it seems much more stable. Even the > radio-enable light turns on and off appropriately when I toggle the > switch. > > Unfortunately, though, it acts as if it the radio is turned off. I > cannot associate with any AP, and "iwlist eth2 scan" lists nothing. Please run 'cat /proc/wireless' to see if interrupts are being delivered to the bcm43xx. > Now that I'm on an untouched wireless-2.6 kernel, I'll try to git-pull > more often and test whenever updates are available. > > (Is this the best method for testing the latest changes? I could apply > patches manually, but I'll have to learn how to "undo" those in git > properly.) A good way to apply patches is with the use of quilt. You can use the 'quilt import filename' to add a patch file to the quilt database. You then use 'quilt push' to apply the patch to the source tree. If there is a problem, your source is not messed up. To remove that patch file, use 'quilt pop'. If you want to roll your own patch, use 'quilt new some_descriptive_name', then change the source by using 'quilt edit source_file_name'. Once you have the source the way you want it, do a 'quilt refresh' to create the updated patch file. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
