Bug 209641 - Intel AX201 WiFi card cannot be restarted on boot when held by Windows 10
Summary: Intel AX201 WiFi card cannot be restarted on boot when held by Windows 10
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless-intel (show other bugs)
Hardware: Intel Linux
: P1 high
Assignee: Default virtual assignee for network-wireless-intel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-13 04:51 UTC by siegfred
Modified: 2025-03-03 16:04 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.4.0-48-generic
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description siegfred 2020-10-13 04:51:10 UTC
I have a dual boot laptop with Windows 10 and Linux Mint 20 on separated NVME m.2 and utilizing an Intel AX201 WiFi card, a curious behaviour is that if Windows 10 is using FastBoot (which obviously holds on to some resources during shutdown) causes the next Linux boot's iwlwifi module to fail, error code -110.

As far what i can understand is that Windows seems to leave PCI in bad state during FastBoot shutdowns.

I still could not figure out as to why the corresponding Linux driver still cannot automatically acknowledge that and automatically do a PCI reset or any appropriate operation so as to clear out the bad state.

Known work around/s :

From Windows:
- Disable power management shutdown for the wifi Card (Which is no longer available or ridiculously difficult because windows).

- Disable FastBoot, which is a shame.

From Linux POV:

- Reboot linux after the first boot right after the last Windows 10 boot.

- Modifying iwlwifi conf to reset PCI, as stated in comment 55 in Bug 201319.

consequences is that we could no longer dual out of the box without fiddling around.
Comment 1 Joseph Whittaker 2025-03-03 16:04:32 UTC
For future reference, I've fixed issue by disabling Intel AMT if it is an option in your BIOS. On the Latitude 7320, it was on when I received it but luckily never configured so I was able to use the default password (admin), and set a new one to disable it.

Note You need to log in before you can comment on or make changes to this bug.