Hi , I build a pc gaming machine and install linux mint on it and for most the thinks works almost perfect except this dougle bluetooth of the brand ugreen , I just buy this device because it said bluetooth 5,4 and when I put the device the system recognize as a bt device but when I try to enable blueman , the program in seft crash I try this command and give me this error [ 9.428797] Bluetooth: hci0: command 0x1005 tx timeout [ 9.428845] Bluetooth: hci0: Opcode 0x1005 failed: -110 so.. I don't know can I do now , I try to forums of linux mint , telegram about linux mint , discord too and none it can give a awnser , can someone with more experience help me please and thanks for give me a little of your time and readme Ricardo.
Please try kernel 6.10 and if it still doesn't work, please attach `dmesg` output.
And please attach `lsusb` output as well.
(In reply to Artem S. Tashkinov from comment #1) > Please try kernel 6.10 and if it still doesn't work, please attach `dmesg` > output. I cannot send because is too long and I can't send it but it said the same error what I am posed here
command 'lsusb' Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 0b05:1a51 ASUSTek Computer, Inc. ROG RYUO III Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 005: ID 33fa:0010 USB2.0-BT Bus 001 Device 004: ID 045e:028e Microsoft Corp. Xbox360 Controller Bus 001 Device 003: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 002: ID 2dc8:5201 8BitDo 8BitDo Retro Keyboard Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
(In reply to ricardo from comment #4) > command 'lsusb' > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 007: ID 0b05:1a51 ASUSTek Computer, Inc. ROG RYUO III > Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub > Bus 001 Device 005: ID 33fa:0010 USB2.0-BT > Bus 001 Device 004: ID 045e:028e Microsoft Corp. Xbox360 Controller > Bus 001 Device 003: ID 062a:4101 MosArt Semiconductor Corp. Wireless > Keyboard/Mouse > Bus 001 Device 002: ID 2dc8:5201 8BitDo 8BitDo Retro Keyboard Receiver > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub the system detect the btusb device but crashed when I enable the bluetooth
(In reply to ricardo from comment #3) > (In reply to Artem S. Tashkinov from comment #1) > > Please try kernel 6.10 and if it still doesn't work, please attach `dmesg` > > output. > > I cannot send because is too long and I can't send it but it said the same > error what I am posed here $ dmesg > 20240720--linux-6.10--messsages.txt Did you try to attach this file clicking on *Add an attachment*? If that does not work, please tell us the size of the text file. $ ls -l 20240720--linux-6.10--messsages.txt
the size of the text file it is 85,3 kB 1137 line of code
https://pastebin.com/mNRqk97e
Created attachment 306602 [details] dmesg
Your BT dongle could be malfunctioning, that's all I can say: [ 7.641748] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 7.641750] Bluetooth: BNEP filters: protocol multicast [ 7.641752] Bluetooth: BNEP socket layer initialized [ 7.746321] input input12: unable to receive magic message: -121 [ 9.399212] input input12: unable to receive magic message: -121 [ 9.449012] input input12: unable to receive magic message: -121 [ 9.524765] Bluetooth: hci0: command 0x1005 tx timeout [ 9.524802] Bluetooth: hci0: Opcode 0x1005 failed: -110 [ 57.877847] input input12: unable to receive magic message: -121 [ 57.944875] input input12: unable to receive magic message: -121 [ 65.820223] input input12: unable to receive magic message: -121 [ 65.894224] input input12: unable to receive magic message: -121 [ 67.979270] input input12: unable to receive magic message: -121 Someone has the exact same issue: https://bbs.archlinux.org/viewtopic.php?id=296195 and they've bought a new one. A google search has not revealed any success stories: https://www.google.com/search?q=%22Opcode+0x1005+failed%22
You could try a solution posted here: https://askubuntu.com/questions/1205962/bluetooth-dongle-problem
so... the doungle it must be remplaced it? there's not another solution from this?
I bought the brand tp link nano USB adapter UB400 , and now is worked so it was the other bluetooth device the issue not a bug , thanks for the support