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: Thu, 15 Jan 2026 10:07:28 -0000 (UTC)

 gnats-admin%NetBSD.org@localhost ("bartek.krawczyk%gmail.com@localhost via gnats") writes:
 
 >[     4.271387] iwm0: hw rev 0x230, fw ver 22.361476.0, address 40:74:e0:51:38:58
 >[    19.361390] iwm0: autoconfiguration error: could not init bt coex (error 35)
 
 >laptop# ifconfig iwm0
 >iwm0: flags=0x8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500
 >        ssid "" nwkey 65536:"","","",""
 >        powersave off
 >        address: 40:74:e0:51:38:58
 >        media: IEEE802.11 autoselect
 >        status: no network
 
 
 There is hardly any difference between netbsd-10 and netbsd-11
 regarding the iwm driver and it is known to be pretty flaky.
 
 One possible difference is the interaction with dhcpcd. It's
 possible that without dhcpcd the interface associates to the network,
 and when you start dhcpcd aftwards, that it appears to function.
 At least that's one of the failure modes I've seen.
 
 In netbsd-current I have tried to fix iwm and it now seems to be
 stable for me and some others.
 
 You could try to boot a current kernel from the daily build
 (you may need to also install the modules set from current).
 
 Or if you are experienced, you could build a netbsd-11 kernel with
 the updated driver from netbsd-current.