On Wed, Nov 7, 2018 at 7:36 AM Petri Lehtinen <petri@xxxxxxxxx> wrote: > > Loading iwlwifi produces the following messages to dmesg. Trying to > bring the wifi interface up also fails. > > [Tue Oct 23 07:17:12 2018] iwlwifi 0000:3a:00.0: loaded firmware version 36.7596afd4.0 op_mode iwlmvm > [Tue Oct 23 07:17:12 2018] iwlwifi 0000:3a:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 > [Tue Oct 23 07:17:13 2018] iwlwifi 0000:3a:00.0: SecBoot CPU1 Status: 0x3040001, CPU2 Status: 0x0 > [Tue Oct 23 07:17:13 2018] iwlwifi 0000:3a:00.0: Failed to start INIT ucode: -110 > [Tue Oct 23 07:17:13 2018] iwlwifi 0000:3a:00.0: Failed to run INIT ucode: -110 > > I'm on Arch Linux, and linux-firmware is built from commit d877533. > With older firmware (commit f1b95fe), it works with this in dmesg > output: > > [Tue Oct 23 07:28:51 2018] iwlwifi 0000:3a:00.0: enabling device (0000 -> 0002) > [Tue Oct 23 07:28:51 2018] iwlwifi 0000:3a:00.0: loaded firmware version 36.e91976c0.0 op_mode iwlmvm > [Tue Oct 23 07:28:51 2018] iwlwifi 0000:3a:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 > [Tue Oct 23 07:28:51 2018] iwlwifi 0000:3a:00.0: base HW address: 00:28:f8:87:a2:e9 > I checked the diff between e91976c0 and 7596afd4 and it is very very small. Is your machine dual boot? A few users have reported a race between BT firmware load and Wifi firmware load. They also reported that booting in Windows, and then shutting down in Windows helps to boot Linux properly. If the above is not applicable, please open a bug in bugzilla.kernel.org and add linuxwifi@xxxxxxxxx to the bug. Thank you.
