Re: ndiswrapper and NetworkManager, and sysfs/HAL

[Joe Barnett <thejoe gmail com>]

yeah, i looked at it a little more, and after adding bcmwl5.sys to the
fully supported list, the NMApplet shows up :)

thanks for all the help,
-Joe

On Fri, 5 Nov 2004 21:05:54 -0500 (EST), Dan Williams <dcbw redhat com> wrote:
> Hi,
> 
> The problem is here:
> Nov  5 17:55:14 localhost NetworkManager: PCI driver for 'wlan0' is
> 'bcmwl5.sys'Nov  5 17:55:14 localhost NetworkManager: wlan0: Driver
> support level is unsupported
> 
> I added whitelisting of wireless drivers a while back, but more and more I
> think that's not the right thing to do since there are so many, and using
> ndiswrapper will just make matters more complicated because the driver
> name could be so many things.  I'll probably remove that code.
> 
> Dan
> 
> 
> 
> On Fri, 5 Nov 2004, Joe Barnett wrote:
> 
> > if it helps at all, here is the contents of syslog when I start dbus
> > (and hence, networkamanger)
> >
> >
> > On Fri, 5 Nov 2004 17:51:22 -0800, Joe Barnett <thejoe gmail com> wrote:
> > > I applied the patch to ndiswrapper 0.10, and now have both a driver
> > > and a device symlink in the /sys/class/net/wlan0 directory that seem
> > > to point to the correct device and driver, but NetworkManager still
> > > doesn't seem to be working, with the same symptoms I saw before.  I
> > > also noticed in the syslog taht NetworkManager is not detecting any
> > > wireless devices:
> > >
> > > AUTO: Best wireless device = (null) (null).
> > >
> > > I've updated http://sweeze.ath.cx/~jbarnett/advanced.jpg with the new
> > > "Advanced" tab in hal-device-manager.  The PCI and Device tabs are
> > > unchanged.
> > >
> > > Thanks,
> > > -Joe
> > >
> > >
> > >
> > >
> > > On Fri, 5 Nov 2004 13:14:14 -0500, Joe Ammond <joe ammond org> wrote:
> > > > Dan Williams scribbled:
> > > > > Great!!  I've seen about 10 people using ndiswrapper so far that are
> > > > > having problems, both on this list and Fedora lists.  Could you post the
> > > > > patch to this list (or email it to me, I'm interested in it)?  How hard
> > > > > will it be to get upstream?
> > > >
> > > > I'm attaching it and CC:ing this list as well as the
> > > > ndiswrapper-general list.  I don't know how difficult this will
> > > > be to get included upstream.  It was a farily trivial patch to
> > > > get working.  This patch is against wrapper.c from ndiswrapper-0.11.
> > > >
> > > > Caveats: this is my first delving into kernel code.  The USB patches
> > > > are untested, as I don't have any USB/ndiswrapper devices.  The
> > > > kludge of passing NULL as the device if the kernel rev is <2.6 is
> > > > icky, but it works.
> > > >
> > > > > What the ndiswrapper developers have to understand is that their stuff
> > > > > is fundamentally broken until they support sysfs.  They don't really
> > > > > need a 'driver' link (though it would be really, really nice), but a
> > > > > 'device' link is almost mandatory.  It has to get done in ndiswrapper
> > > > > because the Windows drivers, of course, aren't going to set a NETDEV on
> > > > > themselves :)
> > > >
> > > > Can't imagine why.  :)
> > > >
> > > > > Dan
> > > >
> > > > ja.
> > > > --
> > > > Joe Ammond                                                  joe ammond org
> > > >               My new toy: http://www.ammond.org/Spitfire
> > > >
> > > >
> > > > _______________________________________________
> > > > NetworkManager-list mailing list
> > > > NetworkManager-list gnome org
> > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > >
> > > >
> > > >
> > > >
> > >
> >
>