Also, just try booting using linux 6.0 to see if that fixes anything. That still seems to available, so if you uninstalled it, it can be reinstalled.
That is great advice, but before starting the thread I had already tried booting 5.10, 5.19, 6.0, and 6.1 to no avail. I was running 6.0.0-4-amd64 both before and after the device failed. I did upgrade to 6.0.0-6-amd64 the day after. Didn't upgrade to 6.1 until 2023-01-21. BTW, this is what the logs contained when the device was last successfully started. (It is indeed the bluetooth chip; no idea why it's not a PCI device.) 2023-01-04T23:44:08.519572-08:00 cockpit kernel: [ 3.927596] usb 1-5: new high-speed USB device number 3 using xhci_hcd 2023-01-04T23:44:08.519572-08:00 cockpit kernel: [ 4.051608] ata3: SATA link down (SStatus 0 SControl 330) 2023-01-04T23:44:08.519572-08:00 cockpit kernel: [ 4.173060] usb 1-5: New USB device found, idVendor=0e8d, idProduct=0608, bcdDevice= 1.00 2023-01-04T23:44:08.519573-08:00 cockpit kernel: [ 4.173065] usb 1-5: New USB device strings: Mfr=5, Product=6, SerialNumber=7 2023-01-04T23:44:08.519573-08:00 cockpit kernel: [ 4.173067] usb 1-5: Product: Wireless_Device 2023-01-04T23:44:08.519573-08:00 cockpit kernel: [ 4.173068] usb 1-5: Manufacturer: MediaTek Inc. 2023-01-04T23:44:08.519574-08:00 cockpit kernel: [ 4.173069] usb 1-5: SerialNumber: 000000000 Theoretically, I guess the kernel could have put the device into an unrecoverable state, even after power cycling, but that's more of a question for an expert. Not to jump to conclusions, but this is starting to sound like a random hardware failure to me. The mobo is still only 3 months old. The one other thing I did try is flipping some XHCI handoff setting in my BIOS, but that didn't help either sadly. Matthew
