Just to confirm, if I use my early-boot hook that I used for your iw list to set the regulatory domain manually (iw reg set GB) all is well. If I allow the driver stack to get to the association stage without setting a regulatory domain, I can never get my 802.11A spectrum back after the fact. Would you still see this as a bug or rather a specific requirement of the new interface that hasn't yet been documented? Regards, Tony V.
Attachment:
signature.asc
Description: This is a digitally signed message part
