linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nigel Sollars <nsollars@gmail.com>
To: Alexander Wetzel <alexander@wetzel-home.de>
Cc: Luciano Coelho <luciano.coelho@intel.com>,
	linuxwifi@intel.com, linux-wireless@vger.kernel.org
Subject: Re: [linuxwifi] Intel Centrino Ultimate N 6300 regression
Date: Wed, 21 Aug 2019 20:12:16 -0400	[thread overview]
Message-ID: <CAG6aBkV_6_ipe3AXJkknidLP+8_40kObfBE5Tfz4vS=2-GGZww@mail.gmail.com> (raw)
In-Reply-To: <4e63174a-34cc-cebf-4eb9-205f0d237574@wetzel-home.de>

Interesting to be sure,  so here are the versions of kernel and wpa_supplicant,

5.2.9-200.fc30.x86_64
wpa_supplicant-2.8-2.fc30.x86_64


On Wed, Aug 21, 2019 at 5:45 PM Alexander Wetzel
<alexander@wetzel-home.de> wrote:
>
> >> 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'm also using a "Intel Corporation Centrino Ultimate-N 6300 (rev 3e)"
> card and it's working perfectly with 5.3.0-rc4-wt here.
> (And with most wireless-testing kernels for the last years, too..)
>
> Now there was one noteworthy bug in the last year we handled on the
> mailing list:
> https://lore.kernel.org/linux-wireless/87k1rk1af5.fsf@kamboji.qca.qualcomm.com/
>
> But then this was a null pointer and does not match to what you observe.
> (And that really should be fixed in any 5.2 kernel...)
>
> I'm using a Gentoo ~amd64 system and wpa_supplicant more or less
> tracking git upstream and the wireless-testing kernels with the same
> firmware as you.
>
> So whatever it is, it's not affecting me. I would suggest to try a
> vanilla 5.2 kernel and maybe also an updated wpa_supplicant version next...
>
> Alexander



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

                           Alan Turing

  reply	other threads:[~2019-08-22  0:12 UTC|newest]

Thread overview: 5+ 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   ` Fwd: Delivery Status Notification (Failure) Nigel Sollars
     [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 [this message]
2019-08-22 22:42     ` Antanas Uršulis

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='CAG6aBkV_6_ipe3AXJkknidLP+8_40kObfBE5Tfz4vS=2-GGZww@mail.gmail.com' \
    --to=nsollars@gmail.com \
    --cc=alexander@wetzel-home.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxwifi@intel.com \
    --cc=luciano.coelho@intel.com \
    /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).