Should I update my Wi-Fi radio module, please?
Framework 13, 13th gen. Intel, everything works except a new (no-name) Bluetooth 5.2 mouse.
(picture enclosed) http://savvyj.co.uk/WiFi.jpg
The new ones in Marketplace list Bluetooth 5.2, but I don’t know the specs of my current one.
Can anyone advise, please?
So, the AX210 specs are a bit confusing. Intel website says bluetooth 5.3, but this PDF with your serial number (AX210NGW) says 5.2. Maybe it has received 5.3 capabilities since it was originally designed and they made a revision change, or maybe it was compatible with 5.3 when it got out so they updated the number on their page. Anyways, I would trust the specsheet PDF more than intel website lol.
If your no name mouse doesn’t work, be sure that drivers for it are installed: pull up driver boster if you are on windows, or make sure your kernel and system is up to date on linux. I’d like to know the result of these commands and these details :
dmesg
uname -r
Your intel chip seems fine, compatibility for the AX210 and AX200 with linux has been there for many years now, they are the adpaters that perform very well and are very well supoprted on linux so I’ll advise you to not change it unless it has an obvious problem. I think the problem is with the noname mouse. A lot of noname mouses requre a bluetooth usb dongle to work, even if you have a bluetooth chip like the AX210, as it is a specialized range for lower-latency and better mouse battery life. Verify if that is the case.
I should have said I’m only thinking of using the latest module supplied by Framework, if it updates my original module–Framework have clearly done a lot of work making sure things are compatible 
The details on the original module are slightly different from those on the one shown in Marketplace, but I don’t know whether they mean any change in function.
Thanks for the reply–I’ll get those details during my lunch break.
Ubuntu 22.04 LTS with xfce4 desktop.
My previous no-name mouse (“M103” dual dongle/BT) mouse shows in Blueman Applet as “BT5.1 Mouse”, while the new no-name mouse doesn’t show in Blueman at all–it will pair with my phone, though.
uname -r
6.5.0-41-generic
There isn’t room for the whole output of dmesg, so I ran sudo dmesg | grep -i “blue”
[ 7.569104] Bluetooth: Core ver 2.22
[ 7.569135] NET: Registered PF_BLUETOOTH protocol family
[ 7.569137] Bluetooth: HCI device and connection manager initialized
[ 7.569143] Bluetooth: HCI socket layer initialized
[ 7.569145] Bluetooth: L2CAP socket layer initialized
[ 7.569148] Bluetooth: SCO socket layer initialized
[ 7.661347] Bluetooth: hci0: Device revision is 0
[ 7.661351] Bluetooth: hci0: Secure boot is enabled
[ 7.661352] Bluetooth: hci0: OTP lock is enabled
[ 7.661353] Bluetooth: hci0: API lock is enabled
[ 7.661353] Bluetooth: hci0: Debug lock is disabled
[ 7.661354] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 7.661356] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[ 7.692211] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
[ 7.692234] Bluetooth: hci0: Boot Address: 0x100800
[ 7.692235] Bluetooth: hci0: Firmware Version: 132-5.22
[ 9.142864] Bluetooth: hci0: Waiting for firmware download to complete
[ 9.144353] Bluetooth: hci0: Firmware loaded in 1418103 usecs
[ 9.144451] Bluetooth: hci0: Waiting for device to boot
[ 9.171455] Bluetooth: hci0: Device booted in 26421 usecs
[ 9.171478] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 9.186495] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0041-0041.ddc
[ 9.188498] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 9.191641] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build 38020
[ 9.503908] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 9.503913] Bluetooth: BNEP filters: protocol multicast
[ 9.503917] Bluetooth: BNEP socket layer initialized
[ 9.505794] Bluetooth: MGMT ver 1.22
[ 10.012779] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[ 16.109201] hid-generic 0005:32C2:6621.0004: input,hidraw3: BLUETOOTH HID v0.01 Mouse [BT5.1 Mouse] on b0:dc:ef:b2:a5:42
[ 32.638690] Bluetooth: RFCOMM TTY layer initialized
[ 32.638705] Bluetooth: RFCOMM socket layer initialized
[ 32.638717] Bluetooth: RFCOMM ver 1.11
Roops
Nah don’t worry they don’t change anything as long it’s also named AX210NGW.
Hmmm, that’s weird, so it’s really connected via bluetooth. Therefore it’s the linux driver for the mouse or the mouse that has a bluetooth band that the AX210 doesn’t have.
That’s a regular problem on AX200 and AX210, have seen that before. Probably not the cause of the error here.
I remember this being problematic before on some intel AX200, try to forget every bluetooth peripheral you have currently coupled to your device, reboot, then try again.
Otherwise, I’ve seen a lot of people report drivers problems with ubuntu 22.04: the kernel starts to be old and to miss drivers for new peripherals, see Search results for 'driver 22.04 order:latest' - Framework Community.
Try updating to the 24.02 if it doesn’t break your workflow… or choose a distribution with an up to date kernel to test it with, for example a live fedora image, to test the mouse on. If it works then definitely update to something more recent.