Re: NM and broadcom stuff with ndiswrapper

["Darren Albers" <dalbers gmail com>]

Unfortunately your first email was a little vague so nobody probably
knew what to say...  I will take a stab at answering but it is likely
that I am misdiagnosing your problem completely but here goes anyway! 
:-)

I think the problem you are having is an issue with the version of
NDISWrapper you have not fully supporting the latest WEXT.  From what
I understand this was fixed and the NDISWrapper has full WEXT support
in CVS.

Because the NM devs did not want to support 15+ different cards they
focused on supporting the Wireless Extensions (WEXT) standard and
hoped to push developers to make their cards compliant.

IF (Notice I said IF ;) ) this is your problem you have three options:
1) Use the open-source driver from: http://bcm43xx.berlios.de/ 
According to this page that driver works: 
http://live.gnome.org/NetworkManagerHardware   *Note* Some members of
the Ubuntuforums have reported that these drivers are somewhat slow.
2) Update to the latest version of NDISWrapper
3) Build Network Manager yourself but apply the patch that Robert Love
posted back in march that adds specific support for NDISWrapper and
MADWIFI drivers.
http://mail.gnome.org/archives/networkmanager-list/2006-March/msg00068.html

I hope this helps!

On 4/26/06, Gene Heskett <gene heskett verizon net> wrote:
> On Thursday 20 April 2006 12:37, Gene Heskett wrote:
>
> 6 days ago, and no reply?  I was recommended to take my questions here,
> but I'm wondering if I'm in the right store here folks.
>
> >Greetings;
> >
> >Is there a snowballs chance of making this (NM) work?
> >
> >HP dv532us lappy, amd64 turion, i386 version of FC5 currently
> > installed.
> >
> >Configured by hand, with fixed addresses all around my local home
> >network, using the drivers from the XP install also on that disk,
> > seems to work just fine.
>
> I've since reconfigured the home network to use dhcp, and it works just
> fine if I do a service network start.  Do a stop, and start NM, and
> there is no connection.
>
> Doing an iwconfig when NM is running discloses that the only thing
> different between a working link and non-working link is that when NM
> is running there is not a WEP key shown in the iwconfig output.
>
> Is this enough info to trigger a response?
>
> >But I have to haul it 900 miles to a job-site & live in a wifi equipt
> >motel for a couple of months.  It would be nice to just start NM and
> >have it find and configure it to work there.
>
> --
> Cheers, Gene
> People having trouble with vz bouncing email to me should add the word
> 'online' between the 'verizon', and the dot which bypasses vz's
> stupid bounce rules.  I do use spamassassin too. :-)
> Yahoo.com and AOL/TW attorneys please note, additions to the above
> message by Gene Heskett are:
> Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>