Control: reassign -1 firmware-ipw2x00 0.36+wheezy.1 On Mi, 13 nov 13, 18:44:36, Andres Salomon wrote: > Package: firmware-ipw2200 > Version: 0.36+wheezy.1 > > On my thinkpad x40, after a full day of use the wireless stops > functioning. This is with the ipw2200 3.1 firmware, which is currently > in wheezy (and sid, I believe). Reloading the ipw2200 module allows it > to start working again. I've tried this with multiple kernels (3.2 in > wheezy, 3.10 in wheezy-backports) and get the same result. > > I found a thread that looks like a similar problem, which suggested > downgrading the firmware. I will give that a try with 3.0 firmware. > > Here's the thread: > http://forums.gentoo.org/viewtopic-t-819782-start-0.html > > Here's dmesg output: > [ 8.613489] libipw: 802.11 data/management/control stack, git-1.1.13 > [ 8.613552] libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com> > [ 8.876998] snd_intel8x0 0000:00:1f.5: setting latency timer to 64 > [ 9.398883] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq > [ 9.398962] ipw2200: Copyright(c) 2003-2006 Intel Corporation > [ 9.399455] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection > [ 9.442738] ipw2200 0000:02:02.0: firmware: agent loaded ipw2200-bss.fw into memory > [ 9.570550] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels) > [ 9.800073] intel8x0_measure_ac97_clock: measured 55167 usecs (2658 samples) > [ 9.800137] intel8x0: clocking to 48000 > [ 9.803211] [drm] Memory usable by graphics device = 128M > [ 9.803279] i915 0000:00:02.0: setting latency timer to 64 > [ 9.804832] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). > [ 9.804891] [drm] Driver supports precise vblank timestamp query. > [ 9.813730] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem > [ 9.824340] [drm] initialized overlay support > [ 9.926898] fbcon: inteldrmfb (fb0) is primary device > [ 10.570137] Console: switching to colour frame buffer device 128x48 > [ 10.589161] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device > [ 10.589385] i915 0000:00:02.0: registered panic notifier > [ 10.589610] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0 > [ 12.271843] Adding 498008k swap on /dev/sda2. Priority:-1 extents:1 across:498008k > [ 12.903779] EXT3-fs (sda3): using internal journal > [ 13.146486] loop: module loaded > [ 15.235663] kjournald starting. Commit interval 5 seconds > [ 15.236284] EXT3-fs (sda1): using internal journal > [ 15.245055] EXT3-fs (sda1): mounted filesystem with ordered data mode > [ 28.637793] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 1770.320059] ipw2200: Firmware error detected. Restarting. > [ 2444.719565] ipw2200: Firmware error detected. Restarting. > [ 2582.956118] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. > [ 3993.115919] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. > [ 4224.987218] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. > [ 4674.398093] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. > [ 5091.795353] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. > [ 5624.415277] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. > [ 5658.786056] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. > [ 7039.317926] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command. > [ 7547.025554] ipw2200: Failed to send ASSOCIATE: Already sending a command. > [16192.912553] e1000: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX > [16192.912630] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt
Attachment:
signature.asc
Description: Digital signature