Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: ipw2200:always disbling/enabling

  1. #1
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default ipw2200:always disbling/enabling

    hi,

    there are hundreds of the following statements in dmesg

    "ipw2200: Firmware error detected. Restarting."

    old problem! does anyone know of a new fix?

    also found it impossible to connect to hidden network!

    cheers
    ======

    os:
    Kernel: 4.12.11-1-default i686 (32 bit) Desktop: KDE Plasma 5.10.5
    Distro: openSUSE Tumbleweed 20170909
    Machine: Device: laptop System: TOSHIBA product: Satellite M60 v: PSM60E-0C801GGR
    Mobo: TOSHIBA model: EBQ10 v: Null BIOS: TOSHIBA v: V1.60 date: 03/16/2006
    CPU: Single core Intel Pentium M (-UP-) cache: 2048 KB speed: 1867 MHz (max)
    Graphics: Card: Advanced Micro Devices [AMD/ATI] RV410/M26 [Mobility Radeon X700]
    Display Server: x11 (X.Org 1.19.3) drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
    Resolution: 1680x1050@60.11hz
    OpenGL: renderer: ATI RV410 version: 2.1 Mesa 17.2.0 Direct Render: Yes

  2. #2
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Re: ipw2200:always disbling/enabling

    the output of dmesg | grep ipw was as follows,
    1 [ 19.152630] libipw: 802.11 data/management/control stack, git-1.1.13
    2 [ 19.152633] libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
    3 [ 19.618852] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kdmprq
    4 [ 19.618856] ipw2200: Copyright(c) 2003-2006 Intel Corporation
    5 [ 19.619462] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
    6 [ 20.065065] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
    7 [ 20.074417] ipw2200 0000:06:02.0 wlp6s2: renamed from eth0
    8 [ 35.348900] ipw2200: Firmware error detected. Restarting.
    9 [ 35.553308] ipw2200: Firmware error detected. Restarting.
    10 [ 37.416652] ipw2200: Firmware error detected. Restarting.
    ..........................................dito
    ..........................................dito
    ..........................................dito
    387 [ 3899.987321] ipw2200: Failed to send SYSTEM CONFIG: Already sending a command.
    388 [ 3906.291268] ipw2200: Firmware error detected. Restarting.
    389 [ 3907.182025] ipw2200: Firmware error detected. Restarting.
    ..........................................dito
    ..........................................dito
    ..........................................dito
    402 [ 3964.380660] ipw2200: Failed to send SYSTEM CONFIG: Already sending a command.
    403 [ 3964.420687] ipw2200: Firmware error detected. Restarting.
    404 [ 3965.092630] ipw2200: Firmware error detected. Restarting.
    405 [ 3965.662912] ipw2200: device failed to start within 500ms
    406 [ 3965.662941] ipw2200: Unable to load firmware: -62
    407 [ 3965.662943] ipw2200: Failed to up device
    408 [ 3976.000402] ipw2200: Firmware error detected. Restarting.
    409 [ 3978.675542] ipw2200: Firmware error detected. Restarting.
    410 [ 3979.359150] ipw2200: Firmware error detected. Restarting.
    ..........................................dito
    ..........................................dito
    ..........................................dito
    634 [ 12877.455439] ipw2200: Firmware error detected. Restarting.
    635 [ 12877.806336] ipw2200: Firmware error detected. Restarting.
    636 [ 12877.999893] ipw2200: Firmware error detected. Restarting.
    any comments appreciated

  3. #3
    Join Date
    Oct 2011
    Location
    Germany (Ore Mountains)
    Posts
    457

    Default Re: ipw2200:always disbling/enabling

    "me too".
    I see these errors too, but not that often.
    It started in June.
    I did not find a solution yet, only others with the same problem, and - according to Google - it is not new.

    e.g.: http://www.thinkwiki.org/wiki/Intel_...apter#Problems

    Hendrik

  4. #4
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Re: ipw2200:always disbling/enabling

    hi Hendrik

    thanks for the info,

    your reference addresses power saving in the modem card

    but power saving is disabled by default on this laptop

    see output below

    comparing dmesg output from yesterday and 30-March-2016 setup entries for the ipw2200 are identical but no disbling/enabling entries

    also the dmesg outputs for kernel 4.12 and 4.13 are similar for these anomalies, so have no idea when these started to appear

    cheers
    ======

    tosh-sm60<2017-09-25 09:38:45><13.2>... sudo iwconfig wlp6s2
    [sudo] password for root:
    wlp6s2 IEEE 802.11 ESSID:"3MobileWiFi-3984"
    ---Mode:Managed Frequency: 2.437 GHz Access Point:
    ---Bit Rate: 54 Mb/s Tx-Power= 20 dBm Sensitivity= 8/0
    ---Retry limit:7 RTS thr: off Fragment thr: off
    ---Encryption key: Security mode: open
    ---Power Management: off
    ---Link Quality= 89/100 Signal level= -30 dBm Noise level= -86 dBm
    ---Tx excessive retries: 0 Invalid misc: 0 Missed beacon: 4
    tosh-sm60<2017-09-25 09:48:28><13.2>...

  5. #5
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: ipw2200:always disbling/enabling

    Just an idea: I had serious issues with a printer which appeared ( after a very long search ) to be disabled immediately after enabling due to issues with the new powersaving on TW, so I had to blacklist the device in /etc/default/tlp . In my case dmesg reported an error, but no relation to powersaving.
    The file has entries for WIFI devoces as well, could this be something alike?
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  6. #6
    Join Date
    Oct 2011
    Location
    Germany (Ore Mountains)
    Posts
    457

    Default Re: ipw2200:always disbling/enabling

    The power management is already off.
    Today I got not the firmware errors, but this:
    Code:
    Sep 25 20:14:41 schlepptop.site NetworkManager[1488]: <info>  [1506363281.4034] device (wlp6s5): supplicant interface state: completed -> disconnected
    Sep 25 20:14:41 schlepptop.site NetworkManager[1488]: <info>  [1506363281.5036] device (wlp6s5): supplicant interface state: disconnected -> scanning
    Sep 25 20:14:41 schlepptop.site NetworkManager[1488]: <info>  [1506363281.8588] device (wlp6s5): supplicant interface state: scanning -> associating
    Sep 25 20:14:42 schlepptop.site NetworkManager[1488]: <info>  [1506363282.3237] device (wlp6s5): supplicant interface state: associating -> 4-way handshake
    Sep 25 20:14:42 schlepptop.site NetworkManager[1488]: <info>  [1506363282.3314] device (wlp6s5): supplicant interface state: 4-way handshake -> completed
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.1566] device (wlp6s5): supplicant interface state: completed -> disconnected
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.2575] device (wlp6s5): supplicant interface state: disconnected -> scanning
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.6078] device (wlp6s5): supplicant interface state: scanning -> associating
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.6230] device (wlp6s5): supplicant interface state: associating -> 4-way handshake
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.6312] device (wlp6s5): supplicant interface state: 4-way handshake -> completed
    Sep 25 20:47:03 schlepptop.site NetworkManager[1488]: <info>  [1506365223.6920] device (wlp6s5): supplicant interface state: completed -> disconnected
    Sep 25 20:47:03 schlepptop.site NetworkManager[1488]: <info>  [1506365223.7919] device (wlp6s5): supplicant interface state: disconnected -> scanning
    Sep 25 20:47:04 schlepptop.site NetworkManager[1488]: <info>  [1506365224.1483] device (wlp6s5): supplicant interface state: scanning -> associating
    Sep 25 20:47:04 schlepptop.site NetworkManager[1488]: <info>  [1506365224.1603] device (wlp6s5): supplicant interface state: associating -> 4-way handshake
    Sep 25 20:47:04 schlepptop.site NetworkManager[1488]: <info>  [1506365224.1692] device (wlp6s5): supplicant interface state: 4-way handshake -> completed
    Sep 25 20:48:24 schlepptop.site NetworkManager[1488]: <info>  [1506365304.8969] device (wlp6s5): supplicant interface state: completed -> disconnected
    Sep 25 20:48:24 schlepptop.site NetworkManager[1488]: <info>  [1506365304.9972] device (wlp6s5): supplicant interface state: disconnected -> scanning
    Sep 25 20:48:25 schlepptop.site NetworkManager[1488]: <info>  [1506365305.3496] device (wlp6s5): supplicant interface state: scanning -> associating
    Sep 25 20:48:25 schlepptop.site NetworkManager[1488]: <info>  [1506365305.8151] device (wlp6s5): supplicant interface state: associating -> 4-way handshake
    Sep 25 20:48:25 schlepptop.site NetworkManager[1488]: <info>  [1506365305.8242] device (wlp6s5): supplicant interface state: 4-way handshake -> completed
    I have no idea, what is causing this on-off game.

    Hendrik

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,698
    Blog Entries
    1

    Default Re: ipw2200:always disbling/enabling

    I've seen this kind of repetitive disconnecting and connecting process occur when there is an issue with the wireless encryption protocol in use. If you administer the router, you could try experimenting with the settings. (In the distant past, I recall a problematic wireless network when using a laptop with an Intel 2200 device.)

  8. #8
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Re: ipw2200:always disbling/enabling

    hi,

    thanks for the replies

    updated the kernel, 14.13.1 to 14.3.3, this evening

    the number of 'ipw2200: Firmware error detected. Restarting' has dropped
    from >600 to <15 over a 3000 second period

    not fixed but great improvement

    looks like its the kernel!? nothing else has changed

    cheers
    ======

  9. #9
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Re: ipw2200:always disbling/enabling

    correction

    should be
    'updated the kernel, 14.13.1 to 14.13.3, this evening'
    not
    'updated the kernel, 14.13.1 to 14.3.3, this evening'

  10. #10
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,558

    Default Re: ipw2200:always disbling/enabling

    Quote Originally Posted by hendwolt View Post
    The power management is already off.
    Today I got not the firmware errors, but this:
    Code:
    Sep 25 20:14:41 schlepptop.site NetworkManager[1488]: <info>  [1506363281.4034] device (wlp6s5): supplicant interface state: completed -> disconnected
    Sep 25 20:14:41 schlepptop.site NetworkManager[1488]: <info>  [1506363281.5036] device (wlp6s5): supplicant interface state: disconnected -> scanning
    Sep 25 20:14:41 schlepptop.site NetworkManager[1488]: <info>  [1506363281.8588] device (wlp6s5): supplicant interface state: scanning -> associating
    Sep 25 20:14:42 schlepptop.site NetworkManager[1488]: <info>  [1506363282.3237] device (wlp6s5): supplicant interface state: associating -> 4-way handshake
    Sep 25 20:14:42 schlepptop.site NetworkManager[1488]: <info>  [1506363282.3314] device (wlp6s5): supplicant interface state: 4-way handshake -> completed
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.1566] device (wlp6s5): supplicant interface state: completed -> disconnected
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.2575] device (wlp6s5): supplicant interface state: disconnected -> scanning
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.6078] device (wlp6s5): supplicant interface state: scanning -> associating
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.6230] device (wlp6s5): supplicant interface state: associating -> 4-way handshake
    Sep 25 20:45:41 schlepptop.site NetworkManager[1488]: <info>  [1506365141.6312] device (wlp6s5): supplicant interface state: 4-way handshake -> completed
    Sep 25 20:47:03 schlepptop.site NetworkManager[1488]: <info>  [1506365223.6920] device (wlp6s5): supplicant interface state: completed -> disconnected
    Sep 25 20:47:03 schlepptop.site NetworkManager[1488]: <info>  [1506365223.7919] device (wlp6s5): supplicant interface state: disconnected -> scanning
    Sep 25 20:47:04 schlepptop.site NetworkManager[1488]: <info>  [1506365224.1483] device (wlp6s5): supplicant interface state: scanning -> associating
    Sep 25 20:47:04 schlepptop.site NetworkManager[1488]: <info>  [1506365224.1603] device (wlp6s5): supplicant interface state: associating -> 4-way handshake
    Sep 25 20:47:04 schlepptop.site NetworkManager[1488]: <info>  [1506365224.1692] device (wlp6s5): supplicant interface state: 4-way handshake -> completed
    Sep 25 20:48:24 schlepptop.site NetworkManager[1488]: <info>  [1506365304.8969] device (wlp6s5): supplicant interface state: completed -> disconnected
    Sep 25 20:48:24 schlepptop.site NetworkManager[1488]: <info>  [1506365304.9972] device (wlp6s5): supplicant interface state: disconnected -> scanning
    Sep 25 20:48:25 schlepptop.site NetworkManager[1488]: <info>  [1506365305.3496] device (wlp6s5): supplicant interface state: scanning -> associating
    Sep 25 20:48:25 schlepptop.site NetworkManager[1488]: <info>  [1506365305.8151] device (wlp6s5): supplicant interface state: associating -> 4-way handshake
    Sep 25 20:48:25 schlepptop.site NetworkManager[1488]: <info>  [1506365305.8242] device (wlp6s5): supplicant interface state: 4-way handshake -> completed
    I have no idea, what is causing this on-off game.

    Hendrik
    Hi Hendrik

    do not have the same response you are getting

    after todays update the output was

    tosh-sm60<2017-09-27 16:37:14><Downloads>... dmesg |grep ipw
    [ 18.214275] libipw: 802.11 data/management/control stack, git-1.1.13
    [ 18.214277] libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
    [ 18.659010] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kdmprq
    [ 18.659014] ipw2200: Copyright(c) 2003-2006 Intel Corporation
    [ 18.659612] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
    [ 18.878091] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
    [ 18.886059] ipw2200 0000:06:02.0 wlp6s2: renamed from eth0
    [ 1116.071864] Modules linked in: lib80211_crypt_ccmp af_packet nf_log_ipv6 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_limit ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 xt_pkttype xt_tcpudp iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables radeon snd_intel8x0m snd_intel8x0 snd_ac97_codec snd_pcm hwmon ttm drm_kms_helper snd_timer drm fb_sys_fops syscopyarea sysfillrect ipw2200 sysimgblt snd i2c_algo_bit libipw lib80211 iTCO_wdt iTCO_vendor_support lpc_ich toshiba_bluetooth 8139too 8139cp cfg80211 mii joydev i2c_i801 soundcore ac97_bus video rfkill pcspkr shpchp battery button acacpi_cpufreq xfs libcrc32c hid_generic usbhid
    tosh-sm60<2017-09-27 16:37:58><Downloads>...
    assuming lots of modules have been pulled into the kernel

    now the output is

    tosh-sm60<2017-09-27 16:49:42><~>... dmesg |grep ipw
    [ 16.671529] libipw: 802.11 data/management/control stack, git-1.1.13
    [ 16.671532] libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
    [ 17.020084] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kdmprq
    [ 17.020087] ipw2200: Copyright(c) 2003-2006 Intel Corporation
    [ 17.020565] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
    [ 17.255801] ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
    [ 17.263628] ipw2200 0000:06:02.0 wlp6s2: renamed from eth0
    tosh-sm60<2017-09-27 16:50:00><~>...
    so for now on this os the problem appears fixed

    is yours output still the same after todays updates?

    cheers
    ======

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •