On Wed, 25 Jan 2023 at 14:54, Matthew McAllister <matthew.mcalliste...@gmail.com> wrote:
> 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 Hi, how does that compare with the output of (as root) lsusb -v -s 1:5 today? Not that I expect this will fix anything, just curious :/
