On Tue, 18 Feb 2025, Bjoern A. Zeeb wrote: Update on HW Crypto testing after 9 days (I know it was not that long in stable/14).
Thank you to everyone who replied so far. Really much appreciated. I hope I didn't miss any results when I just went through my inbox again to collect them for the email. * Summary: I wanted to turn HW_CRYPTO on by default but both the little feedback, as well as the rtw89 issues I encountered, plus the possible iwlwifi issue on 9xxx made me not do that (yet). As expected the modern iwlwifi chipset (AX2xx) results seem fine. If you will do further testing and have an AX2xx device, please report any issues. I am very happy that the one rtw88 feeback also was fine. I want people to understand that if they want HT/VHT support to work (later) on their device by default with the LinuxKPI based drivers we need to make sure hw crypto works without trouble first (for everyone/all the LinuxKPI based drivers -- or at least for most and then we flip the defualt to disable for those it doesn't work or the once which did not get testing). I've 5 iwlwifi chipsets (w/o duplicates) to test with, 3 rtw88, and 2 rtw89 currently. That is more together than I got answers but I am limited to my setup(s) against I develop and which only represent a tinsy fraction of the world out there. I am well aware that the "please turn it on and test this" wasn't the best question either -- and feedback early on showed that. So let me ask a few more questions: * Question to those who would test but didn't or would love to have it more organized: - would you test if you had a memstick image to boot from for testing, maybe setup your wpa_supplicant.conf and then email results, unplug and boot back (ignore if the memstick was main or stable)? - would you test if you got something similar with a bhyve image with instructions to setup passthru temporary for your wifi? - how much time would you want/need to be able to test? - would it help if there was a scripted way of setting up tests or gathering test results (or at least a defined way of -- check X)? - anything else which would help you to test? * Here's what I got (so far): (1) 2x People had TKIP issues; both solved by turning TKIP off on the AP (2) iwlwifi feedback: ---------------------------------------- * [] OK * vendor=0x8086 device=0x2725 subvendor=0x8086 subdevice=0x0020 [] OK * vendor=0x8086 device=0x51f1 subvendor=0x8086 subdevice=0x0090 [] OK * [Intel(R) Wi-Fi 6 AX201 160MHz, iwlwifi-QuZ-a0-hr-b0-77.ucode] OK (if TKIP disabled) * vendor=0x8086 device=0x02f0 subvendor=0x8086 subdevice=0x0070 [Intel(R) Wi-Fi 6 AX201 160MHz, iwlwifi-QuZ-a0-hr-b0-77.ucode] OK (if TKIP disabled) * vendor=0x8086 device=0x31dc subvendor=0x8086 subdevice=0x0264 [Intel(R) Wireless-AC 9461, iwlwifi-9000-pu-b0-jf-b0-46.ucode] 14.2 cherry-picked, Problems (3) rtw88 feedback: ---------------------------------------- * [] OK (4) rtw89 (my own testing): ---------------------------------------- * vendor=0x10ec device=0xc822 subvendor=0x1a3b subdevice=0x3750 [8852AE, rtw89/rtw8852a_fw.bin 0.13.36.0 (c33d3f88)] Problems, 'FW crash' More tomorrow, Bjoern -- Bjoern A. Zeeb r15:7
