[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ipw2200 wireless network card stops working



On Mon, May 08, 2006 at 12:02:46AM +0200, heimdal200599-news@yahoo.no wrote:
> Anton Piatek wrote:
> >Hi,
> >I am wondering if anyone has had problems with their ipw2200 network
> >card losing connection after a while.
> >It can vary between a minute and twenty before the connection stops, and
> >I cannot figure out why.
> >
> >I don't *think* I have anything running trying to reconfigure it, and it
> >still has the right ip address and routes set after it dies, I just
> >cannot ping anything apart from my own NIC.
> >
> >I have tried a 2.6.15 and .16 kernel with the builtin iee80211 stack and
> >ipw2200 drivers, and even the latest stable and testing ipw drivers (and
> >new firmware and matchin ieee stack).
> ...
> 
> I had a similar problem when I upgraded linux-image from 2.6.11 to 
> 2.6.15. No sensible info in the logs, but finally I checked out the 
> parameters for the ipw2200 module and tried hwcrypo=0. That made it. I 
> have put it in /etc/modules:
> 
> ipw2200 hwcrypto=0 led=1
> 
> (led=1 turns on the wireless LED)
> 
> I'm using the ipw2200 and ieee80211* modules from the linux-image package.

Also experiencing it on a 2.6.15 kernel here:
	Linux fujitsu 2.6.15-dtsplash #3 Sun Apr 30 07:18:16 BST 2006 i686 GNU/Linux
on a Fujitsu P7120 notebook with an integrated wireless interface
detected as follows:
  ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, git-1.0.8
  ipw2200: Copyright(c) 2003-2005 Intel Corporation
  ACPI: PCI Interrupt 0000:06:05.0[A] -> GSI 18 (level, low) -> IRQ 193
  ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection

Problems with the sata CD meant that I have not tried any earlier
kernels.

I have also been getting warning messages from the driver which I
originally thought might be related, but though they were being
generated about once an hour on Friday, I have been waiting for
a recurrnce since the first post on this subject (so that I could
include the content in my response), and though I
have had one network lockup since, I have not had any more of the
messages - so I now suspect the messages are triggered by some
interaction with other wireless activity - probably from nearby
offices which are not doing anything on the weekend.

I'll post a follow up with the message I am getting when they
resume...

What sort of configuration are you using? I have not yet tried
to use any protocol level encryption. I am restricting access
by restricting MAC addresses in the router config, and using
ssh etc for privacy.

Are you using the same firmware as me:
  digbyt@fujitsu:~$ ls -l /lib/firmware
  total 551
  -rw-r--r-- 1 root root   6472 2006-04-19 01:06 ipw-2.4-boot.fw
  -rw-r--r-- 1 root root 168344 2006-04-19 01:06 ipw-2.4-bss.fw
  -rw-r--r-- 1 root root  16334 2006-04-19 01:06 ipw-2.4-bss_ucode.fw
  -rw-r--r-- 1 root root 162884 2006-04-19 01:06 ipw-2.4-ibss.fw
  -rw-r--r-- 1 root root  16312 2006-04-19 01:06 ipw-2.4-ibss_ucode.fw
  -rw-r--r-- 1 root root 168344 2006-04-19 01:06 ipw-2.4-sniffer.fw
  -rw-r--r-- 1 root root  16344 2006-04-19 01:06 ipw-2.4-sniffer_ucode.fw
  digbyt@fujitsu:~$ sum /lib/firmware/*
  50619     7 /lib/firmware/ipw-2.4-boot.fw
  11311   165 /lib/firmware/ipw-2.4-bss.fw
  01132    16 /lib/firmware/ipw-2.4-bss_ucode.fw
  44032   160 /lib/firmware/ipw-2.4-ibss.fw
  52000    16 /lib/firmware/ipw-2.4-ibss_ucode.fw
  53348   165 /lib/firmware/ipw-2.4-sniffer.fw
  05122    16 /lib/firmware/ipw-2.4-sniffer_ucode.fw

Regards,
DigbyT
-- 
Digby R. S. Tarvin                                          digbyt(at)digbyt.com
http://www.digbyt.com



Reply to: