Jason Lunz wrote:
[EMAIL PROTECTED] said:
As far as wireless goes you might steer clear of a laptop with
Broadcom wireless chipset if you want to be able to use software such
as Airsnort as the bcm43xx kernel module is still pretty limited.
it's progressing rapidly, though. My last laptop was an HP zv5000, and
the bcm43xx driver worked very well.
The only way the Broadcom chip will work with WPA is to use
ndiswrapper and the Windows NDIS drivers.
I used bcm43xx to do WPA on a daily basis.
Now, I suspect that a part of my problems are caused by having a 64-bit
cpu and the rest of the hardware being 32-bit, but that will probably be
I had no problems using bcm43xx in a 64-bit kernel to do WPA,
monitor mode/kismet/airsnort, pretty much everything.
true of any other laptop with a 64-bit cpu too. I'm forced into
running a 32-bit OS if I want wireless that starts with the OS. I
can't use ndiswrapper in a pure 64-bit environment as the only Windows
drivers available for the Broadcom chip are 32-bit and the 64-bit
bcm43xx kernel module is something I've never gotten to work in any
fashion.
ndiswrapper worked on that hardware for me in both 32- and 64-bit modes.
You need to get different firmware for 64-bit; it's a little harder to
find. I stopped using ndiswrapper as bcm43xx matured.
otoh, bcm43xx's functionality varies widely depending on exactly which
broadcom wireless part you have. Some hardware is still unsupported.
Jason
Interesting. What does lspci return as the part number for you, i.e.
14E4:xxxx?
Also, where did you find 64-bit firmware? All I've ever been able to
find is 32-bit.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
