Prev: Asus M4A88TD-V EVO/USB3 (was:Re: AM3 socket Asus M4A87TD EVO ...)
Next: GRUB broken after upgrade on Macbook
From: John on 13 Jul 2010 05:20
On Tue, Jul 13, 2010 at 3:41 AM, John Frankish <j-frankish(a)slb.com> wrote:
>
>
>> -----Original Message-----
>> From: John [mailto:nesredep(a)gmail.com]
>> Sent: Tuesday, 13 July, 2010 11:33
>> To: debian-user(a)lists.debian.org
>> Subject: Re: NetworkManager Cannot Connect to Wireless Network
>>
>> On Tue, Jul 13, 2010 at 3:14 AM, John Frankish <j-frankish(a)slb.com>
>> wrote:
>> >
>> >
>> > 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.
>>
>> John
>>
> 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.

John


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/AANLkTincEfKERjwDCiKlvXyzNATDUA6VxEdrRsOQa1pd(a)mail.gmail.com
From: Lisi on 13 Jul 2010 10:50
On Tuesday 13 July 2010 08:41:58 John Frankish wrote:
> 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...

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



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/201007131545.30863.lisi.reisz(a)gmail.com
From: Mark on 13 Jul 2010 11:00
On Tue, Jul 13, 2010 at 7:45 AM, Lisi <lisi.reisz(a)gmail.com> wrote:

>
> 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
>

+1. WICD solved a similar problem on my girlfriend's laptop. NM couldn't
connect but WICD had no issues connecting.
From: Bruno Costacurta on 14 Jul 2010 05:40

> 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

+1 for WICD

With NetworkManager I faced some failures to connect to the (public so
no WEP or WAP) Wifi in my favorite bar : few times per month the Wifi
was correcly detected but NetworkManager was simply unable to connect
to it.

Now with WICD it simply works 24/7.

Bye,
Bruno

--
Linux Counter #353844
http://counter.li.org/


----------------------------------------------------------------


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100714110602.103697gutcf3c0s8(a)webmail.costacurta.org
From: John Frankish on 15 Jul 2010 00:10


> -----Original Message-----
> From: Lisi [mailto:lisi.reisz(a)gmail.com]
> Sent: Tuesday, 13 July, 2010 18:46
> To: debian-user(a)lists.debian.org
> Subject: Re: NetworkManager Cannot Connect to Wireless Network
>
> On Tuesday 13 July 2010 08:41:58 John Frankish wrote:
> > 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...
>
> 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


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/6AC5A55546F64545AE996F8200E3AC4E0333FA139C(a)NL0105EXC01V01.eur.slb.com
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Asus M4A88TD-V EVO/USB3 (was:Re: AM3 socket Asus M4A87TD EVO ...)
Next: GRUB broken after upgrade on Macbook