Re: NetworkManager Cannot Connect to Wireless Network
On Thursday 15 July 2010 08:53:03 John Frankish wrote:
> > -----Original Message-----
> > From: Lisi [mailto:lisi.reisz@gmail.com]
> > Sent: Thursday, 15 July, 2010 11:40
> > To: debian-user@lists.debian.org
> > Subject: Re: NetworkManager Cannot Connect to Wireless Network
> >
> > On Thursday 15 July 2010 05:08:13 John Frankish wrote:
> > > > -----Original Message-----
> > > > From: Lisi [mailto:lisi.reisz@gmail.com]
> > > > Sent: Tuesday, 13 July, 2010 18:46
> > > > To: debian-user@lists.debian.org
> > > > Subject: Re: NetworkManager Cannot Connect to Wireless Network
> > > >
> > > > Why not try uninstalling Network Mangler and using someother method -
> > > > e.g.
> > > > WICD (my own preferred solution), /etc/network/interfaces or some
> > > > other manager?
> > > >
> > > > Lisi
> > >
> > > I tried a few more things:
> > >
> > > 1. NetworkManager
> > > I get the errors below and rmmod/modprobe ipw2100 does not help. Since
> > > only NetworkManager and not wicd nor "the old way" produces these error
> > > messages, I presume this is a bug.
> > >
> > > $ dmesg | grep ipw2100
> > > [6.807473] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver,
> > > git-1.2.2 [6.807478] ipw2100: Copyright(c) 2003-2006 Intel Corporation
> > > [6.829420] ipw2100 0000:01:0a.0: PCI INT A -> Link[LNKG] -> GSI 11
> > > (level, low) -> IRQ 11
> > > [6.830090] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
> > > [6.830117] ipw2100 0000:01:0a.0: firmware: requesting ipw2100-1.3.fw
> > > [39.906727] ipw2100: Fatal interrupt. Scheduling firmware restart.
> > > [78.668486] ipw2100: Fatal interrupt. Scheduling firmware restart.
> > > [130.105385] ipw2100: Fatal interrupt. Scheduling firmware restart.
> > >
> > > 2. wicd
> > > All attempts to connect to the wireless network result in an error
> > > message "bad password" There are no errors in dmesg
> > >
> > > 3. This works without errors in dmesg and wcid recognizes the link is
> > > connected
> > >
> > > $ cat /etc/network/interfaces
> > > ...
> > > # wireless
> > > allow-hotplug eth2
> > > iface eth2 inet dhcp
> > > wireless-essid myessid
> > > wireless-key 12:34:56:78:9A:BC:DE:F1:23:45:67:89:AB
> > > wireless-keymode restricted
> >
> > When trying WICD did you:
> >
> > 1. Uninstall Network Mangler
> >
> > 2. Comment out the wireless entries in /etc/network/interfaces
> >
> > 3. Reboot
> >
> > 4. Run WICD
> >
> > If you have not (and you need to have done all of them), I should try
> > it now.
> >
> > It is possible to stop and restart the network without rebooting, but I
> > feel
> > that this way makes sure that everyting has to restart. Others MMV.
> >
> > Lisi
>
> 1. Yes, 2. Yes, 3. Yes, 4. Yes :)
Oh dear!!
Setting my granddaughter's laptop to talk to her school's wireless network was
a nightmare, and I never did find out why. It connected to other wireless
routers without a problem. I tried 3 - or was it 4? - different distros, I
tried 3 different wireless cards, I asked for help from someone more
knowledgable and experienced than I, I tore my hair out. Eventually, with
Open Suse 11.00, I was getting some sort of response, but still not an actual
connection. In the end, the one person in the school IT department who knew
anything about Linux took the almost-connecting Open Suse install off to the
school IT lab, and came back with it working, having worked thro' several
wireless cards that they had lying around, and found one that worked, which
they donated to her. He may also have done some tweaking,
My laptop with Lenny and that same card does not connect at her school - but
connects without hesitation anywhere else.
I believe the American expression is "go figure!". You have my sympathy, but
I am for now out of ideas.
I assume that you have checked the driver?
Lisi
Reply to: