Upgrade to Fedora 35

Doug Hutcheson · 11-08-2021, 09:01 PM

After upgrading to 35, I had to 'Remove Device' for my MS Designer BT mouse and re-pair it before it would work. Now my MS Designer BT keyboard is not working and 'Remove Device' followed by re-pair is not working. The keyboard is visible in the list of devices, but keystrokes are not being processed, so I cannot confirm the pairing.

The keyboard pairs easily with my Android tablet, so the keyboard is not at fault.

F35 also broke my sound system and none of the fixes I could find worked, so I disabled WirePlumber and successfully reverted to pulseaudio.

Any suggestions as to how to fix these problems would be appreciated.

Brains · 11-09-2021, 02:45 AM

So...
You've been a Red Hat designer since Fedora 30.
Sounds like you're a little frustrated with bleeding edge technology, not installing/running smooth like a stable distribution.
You may want to Google up "bluetoothctl" and try linking from command, you'll likely get more insight on what's going wrong this way.
Also, kernel configs can be tricky in the BT arena, some drivers need to be modules, not built in, and tricky as in having one off can result in this behavior.

I know from experience from when I first started designing my own kernel which combination got things working properly to this day with 5.14.15 kernel:

Quote:

CONFIG_BT=m
CONFIG_BT_BREDR=y
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=m
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=m
CONFIG_RFKILL=m
CONFIG_CRYPTO_USER=m
CONFIG_CRYPTO_USER_API=y
CONFIG_CRYPTO_USER_API_HASH=y
CONFIG_CRYPTO_USER_API_AEAD=m
CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE=y

Doug Hutcheson · 11-11-2021, 07:58 PM

Quote:

Originally Posted by Brains

You've been a Red Hat designer since Fedora 30.

Erm .. I am not a Red Hat designer, but I've been using Red Hat/Fedora since the late 90s. My knowledge of BlueTooth is almost but not quite limited to how to spell the name. Thank you very much for the pointer to bluetoothctl - ill give that a whirl.

Doug Hutcheson · 11-11-2021, 08:24 PM

Quote:

Originally Posted by Brains

"bluetoothctl"

I did that, but the result is still failure. Attempts to pair the keyboard present the six digit code to key in, but these keystrokes are not being recognised.

I know the keyboard is working because it pairs easily with my tablet. The matching Bluetooth mouse from this set is working perfectly.

Here is my attempt to connect using bluetoothctl:

Code:

[doug@womble ~]$ bluetoothctl
Agent registered
[CHG] Controller 00:1A:7D:DA:71:15 Pairable: yes
[Designer Mouse]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:15 Discovering: yes
[NEW] Device D5:75:9D:C4:D7:38 Designer Keyboard
[Designer Mouse]# pair D5:75:9D:C4:D7:38
Attempting to pair with D5:75:9D:C4:D7:38
[CHG] Device D5:75:9D:C4:D7:38 Connected: yes
[agent] Passkey: 827185
[NEW] Primary Service (Handle 0x09bd)
	/org/bluez/hci0/dev_D5_75_9D_C4_D7_38/service0008
	00001801-0000-1000-8000-00805f9b34fb
	Generic Attribute Profile
[NEW] Characteristic (Handle 0x4f94)
	/org/bluez/hci0/dev_D5_75_9D_C4_D7_38/service0008/char0009
	00002a05-0000-1000-8000-00805f9b34fb
	Service Changed
[NEW] Descriptor (Handle 0x8ba4)
	/org/bluez/hci0/dev_D5_75_9D_C4_D7_38/service0008/char0009/desc000b
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[NEW] Primary Service (Handle 0x09bd)
	/org/bluez/hci0/dev_D5_75_9D_C4_D7_38/service000c
	0000180a-0000-1000-8000-00805f9b34fb
	Device Information
[NEW] Characteristic (Handle 0x99b4)
	/org/bluez/hci0/dev_D5_75_9D_C4_D7_38/service000c/char000d
	00002a29-0000-1000-8000-00805f9b34fb
	Manufacturer Name String
[NEW] Characteristic (Handle 0x7994)
	/org/bluez/hci0/dev_D5_75_9D_C4_D7_38/service000c/char000f
	00002a50-0000-1000-8000-00805f9b34fb
	PnP ID
[NEW] Primary Service (Handle 0x09bd)
	/org/bluez/hci0/dev_D5_75_9D_C4_D7_38/service0011
	0000180f-0000-1000-8000-00805f9b34fb
	Battery Service
[NEW] Characteristic (Handle 0xb054)
	/org/bluez/hci0/dev_D5_75_9D_C4_D7_38/service0011/char0012
	00002a19-0000-1000-8000-00805f9b34fb
	Battery Level
[NEW] Descriptor (Handle 0xbcd4)
	/org/bluez/hci0/dev_D5_75_9D_C4_D7_38/service0011/char0012/desc0014
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[CHG] Device D5:75:9D:C4:D7:38 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device D5:75:9D:C4:D7:38 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device D5:75:9D:C4:D7:38 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device D5:75:9D:C4:D7:38 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device D5:75:9D:C4:D7:38 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[CHG] Device D5:75:9D:C4:D7:38 ServicesResolved: yes
[CHG] Device D5:75:9D:C4:D7:38 ServicesResolved: no
[CHG] Device D5:75:9D:C4:D7:38 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
[CHG] Device D5:75:9D:C4:D7:38 WakeAllowed: yes
[Designer Mouse]# pair D5:75:9D:C4:D7:38
Attempting to pair with D5:75:9D:C4:D7:38
[CHG] Device D5:75:9D:C4:D7:38 Connected: yes
[agent] Passkey: 511889
[CHG] Device D5:75:9D:C4:D7:38 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
[Designer Mouse]#

Brains · 11-22-2021, 12:41 AM

To be a Red Hat developer:
Just use CentOS or Fedora. The OS takes care of the diags and reporting etc.

Quote:

[NEW] Device D5:75:9D:C4

7:38 Designer Keyboard
[Designer Mouse]# pair D5:75:9D:C4

7:38

The quote above is confusing, I'm guessing that address belongs to the keyboard only but why is the mouse trying to pair with it?
At least... that's what that looks like. What about pairing the keyboard without the mouse, turn it off.

Brains · 11-22-2021, 12:53 AM

Fedora used to be Red Hat's flagship but now it's CentOS but Fedora still tied somehow.
Maybe there's too many desktop users in the Fedora user count, not the type of users they need for the software they focus on developing for the Red Hat OS, it's not designed for desktop use.