MX master 3s will not connect after last update

Our Neighbors Asahi Linux Ask Asahi
1

Anyone else having the same problem?

2

Nope, works fine here.

3

My MX Master 3s works fine here too.

4

Confirmed here. Feels like the previous bluetooth issue and v6.8.9 has a suspicious change which potentially reintroduces the previous issue.

5

Have the same issue with MX Anywhere 2 after last update

6

same here with fresh install on M1 Macbook Pro.

mrinal@lnx]~% uname -a       
Linux lnx 6.8.9-402.asahi.fc40.aarch64+16k #1 SMP PREEMPT_DYNAMIC Wed May  8 18:05:42 UTC 2024 aarch64 GNU/Linux

bluetooth]# show
Controller BC:D0:74:5F:D3:B7 (public)
	Manufacturer: 0x000f (15)
	Version: 0x0b (11)
	Name: lnx
	Alias: lnx
	Class: 0x007c0000 (8126464)
	Powered: yes
	PowerState: on
	Discoverable: yes
	DiscoverableTimeout: 0x000000b4 (180)
	Pairable: yes
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d054B
	Discovering: yes
	Roles: central
	Roles: peripheral
Advertising Features:
	ActiveInstances: 0x00 (0)
	SupportedInstances: 0x08 (8)
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
	SupportedSecondaryChannels: 1M
	SupportedSecondaryChannels: 2M
[bluetooth]# pair EA:F4:05:A4:92:3B 
Attempting to pair with EA:F4:05:A4:92:3B
[bluetooth]# Failed to pair: org.bluez.Error.AuthenticationFailed
7

@jannau downgrading to 6.8.8-400 fixed the issue for me.

8

Booting to the previous kernel fixes the bluetooth problem.
I guess this will be fixed in next kernel update…?

9

Yesterday, my MX Master 3s worked fine with 6.8.9-402.asahi.fc40.
Today, it doesn’t, but installing and choosing 6.8.8-400.asahi.fc40 from grub remedied the issue.

Basically, the same experience as the same bug before (magically worked fine while others had issues, then stopped working after a reboot).

So, I’m just sticking with booting 6.8.8-400.asahi.fc40 for now. The only weird thing about 6.8.8-400.asahi.fc40 is that I randomly get a kernel panic right near the end of system initialization on my M1 Ultra Mac Studio, but after a reboot (or two) it boots fine and works fine (it’s a minor nuisance only since I rarely reboot). I don’t have that issue with 6.8.9-402.asahi.fc40, so I’m not sure if the two are related.

1 Like
10

This is fixed in kernel-16k-6.8.9-403.asahi. See Fedora Asahi Remix 40 is now available - #6 by jannau

2 Likes
11

Just updated - works great - thanks!