Brennan Ashton wrote: > On 7/4/07, Robert Easter <[EMAIL PROTECTED]> wrote: >> It took a BS programmer over five hours, but he got my bcm4318 chip >> talking to my computer with the NDISWrapper and a kernel build. Before >> that the wireless was showing on the laptop's wifi switch light but not >> making up to the computer to actually use the signal. Now, after six >> days, it suddenly stops. Give it a few days, and it's on again. Any clues?
What does BS mean in this context? > Ok i am going to try to be nice, as i myself have been chewed out by > this forum before (improper email reply edict), and as i had a similar > problem i think, but as has been explained before its hard to tell. > First there is a transmit power problem that has been hard to fix > (correct me if i have misunderstood some of the other emails that flow > though here) this is going to make connecting to some networks very > flaky if not impossible when you are father away. Several of us try very hard to make this forum helpful, and not chew out the OP, but it is very hard to diagnose a problem when crucial information is missing. Suppose I asked for help in diagnosing my Ford truck and I didn't tell you that it is a diesel, and I didn't even say whether it started, or not. For the record, diagnosis of problems require the kernel version (uname -r), any patches that have been applied, the results from the command 'dmesg | grep bcm43xx', information about encryption on the access point, and any additional software being used to connect (NetworkManager, etc.). As stated below, if you want to use ndiswrapper, go elsewhere. We have done a lot of work to avoid that!! > As for the ability to connect sometimes and not others, it is > something called i need to use the new kernel. Or use rmmod bcm43xx a > lot. If you are using a distros kernel, it is very likely that it > wont work, so i direct your attention toward www.kernel.org. At the > time that my system was exhibiting that behavior, i applied this patch > and it went away > https://lists.berlios.de/pipermail/bcm43xx-dev/2007-February/003819.html > . With the newer kernels, it should not be a problem. I still have > problems when i am to far away from my AP, but in a reasonable range, > it is very functional. > > a uname -a would be helpful > lspci | grep Broadcom > dmesg | grep bcm43xx > > Also that tidbit about the light was completely useless, it is > hardware not software (the filament in your ceiling light does not > effect whether or not the wall switch opens and closes) > > If wont use the bcm43xx driver you are not going to find what people > say here very useful. > > Well that is my best guess at what you were trying to say. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
