"Bart Schaefer" barton.schaefer@gmail.com wrote:
On Nov 28, 2007 7:23 AM, David G. Miller dave@davenjudy.org wrote:
Now everything (sort of) "just works (TM)". I say "sort of" because I'm still running ndiswrapper since every time I've tried the bcm43xx kernel module it hasn't worked with my WAP.
I've had a similar experience with my HP. Did you manage to get NetworkManager and ndiswrapper to co-operate? I had to disable NetworkManager, but it'd be nice to use the profiles rather than reconfigure the network when changing access points.
I had it working for a while but it kept getting in the way when I was trying to get the bcm43xx module working. I went back to my old system of just having eth0 for the wired connection and eth1 for wireless and user controllable. Other than my home network, I don't have any other wireless networks that I connect to on a regular basis so this approach lets me manually control what happens when I'm trying to connect to some oddball network that I've never seen before and probably won't see again.
One thing I remember about getting NetworkManager and the piece that handles keys (not gnome-keyring; don't remember the name right now and the laptop is off) was to tell that piece to use the generic wireless kernel API instead of the ndiswrapper control interface. Seems weird but it worked. If you need more information, I can fire up the laptop at some point.
Cheers, Dave