NOTHING would please me more than to see your device work. I feel I would not be happy if it were not to work.And yet, unfortunately, in this imperfect world I must work with some imperfections... like....
Zero diagnostic information.Ndiswrapper typically works in about 5 seconds, so not only no diagnostic information, but your "BS programmer" is 4 hours 59 minutes and 55 seconds full of "BS".
You don't mention your kernel version. You don't include a uname -a or a dmesg | grep bcm43 Now let's talk English "chip talking" -- meaningless "a kernel build" -- meaningless "wireless was showing" -- meaningless "wifi switch light" -- meaningless "not making up to" -- meaningless "actually use the signal" -- meaningless"it suddenly stops" -- almost meaningless. SOmething that might have been previously defined (but wasn't) no longer words.
"it's on again" -- same comment as above "Any clues" -- no, you don't have anySO... I'd say "good luck" but it looks like you don't have any of that either.
Ehud Robert Easter 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?_______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
