Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CAG6aBkWDyGDtWX7X0t-FjynkYxpdhpZsAv4Ysw3dKf+iEu+mig@mail.gmail.com>
 <941b807b02962fadaf738942baf1621738872723.camel@intel.com>
In-Reply-To: <941b807b02962fadaf738942baf1621738872723.camel@intel.com>
From:   Nigel Sollars <nsollars@gmail.com>
Date:   Wed, 21 Aug 2019 10:30:50 -0400
Message-ID: <CAG6aBkW09YFz4asHZkhWBUenBiT3dgb7iGXBCq8KkCM09QXjLg@mail.gmail.com>
Subject: Re: [linuxwifi] Intel Centrino Ultimate N 6300 regression
To:     Luciano Coelho <luciano.coelho@intel.com>
Cc:     linuxwifi@intel.com, linux-wireless@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

Thanks for the feedback I will look into this and report my findings,
to answer your question, yes I can build a kernel to do this testing.

I will also update my Redhat Bug Ticket with this information also

Regards
Nigel Sollars

On Wed, Aug 21, 2019 at 2:08 AM Luciano Coelho <luciano.coelho@intel.com> w=
rote:
>
> Hi Nigel,
>
> Unfortunately we don't actively support these old devices anymore, though=
 we try to help as much as we can.
>
> This error is -EINVAL, which means that the driver is not recognizing a p=
arameter passed to it. It's hard to tell exactly what is causing that witho=
ut further investigation. Are you able to compile the kernel and do some te=
sts? One way you could do it is to replace the -EINVAL with a line number, =
so we can try to see where the invalid parameter error is coming from. Doin=
g something like this: http://pastebin.coelho.fi/03fa29d951db5405.txt
>
> Then the returned error should correspond to a line number on the driver.
>
> Another thing you could try is to bisect the kernel between the last know=
n good version and the one that fails. To do that you should try to find a =
newer kernel than 4.15 that works, preferrably as close to 5.1 as possible.
>
> HTH.
>
> --
> Cheers,
> Luca.
>
>
> On Thu, 2019-08-08 at 10:42 -0400, Nigel Sollars wrote:
>
> 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 try=
ing to connect to any networks ( either 2.4 ot 5 Ghz ) results in the follo=
wing,
>
>   wlp3s0: CTRL-EVENT-SCAN-FAILED ret=3D-22 retry=3D1
>
> ( alot of these ) which then resets connection status with a failed timeo=
ut.
>
> I am currently running FedoraCore 30 with the 5.2.5-200 kernel updated fr=
om 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 ye=
ilds 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, thinkin=
g 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 card=
s.
>
> Hope this information is helpful to solve quickly, please reach out for m=
ore information if required
>
> Thanks
> Nige
>


--=20
=E2=80=9CScience is a differential equation. Religion is a boundary conditi=
on.=E2=80=9D

                           Alan Turing