Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 29 Nov 2022 18:46:50 +0100
From:   Stanislaw Gruszka <stf_xl@wp.pl>
To:     Ioannis Barkas <jnyb.de@gmail.com>
Cc:     linux-wireless@vger.kernel.org
Subject: Re: PRO/Wireless 4965 Intel WPA2,3 SSID connection problem #1
Message-ID: <20221129174650.GA620872@wp.pl>
References: <CADUzMVb6QKX-dhVpFXvUJ2MXMf93vK1RC+R8JqAPxExBSisA0A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADUzMVb6QKX-dhVpFXvUJ2MXMf93vK1RC+R8JqAPxExBSisA0A@mail.gmail.com>
Precedence: bulk

Hi Ioannis

On Tue, Nov 29, 2022 at 12:34:38AM +0200, Ioannis Barkas wrote:
> I have figured everything out with MX Linux and created a new kernel
> based on 6.0 that it works well on my test PC as well. Then I applied
> your patch along with some debugging options. Unfortunately the
> problem remains and it continues to be unable to connect at the
> desired WPA2,3 based network.

Regarding patch, it was for UBSAN error, but looking at your other emails,
the problem you have is more general. I think you should try swcrypto=1
module option.

Regards
Stanislaw