NUC10 AX201 on Ubuntu 18.04

[shigmas]

I know I'm making it even harder by using Ubuntu 18.04, since everything seems fine with 20.04 server. But, I have to deploy with 18.04 because we haven't ported our software yet.

Here's what I've got:

NUC10i5FNH (AX201 160MHz, REV=0x354)

Firmware: FNCML357 (Mar 2021)

Ubuntu 18.04 server

wifi didn't work with linux-generic kernel didn't work, so I went with linux-generic-hwe

But, bluetooth is not usable. bluetoothctl doesn't discover anything nearby (20.04 works fine).

I've pulled the linux-firmware today, since, previously, it looked like it tried to load the firmware starting at 50, and down until 48:

[ 44.887033] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[ 44.889488] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
[ 44.889674] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
[ 44.896433] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17

So, I've updated 48 first, then added the rest of the iwlwifi-QuZ files

Is there a way to get iwlwifi to pull the same ones that 20.04 does, are are there incompatabilities with the kernel?

[Hans_Bausewein]

Hello @shigmas 

You may get a better reply on an Ubuntu forum, but I think you need Ubuntu Backports.

I use Debian and Mint (which is based on Ubuntu), so maybe I miss something.

This is my firmware-iwlwifi from Debian/backports:

ii firmware-iwlwifi 20210315-2~bpo10+1 all Binary firmware for Intel Wireless cards

Note that backports are sometimes a bit late(r) with updates, which is an issue in critical deployments.

Maybe you'll need a newer kernel as well, which may conflict with your 18.04 requirement.

Regards,

Hans

[shigmas]

This didn't seem to get bluetooth better than it was before:

1. backports didn't seem to have firmware-iwlwifi
2. found the package in https://packages.debian.org/sid/all/firmware-iwlwifi/download
3. installed (--force-overwrite): firmware-iwlwifi/now 20210315-2 all [installed,local]

But, even though it wasn't a magic solution, it opened another avenue to find the solution. Thanks.

[Hans_Bausewein]

Good to hear that the Debian firmware-iwlwifi works on your Ubuntu, but you should use the Ubuntu backports instead. Then you'll also get security updates and dependency management.

BUT . . . just checked myself: see below.

To find what USB devices you have, use:

lsusb -v

Bluetooth is probably the USB 8087:0026 device (on my NUC10i3FNK it is).

Check the Ubuntu kernel lifecycle page:
  "Ubuntu 18.04.5 LTS (v5.4)"

Kernel 5.4 should be recent enough for bluetooth.
It's here: https://releases.ubuntu.com/18.04/

For iwlwifi you may need a 5.7 kernel:

    Device 'Intel Comet Lake PCH-LP CNVi WiFi' 

Regards,

Hans

[shigmas]

Sorry. I'm getting back to this after working on something else.

I actually said that it *didn't* work. I'm trying a different approach (and started another thread), since this was a bit more complicated.

[shigmas]

Getting back to this and trying a different approach. I installed 18.04 Desktop and 18.04 Server on two different SSD's (one is NVMe, but if that's important... I will break something). Desktop works, server doesn't (It will detect the blue speaker, but nothing else.) So. it's the same hardware, I'm just switching drives.

On the server, I've had to restart bluetooth because:

Jun 03 05:50:53 machine-name bluetoothd[966]: Failed to set privacy: Rejected (0x0b)'

(I've seen some posts about Privacy=off in bluetooth/main.conf, but right now, desktop and server 

dmesg is the same as far as the bluetooth messages are concerned:

[ 3.104454] Bluetooth: Core ver 2.22
[ 3.104471] NET: Registered protocol family 31
[ 3.104471] Bluetooth: HCI device and connection manager initialized
[ 3.104474] Bluetooth: HCI socket layer initialized
[ 3.104476] Bluetooth: L2CAP socket layer initialized
[ 3.104480] Bluetooth: SCO socket layer initialized
[ 3.106258] Intel(R) Wireless WiFi driver for Linux
[ 3.106260] Copyright(c) 2003- 2015 Intel Corporation
[ 3.106333] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[ 3.111704] usbcore: registered new interface driver btusb
[ 3.112266] Bluetooth: hci0: Firmware revision 0.0 build 62 week 31 2019
[ 3.113761] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2
[ 3.113775] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2
[ 3.115260] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
[ 3.115267] iwlwifi 0000:00:14.3: Found debug destination: EXTERNAL_DRAM
[ 3.115268] iwlwifi 0000:00:14.3: Found debug configuration: 0
[ 3.115753] iwlwifi 0000:00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm

(From previous experimentation, I know it's searching for the iwlwifi-QuZ-a0 files, and finds the right one, which is 48.ucode on the desktop and server.) 

I'm trying to get the server packages to be the same as the desktop (or tweaking the desktop to be like the server). But, these all match.

• linux-firmware: 1.173.20 (desktop was .19, so I updated it)
• bluez: 5.48-0ubuntu3.4
• bluez-cups: 5.48-0ubuntu3.4
• bluez-obexd: 5.48-0ubuntu3.4 (These two packages, I just saw on the desktop, so I installed them on the server, just to eliminate any differences)
• linux-generic-hwe-18.04 5.4.0.74.83~18.04.67

Any ideas what else might be the difference?