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 <[email protected]> wrote: > > 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 > parameter passed to it. It's hard to tell exactly what is causing that > without further investigation. Are you able to compile the kernel and do some > tests? 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. Doing > 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 known > 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 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
