Re: kern/59922: iwm0 - Intel Dual Band Wireless AC 8265 (rev. 0x78) - stopped working on NetBSD 11.0_BETA

["Michael van Elst via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR kern/59922; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/59922: iwm0 - Intel Dual Band Wireless AC 8265 (rev. 0x78) - stopped working on NetBSD 11.0_BETA
Date: Wed, 21 Jan 2026 00:17:26 -0000 (UTC)

 gnats-admin%NetBSD.org@localhost ("Bartek Krawczyk via gnats") writes:
 
 > I can now reliably get "ifconfig iwm0 list scan" I think, but I still 
 > get this in dmesg:
 > 
 > iwm0: autoconfiguration error: could not init bt coex (error 35)
 
 That should mean that the firmware isn't answering (probably because
 it halted for some unknown error condition). The error also breaks
 the interface initialization, so it doesn't go into RUNNING state.
 
 
 > Also wpa_supplicant is not able to work with iwm0:
 > 
 > messages:Jan 20 23:14:30 laptop wpa_supplicant[2716]: ioctl[SIOCS80211, 
 > op=23, val=0, arg_len=0]: Invalid argument
 
 That's a scan request that fails because the interface
 isn't UP and RUNNING.
 
 
 You could try to #ifdef out the failing call. It tries to configure
 the chip for Wifi priority over Bluetooth but I doubt that strictly
 necessary for it to function.
 
 E.g.:
 
 --- if_iwm.c    21 Dec 2025 16:24:39 -0000      1.93
 +++ if_iwm.c    21 Jan 2026 00:12:30 -0000
 @@ -7651,12 +7651,14 @@ iwm_init_hw(struct iwm_softc *sc)
                 goto err;
         }
  
 +#if 0
         err = iwm_send_bt_init_conf(sc);
         if (err) {
                 aprint_error_dev(sc->sc_dev,
                     "could not init bt coex (error %d)\n", err);
                 goto err;
         }
 +#endif
  
         if (isset(sc->sc_enabled_capa,
             IWM_UCODE_TLV_CAPA_SOC_LATENCY_SUPPORT)) {