Re: NetworkManager Cannot Connect to Wireless Network
On Tue, Jul 13, 2010 at 3:41 AM, John Frankish <firstname.lastname@example.org> wrote:
>> -----Original Message-----
>> From: John [mailto:email@example.com]
>> Sent: Tuesday, 13 July, 2010 11:33
>> To: firstname.lastname@example.org
>> Subject: Re: NetworkManager Cannot Connect to Wireless Network
>> On Tue, Jul 13, 2010 at 3:14 AM, John Frankish <email@example.com>
>> > Hmm - now I see the following in dmesg:
>> > ipw2100: Fatal interrupt. Scheduling firmware restart
>> > There are many, many hits for this in google, but no solutions...
>> I assume you have gotten things working with WEP turned off? Go the
>> the router and disable WEP, and similarly on your computer select "no
>> encryption", and make sure everything works. I can't remember if you
>> said you had done that or if somebody else mentioned this, but just to
>> be sure, it's worth checking that things work properly in the most
>> simple setup.
> No, I have not tried turning WEP off, but on the same machine booted in tinycorelinux I can connect, albeit after a couple of attempts and not using NetworkManager.
> Also on three other laptops (none of which use the same hardware) and an iPhone there are no problems connecting.
> I'll try rmmod/modprobe ipw2100 (google suggests this might work) and if not, I guess it's ndiswrapper...
This last bit suggests that you are looking at hardware and
compatibility. Someone else on this thread has suggested
NetworkManager does not have a great reputation. That gives you lots
of variables (aka "suspects").
I have a Mepis 8 live CD that I sometimes use for testing (even if
it's a plain Debian system). Mepis 8 is basically Lenny, but Mepis
has (and has had for quite a long time) a very effective network
control package. If in doubt about an encrypted wifi connection, I
find that throwing in this live CD can at least give me a clue about
hardware and compatibility. It accepts the WEP key as either Hex or
Ascii (automatically translates to Hex), which can be handy.