From: Blue Glacier <blueglacier414@gmail.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: "No association and the time event is over already..."
Date: Sun, 21 Jun 2015 00:27:58 +0200 [thread overview]
Message-ID: <5585E8EE.2000005@gmail.com> (raw)
In-Reply-To: <CANUX_P0DYFVqxVHg6B8ZXLiLv97Gu8JuiXcUEA8rvPMW8+Jb2Q@mail.gmail.com>
Hello,
yes, already tried to disable and re-enable WiFi. Didn't help.
I guess AP means Access Point. It is a "FRITZ!Box 6360 Cable (um)". I
tried to reboot it. 15 minutes later it suddenly worked - but only for
two hours. Now the connection is broken again.
While ping times out, I sometimes seem to be able to load websites - but
it takes almost 10 minutes and many elements are missing. I am also
repeatedly asked for my WiFi-password, which worked until yesterday.
I compared the md5 hash sums of the driver image (iwlwifi-7265-9.ucode)
that I have installed and the one that is available through the link you
gave me, and the sums are equal. Therefore, I think it doesn't make
sense to try the other image.
I don't know if it is a good idea to install a different kernel on
Debian Stable.
Jens
Am 20.06.2015 um 22:01 schrieb Emmanuel Grumbach:
> On Sat, Jun 20, 2015 at 9:33 PM, Blue Glacier <blueglacier414@gmail.com> wrote:
>> Hello,
>>
>> my Intel Wireless 7265 chip suddenly stopped working. The Network Manager
>> shows that I am connected, but I cannot even ping to my home router. I
>> didn't change anything on my system.
> What is your AP? Can you reproduce consistently? If you disable WiFi
> and re-enable WiFi from the Network Manager, does it help?
>
>> The output of dmesg looks interesting:
>>
>> [ 507.737606] wlan0: Connection to AP c0:25:06:ce:d2:e9 lost
>> [ 507.806070] cfg80211: Calling CRDA for country: DE
>> [ 508.379770] cfg80211: Calling CRDA for country: DE
>> [ 511.332818] wlan0: authenticate with c0:25:06:ce:d2:e9
>> [ 511.338625] wlan0: send auth to c0:25:06:ce:d2:e9 (try 1/3)
>> [ 511.341600] wlan0: authenticated
>> [ 511.343813] wlan0: associate with c0:25:06:ce:d2:e9 (try 1/3)
>> [ 511.350128] wlan0: RX AssocResp from c0:25:06:ce:d2:e9 (capab=0x431
>> status=0 aid=8)
>> [ 511.353700] wlan0: associated
>> [ 511.645582] iwlwifi 0000:03:00.0: No association and the time event is
>> over already...
>> [ 511.645642] wlan0: Connection to AP c0:25:06:ce:d2:e9 lost
>> [ 511.688174] cfg80211: Calling CRDA to update world regulatory domain
>>
>> (repeated numerous times)
>>
>> I am using Debian 8 Jessie (stable) together with the firmware from your
>> server (iwlwifi-7265-9.ucode). The Kernel Version is 3.16.0-4-amd64.
> Can you try a more recent kernel with a more recent firmware?
> You can check https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release
> if you want to update your driver without changing your kernel.
>
>> Any idea how to fix this?
>
>> Jens
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
next prev parent reply other threads:[~2015-06-20 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 18:33 "No association and the time event is over already..." Blue Glacier
2015-06-20 20:01 ` Emmanuel Grumbach
2015-06-20 22:27 ` Blue Glacier [this message]
2015-06-21 6:22 ` Emmanuel Grumbach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5585E8EE.2000005@gmail.com \
--to=blueglacier414@gmail.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).