Ubuntu crashes (?) my wireless adapter from time to time

Sat Apr 9 13:21:47 UTC 2005

Hi,

a couple of day ago I made a post with a wireless troubleshoot guide 
that is availibe in the wiki, too. Please do me the favour and have a 
read through it and post the outputs of iwconfig when you should be 
connected as well as the interfaces file. Otherwise we can hardly help you.

thanks
.christoph

Behrang Saeedzadeh wrote:
> Any ideas :(
> 
> This is still happening now and then :((
> 
> BTW, This is a discussion on Linux Thinkpad mailing list about a similar 
> problem:
> 
> Hi all
> 
> I'm running Debian testing on a T42 2378-JZM which has the Intel 2200BG
> wifi adapter. I've been using the ipw2200 driver without a hitch until
> this morning. I have used the contributed debian ipw2200-source package,
> and have simply used module-assistant to update the driver as and when
> updates occur.
> 
> This morning I downloaded the new source package, built it fine, and
> re-loaded the module only to discover that I could no-longer associate
> with an access point. Although `iwlist eth1 scanning` showed the access
> point, and although I'd configured the essid and the WEP key, I could
> not associate. (This was version 1.0.2, whereas I had previously used
> 1.0.0) I used the same firmware, version 2.2 (latest) with both module
> versions.
> 
> There's no error in dmesg or syslog ... and I'm a bit stumped ...
> 
> Has anyone else had similar problems ?
> 
> (I've since downgraded to 1.0.2 vanilla, and 1.0.1 in an attempt to get
> online and neither of these versions were able to associate. I'm using
> 1.0.0 vanilla now, without any problems at all)
> 
> -----
> 
> Hi David,
> 
> I've had similar issues with this version of the driver.
> Unfortunately, I can't offer you an explanation nor a reliable
> solution but what I've found to get it to work is to use the load
> script instead of modprobe that comes with the driver distribution
> to load the driver, then sometimes I need to run iwconfig eth1 essid
> <> a few times to get it to stick. If that fails and you've been
> trying a few things to get it to associate, try rebooting. I've
> found that many times it'll associate right up after a fresh reboot.
> 
> I think where things may get messed up is switching from one wireless
> network to another and an extra reboot (at least to me) seems to help.
> 
> Maybe someone who's more familiar with how wireless works on Linux can
> give a more reliable explanation and/or solution?
> 
> Thank you very much!
> 
> ----
> 
> 
> Jeff wrote:
> 
>>On Fri, 8 Apr 2005, David de Hoog wrote:
>>
>>
>>
>>>Hi all
>>>
>>>I'm running Debian testing on a T42 2378-JZM which has the Intel 2200BG
>>>wifi adapter. I've been using the ipw2200 driver without a hitch until
>>>this morning. I have used the contributed debian ipw2200-source package,
>>>and have simply used module-assistant to update the driver as and when
>>>updates occur.
>>>
>>>This morning I downloaded the new source package, built it fine, and
>>>re-loaded the module only to discover that I could no-longer associate
>>>with an access point. Although `iwlist eth1 scanning` showed the access
>>>point, and although I'd configured the essid and the WEP key, I could
>>>not associate. (This was version 1.0.2, whereas I had previously used
>>>1.0.0) I used the same firmware, version 2.2 (latest) with both module
>>>versions.
>>>
>>>There's no error in dmesg or syslog ... and I'm a bit stumped ...
>>>
>>>Has anyone else had similar problems ?
>>>
>>>(I've since downgraded to 1.0.2 vanilla, and 1.0.1 in an attempt to get
>>>online and neither of these versions were able to associate. I'm using
>>>1.0.0 vanilla now, without any problems at all)
>>>
>>>Cheers
>>>--
>>>David de Hoog <dehood01 at student.uwa.edu.au>
>>
>>
>>Hi David,
>>
>>I've had similar issues with this version of the driver.
>>Unfortunately, I can't offer you an explanation nor a reliable
>>solution but what I've found to get it to work is to use the load
>>script instead of modprobe that comes with the driver distribution
>>to load the driver, then sometimes I need to run iwconfig eth1 essid
>><> a few times to get it to stick. If that fails and you've been
>>trying a few things to get it to associate, try rebooting. I've
>>found that many times it'll associate right up after a fresh reboot.
>>
>>I think where things may get messed up is switching from one wireless
>>network to another and an extra reboot (at least to me) seems to help.
>>
>>Maybe someone who's more familiar with how wireless works on Linux can
>>give a more reliable explanation and/or solution?
>>
>>Thank you very much!
>>
>>-Jeff
> 
> 
> i don't know about how dibian handles this, but at least in gentoo there
> is a startup script for the ntwork-interfaces you want to have up on
> boot time.
> 
> if you rerun this init-script (via /etc/init.d/net.ath0 restart) it
> solves this problem at least for me (with a different card) but
> nevertheless, i sometimes have the same problem after switching WLANs
> 
> ----
> 
> On Apr 9, 2005 3:20 PM, Behrang Saeedzadeh <behrangsa at gmail.com> wrote:
> 
>>Hi all
>>
>>This has happened two times sinece I installed Hoary on my system 
>>yesterday. Suddenly my wireless connection is not working anymore. A 
>>screenshot showing the wireless conn. indicator is attached.
>>
>>I tried to solve it without restarting the system by executing the 
>>following commands with no success:
>>
>>behrangsa at Ubuntu:~$ sudo ifup eth1
>>Password:
>>Sorry, try again.
>>Password:
>>ifup: interface eth1 already configured
>>
>>This showed that my wireless adapter is already up. Then I did this:
>>
>>behrangsa at Ubuntu:~$ sudo ifdown eth1
>>Internet Systems Consortium DHCP Client V3.0.1
>>Copyright 2004 Internet Systems Consortium.
>>All rights reserved.
>>For info, please visit http://www.isc.org/products/DHCP
>>
>>sit0: unknown hardware address type 776
>>sit0: unknown hardware address type 776
>>Listening on LPF/eth1/00:0e:35:78:d7:f6
>>Sending on LPF/eth1/00:0e:35:78:d7:f6
>>Sending on Socket/fallback
>>DHCPRELEASE on eth1 to 192.168.1.1 <http://192.168.1.1> port 67
>>
>>behrangsa at Ubuntu:~$ sudo ifup eth1
>>Internet Systems Consortium DHCP Client V3.0.1
>>Copyright 2004 Internet Systems Consortium.
>>All rights reserved.
>>For info, please visit http://www.isc.org/products/DHCP
>>
>>sit0: unknown hardware address type 776
>>sit0: unknown hardware address type 776
>>Listening on LPF/eth1/00:0e:35:78:d7:f6
>>Sending on LPF/eth1/00:0e:35:78:d7:f6
>>Sending on Socket/fallback
>>DHCPDISCOVER on eth1 to 255.255.255.255 <http://255.255.255.255> port 67 
>>interval 6
>>DHCPDISCOVER on eth1 to 255.255.255.255 <http://255.255.255.255> port 67 
>>interval 11
>>DHCPDISCOVER on eth1 to 255.255.255.255 <http://255.255.255.255> port 67 
>>interval 7
>>DHCPDISCOVER on eth1 to 255.255.255.255 <http://255.255.255.255> port 67 
>>interval 12
>>DHCPDISCOVER on eth1 to 255.255.255.255 <http://255.255.255.255> port 67 
>>interval 16
>>DHCPDISCOVER on eth1 to 255.255.255.255 <http://255.255.255.255> port 67 
>>interval 9
>>No DHCPOFFERS received.
>>No working leases in persistent database - sleeping.
>>
>>Again, I couldn't solve the problem without restarting.
>>
>>BTW - The wireless went of once again when I was writing this email :(
>>
>>Any help will be appreciated.
>>
>>Best Regards,
>>Behrang.
>>
>>-- 
>>
>>Behrang Saeedzadeh
>>http://www.jroller.com/page/behrangsa
>>
>>
> 
> 
> 

-- 

Christoph Georgi
-----------------------------
email.  christoph.georgi at web.de
fon.	+64 (0)9 815 8259

registered linux user #380268
ubuntulinux 4.10 (warty)