It was (is) running a pretty standard slack32 13.0 and I recall having trouble with both the bcm chipset installed and the pcmcia card he was using which had the same chip.
Long story short, what made it work was using fw-cutter or whatever it's called and using the force option on a driver whose checksum it didnt like (that I downloaded from some spyware-laden windows driver website) and it produced a proper set of firmware modules.
Another note: Slack uses Wicd as the default method of controlling wifi interfaces in the gui, and it's been my experience that it's the least error-prone (if you're not familiar it consists of a python-based control panel and a daemon, just make sure you're a member of netdev).
Also it's been my experience that some laptops seem to have an airplane mode switch that just kills the antenna, but the chipset stays active and tries to behave properly but can't actually connect to anything.
And one last thing, I don't know about debian, but some distros make ifconfig and ifconfig -a do different things. IE without the -a it only displays currently activated interfaces. It wouldnt hurt to make sure you're not trying to interface with a software ghost interface when the real one is quietly inactive.
Good luck, and hopefully someone will make a wifi card worth owning one of these days >.>
-a
_______________________________________________
BLUG mailing list
BLUG@linuxfan.com
http://mailman.cs.indiana.edu/mailman/listinfo/blug
No comments:
Post a Comment