I think the problem solved itself. I found an updated package of ndiswrapper
at ATrpms.net, and after I installed that, it started working (for the most
part, it still takes a couple of connection attempts sometimes).
Thanks for your help,
Andrew
On 10/15/07, Dan Williams <[EMAIL PROTECTED]> wrote:
>
> On Sun, 2007-10-14 at 16:01 -0400, Andrew Pegram wrote:
> > Sorry I took so long getting back to you. I've attached the iwevent
> > output as well as the relevant section of the syslog.
>
> So this is because ndiswrapper never actually associates to the access
> point that NM has told it to associate to. You'll likely have to enable
> ndiswrapper debugging or something to see what's going on there.
>
> Dan
>
> > On 10/12/07, Dan Williams <[EMAIL PROTECTED]> wrote:
> > On Fri, 2007-10-12 at 00:07 -0400, Andrew Pegram wrote:
> > > Hello all
> > >
> > > I don't know if it actually went out the last time I sent
> > this, so I'm
> > > sending it again (sorry for the repeat, if it is one).
> > >
> > > I'm having an issue with connecting to wireless networks
> > through NM.
> > > It will connect to wired networks just fine, but it refuses
> > to connect
> > > to any type of wireless network (secured WEP/WPA or
> > unsecured). I have
> > > checked the syslog and found the following warning
> > (sensitive
> > > information removed):
> > >
> > > Oct 6 23:42:06 <Hostname> NetworkManager: <WARN>
> > > nm_device_802_11_wireless_set_essid(): error setting ESSID
> > to '' for
> > > device wlan0: Invalid argument
> > >
> > > I know that the program can read the ESSID from the network
> > because
> > > earlier in the log, it has:
> > >
> > > Oct 6 23:41:44 <Hostname> NetworkManager: <info> User
> > > Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / VCU
> > >
> > > ('VCU' is the ESSID)
> > >
> > > I've tried reinstalling everything to do with NetworkManager
> > and
> > > ndiswrapper, and nothing seems to be working. If I haven't
> > posted
> > > enough information, I can post everything in the log from
> > the time I
> > > select the WLAN in the drop-down menu until it stops trying
> > to
> > > connect.
> >
> > During an association attempt, can you run the program
> > "iwevent" (it
> > might be in /sbin or /usr/sbin) and reply with it's output?
> >
> > Thanks!
> > Dan
> >
> > > Thank you for your time,
> > > Andrew
> > > _______________________________________________
> > > NetworkManager-list mailing list
> > > NetworkManager-list@gnome.org
> > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
> >
>
>
_______________________________________________
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
