Link Copied
Bobsen, Thank you for posting in the Intel® Communities Support.
In reference to this scenario, just to let you know, the supported and validated operating system that was tested by Intel® with the Intel® NUC NUC10i5FNH is Windows* 10 and the drivers that we have available are only for that OS as you can confirm in the following links:
https://www.intel.com/content/www/us/en/support/articles/000005628/intel-nuc.html
https://downloadcenter.intel.com/product/189239/Intel-NUC-10-Performance-kit-NUC10i5FNH
Now, in order to try to further assist you with this matter, please follow the steps requested below:
What is the model of the Router?
Is this a new Intel® NUC?
Was it working fine before?
When did the issue start?
Did you make any recent hardware/software changes?
The wireless card, did you purchased it separately or did it came installed on the Intel® NUC?
WiFi troubleshooting steps
Step 1: Check whether the kernel version customer uses supports this device:
The reference table of Wireless adapters and corresponding kernel versions is available by the link: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
The latest FWs are available by the following link: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
If the kernel version corresponds to the Wireless adapter, proceed with step 2.
Step 2: Check whether the Wireless adapter is connected correctly:
Type the following command to the terminal: # lspci
Verify that the Intel network controller is identified, as on a picture below. If not, then the system doesn't identify the Intel network adapter and you will need to make sure it's properly integrated. You may need to request help from the system manufacturer. If the wireless adapter is properly identified - proceed with the step 3.
Step 3: Check whether this is an iwlwifi issue:
Type the following command to the terminal: # modinfo iwlwifi (example of the command output is on the picture below). If there is no output, then the module isn’t installed this is the distribution installation issue.
Please type: # lsmod | grep iwlwifi
If the result is empty, the driver hasn't been loaded. Most likely to be a distribution issue.
To verify, please type: # dmesg | grep iwlwifi
If the result is empty, the driver wasn’t initialized and this is a distribution issue. If the result is populated as on the above picture, proceeed with the step 4.
Step 4: Check whether the suitable firmware is installed:
Please type: # dmesg | grep “no suitable firmware found!”
If the result is not empty, it means you don't have a suitable FW (api mentioned in the dmesg).
Please visit here https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi for supported FW, or here https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ for the latest versions.
If these steps didn't reveal the issue or didn't solve the problem, proceed with the Step 5:
Step 5: Collect the debug data:
Please type: # dmesg | grep ASSERT
If the output is empty, please follow this wiki: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging to extract dmesg and trace-cmd.
If the output has value, please collect from the wiki FW dump too.
Any questions, please let me know.
Regards,
Albert R.
Intel Customer Support Technician
Thanks Alberto,
here are the logs where you can see which firmware is loaded. In my case it seems to fit for the integrated AX201. It is a stock NUC, maybe 5 months old. The device is regularly updated (daily/every other day).
Although there is a note that the api flags index 2 is larger than supported by driver it seems to me I'm using the latest available firmware. I guess the driver has to be updated accordingly at some point.
Here are two logs of the same disconnect.
Any other hints are welcome.
Regards,
Mike
Here is a journal log of a disconnect in more detail (debugging enabled in bluetoothd):
There's a plain and simple disconnect with "reason 1". According to the sourcecode this translates to a connection timeout. Since this doesn't give us any more hints I guess I'll have to debug the kernel next? I'll see what I can do.
Regards,
Bobsen
Alberto,
you're selling those NUCs without HD. If I wanted one with Windows I'd have bought a box with HD and OEM license. So no, not an option.
But I was finally able to fix the issue through downgrading the firmware to the december release (FW Build: REL17535, Release Version: 22.20.0.3) Two evenings in a row without interrupting audio...
Since the only thing I did was removing the Intel folder from /lib/firmware and copying the older firmware manually into place - it is at least obvious to me that changes after that release lead to random connection timeouts. Please have your colleagues look into this. I mean you're only providing binary blobs and no changelog at all. Do the kernel devs at least get more information?
It is not only me having similar problems https://bbs.archlinux.org/viewtopic.php?id=263040&p=3 - it's all different hardware with the same wireless chipset. I hope you agree that downgrading firmware can only be a temporary "solution".
Regards,
Bobsen
