linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nigel Sollars <nsollars@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Fwd: Delivery Status Notification (Failure)
Date: Thu, 8 Aug 2019 15:58:03 -0400	[thread overview]
Message-ID: <CAG6aBkXG50t-KgkLPpkGjcF313hJiic6k1sqOVDCbWN3zPAsGg@mail.gmail.com> (raw)
In-Reply-To: <5d4c34ea.1c69fb81.a7a36.5f7f.GMR@mx.google.com>

Hi,

So I have been trying to reach out in aim to get this driver fixed as
its regressed now to a total non working state.

The card can see access points, but thats about as good as it gets as
trying to connect to any networks ( either 2.4 ot 5 Ghz ) results in
the following,

  wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1

( alot of these ) which then resets connection status with a failed timeout.

I am currently running FedoraCore 30 with the 5.2.5-200 kernel updated
from 5.1.x yesterday. The firmware loaded is,

loaded firmware version 9.221.4.1 build 25532 op_mode iwldvm

Now with all that said, using a Linux Mint live boot from a usb device
yeilds the card working fine at both 2.4 and 5ghz speeds, it connects
within seconds. The kernal in this live boot is 4.15.x and uses the
same firmware build as my FC install.

I did see strange behavior with this card from around 4.18 to 20,
thinking the card might have developed a fault and obtained a new one.
This proved that this was not the case as I get the exact same
behavior from both cards.

Hope this information is helpful to solve quickly, please reach out
for more information if required

Thanks
Nige

-- 
“Science is a differential equation. Religion is a boundary condition.”

                           Alan Turing

       reply	other threads:[~2019-08-08 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAG6aBkWDyGDtWX7X0t-FjynkYxpdhpZsAv4Ysw3dKf+iEu+mig@mail.gmail.com>
     [not found] ` <5d4c34ea.1c69fb81.a7a36.5f7f.GMR@mx.google.com>
2019-08-08 19:58   ` Nigel Sollars [this message]
     [not found] ` <941b807b02962fadaf738942baf1621738872723.camel@intel.com>
2019-08-21 14:30   ` [linuxwifi] Intel Centrino Ultimate N 6300 regression Nigel Sollars
2019-08-21 21:45     ` Alexander Wetzel
2019-08-22  0:12       ` Nigel Sollars
2019-08-22 22:42     ` Antanas Uršulis
     [not found] <CAC+NB+MuEPfbgt8fLWvk_oUZFyX4o=mbPY_cOeQs13kqgO0VFg@mail.gmail.com>
     [not found] ` <047d7b3a89462f279c04f170647e@google.com>
     [not found]   ` <CAC+NB+NcYvmTRht1Go4Dar_Jg2CYTa=GQ4E6YxpBeu8MM=zCAg@mail.gmail.com>
2014-02-25  9:45     ` Fwd: Delivery Status Notification (Failure) Jakub Józefowicz

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=CAG6aBkXG50t-KgkLPpkGjcF313hJiic6k1sqOVDCbWN3zPAsGg@mail.gmail.com \
    --to=nsollars@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).