- This topic has 30 replies, 5 voices, and was last updated Oct 6-11:25 am by caprea.
- Posts
abc-nix
chip-ID: 1310:0001
Based on the hardware database, it should work with the btusb driver, as listed in your inxi.
sisqonrw
Here the result with USB Bluetooth dongle, without and again with dongle.
bluetoothctl list
Controller 00:0C:78:30:3C:9F BlueZ [default]
demo@antix1:~
$ bluetoothctl list
demo@antix1:~
$ bluetoothctl list
Controller 00:0C:78:30:3C:9F BlueZ [default]and he do not find any bluetooth device. my mobile phone find bluetooth device.
bluetoothctl scan on
Discovery started- This reply was modified 2 months ago by sisqonrw.
capreasisqonrw, could you post the bluetooth part of
inxi -zv7ok
Bluetooth:
Device-1: National Bluetooth Device type: USB driver: btusb v: 0.8
bus-ID: 3-1:10 chip-ID: 0400:080a class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 10 state: up address: <filter>
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.I know this is a lot to ask of you. If you have time, please start emmabuntus and save the dmesg output for your bluetooth device
sudo dmesg | grep -i "blu\|btusb\|bt\|0400\|080a"
and also the installed packages related to bluetooth and firmware:
apt list --installed | grep "blu\|firmware"And in antiX, run the same two commands again, and we will compare the output to find what the issue may be.
When you have time, please share the output here of each command, first for emmabuntus and then antiX. Hopefully it is something that can easily be fixed by adding the correct firmware. If we can fix your issue here, we may be able to fix it for other users in the future.
- This reply was modified 1 month, 4 weeks ago by abc-nix. Reason: fix command
PPC
Small improvement, when I tried last night.
Installing “gir1.2-gnomebluetooth-3.0” does make it so my computer can detect and try to connect to my phone and my earbuds. My phone also detects my computer and tries to connect to it. Once I think I got a message that my phone connected to my computer. I tried to send a file from my pc to my phone. My phone asked if I wanted to accept the file, but the transfer failed. After I disconnected the phone’s BT and reconnected again, the computer always fails trying to connect to it…Edit: I’m thinking the failure to properly connect is due to how old the BT dongle is (modern devices are reported not to connect to BT 2 devices, and my BT is even older than that- ex: https://www.quora.com/Can-I-use-a-Bluetooth-2-0-device-on-my-Bluetooth-4-0-Android-smartphone)
So, probably the OP will be able to connect to his BT devices after installing the above mentioned package, or so I hope. If that works, I suggest that that package should come with antiX future versions by default… if required to connect to certain devices (it’s tiny, and antiX already has more BT drivers than Debian it self).
P.
- This reply was modified 1 month, 4 weeks ago by PPC.
- This reply was modified 1 month, 4 weeks ago by PPC.
hi here the result of antix first
(*** Forbidden. Contains contacts. Message seems to be spam. ***)
@sisqonrw : Did you try to install the package I mentioned? Any change if you did? With my BT dongle it almost worked…
no i didnt. should i install this
gir1.2-gnomebluetooth-3.0
after booting with antix?
Yes.
You can do it using the Terminal:
sudo apt update && sudo apt install gir1.2-gnomebluetooth-3.0In my case I did not even have to restart antiX or the BT manager. I just searched for devices and my phone and earbuds were detected (but I could not connect to them, unfortunately, probably because my BT dongle is too old).
note: I’m using a 64bits antiX, but the package should be available for 32bits too…
P.
- This reply was modified 1 month, 4 weeks ago by PPC.
@sisqonrw
Thanks for providing the terminal output. It seems we cannot judge the messages from dmesg because of bluetooth being disabled.Reviewing the filtered list of installed packages, the only relevant one included in emmabuntus not included in antiX is bluez-tools, but it should only be related to cli (terminal) tools, to use separatedly, and not part of the bluetooth component. I don’t think installing it will help.
The other firmware packages are not related to bluetooth. And python3-bluez is for python bluetooth development.I would try 3 different things you can do on the same session.
1. On the live boot menus of antiX 23, if they look like this, then remove the whole boot parameter disable=*** using the backspace of your keyboard, so the bluetooth service is enabled by default on antiX. And test bluetooth search again as you did previously. If a pop-up in blueman asks to enable bluetooth, say yes.
2. Install the package PPC mentioned and test bluetooth search for devices again.
sudo apt update && sudo apt install gir1.2-gnomebluetooth-3.0
as PPC mentioned.3. Install bluez-tools just in case some dependencies are helpful for bluez to detect devices. Search again for devices.
Extra: Again share the dmesg output now that bluetooth is already enabled by step 1. With this we should be able to compare kernel messages between the two distros.
sudo dmesg | grep -i "blu\|btusb\|bt\|0400\|080a"Installing any of the different packages not present in antiX (list below) will not help with bluetooth detection (in my opinion).
Just so others who may know a bit more can have a look. These are the important lines in emmabuntus’ dmesg output:
[ 17.501164] usb 2-1: New USB device found, idVendor=0400, idProduct=080a, bcdDevice= 1.00 [ 49.177056] Bluetooth: Core ver 2.22 [ 49.177128] Bluetooth: HCI device and connection manager initialized [ 49.177136] Bluetooth: HCI socket layer initialized [ 49.177140] Bluetooth: L2CAP socket layer initialized [ 49.177148] Bluetooth: SCO socket layer initialized [ 49.634769] usbcore: registered new interface driver btusb [ 49.673104] Bluetooth: hci0: unexpected event for opcode 0x0000 [ 49.673115] Bluetooth: hci0: unexpected event for opcode 0x0000 [ 82.745057] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 82.745061] Bluetooth: BNEP filters: protocol multicast [ 82.745069] Bluetooth: BNEP socket layer initialized [ 82.958150] Bluetooth: hci0: unexpected event for opcode 0x0000 [ 107.416829] Bluetooth: RFCOMM TTY layer initialized [ 107.416841] Bluetooth: RFCOMM socket layer initialized [ 107.416857] Bluetooth: RFCOMM ver 1.11And these are the packages emmabuntus has that are not included in antiX (from the apt filtered list):
> alsa-firmware-loaders > bluez-tools > dahdi-firmware-nonfree > firmware-intelwimax > firmware-ivtv > firmware-qcom-soc > firmware-siano > hdmi2usb-fx2-firmware > libluajit-5.1-2 > libluajit-5.1-common > pulseaudio-module-bluetooth > python3-bluezi have install it. then the result is as follow but he do not find the bluetooth headset sadly.
how should the boot option exactly be?
disable=***
or should be there only
quiet splash=vsudo dmesg | grep -i "blu\|btusb\|bt\|0400\|080a" [ 0.032755] ACPI: RSDT 0x00000000BFE8FA3C 000040 (v01 PTLTD RSDT 06040000 LTP 00000000) [ 0.032767] ACPI: FACP 0x00000000BFE99E20 000074 (v01 INTEL CALISTGA 06040000 LOHR 0000005A) [ 0.032780] ACPI: DSDT 0x00000000BFE903F8 009A28 (v01 INTEL CALISTGA 06040000 MSFT 02000002) [ 0.032794] ACPI: APIC 0x00000000BFE99E94 000068 (v01 INTEL CALISTGA 06040000 LOHR 0000005A) [ 0.032802] ACPI: HPET 0x00000000BFE99EFC 000038 (v01 INTEL CALISTGA 06040000 LOHR 0000005A) [ 0.032809] ACPI: MCFG 0x00000000BFE99F34 00003C (v01 INTEL CALISTGA 06040000 LOHR 0000005A) [ 0.032817] ACPI: APIC 0x00000000BFE99F70 000068 (v01 PTLTD ? APIC 06040000 LTP 00000000) [ 0.032824] ACPI: BOOT 0x00000000BFE99FD8 000028 (v01 PTLTD $SBFTBL$ 06040000 LTP 00000001) [ 1.125105] pci 0000:00:01.0: [8086:27a1] type 01 class 0x060400 [ 1.125831] pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400 [ 1.126209] pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400 [ 1.126583] pci 0000:00:1c.2: [8086:27d4] type 01 class 0x060400 [ 1.126964] pci 0000:00:1c.3: [8086:27d6] type 01 class 0x060400 [ 1.128532] pci 0000:00:1d.7: reg 0x10: [mem 0xc8004000-0xc80043ff] [ 1.132499] pci 0000:0a:09.0: reg 0x10: [mem 0xc8404000-0xc8404fff] [ 1.133225] pci 0000:00:1e.0: PCI bridge to [bus 0a-0b] (subtractive decode) [ 1.133243] pci 0000:00:1e.0: bridge window [io 0x0000-0xffff] (subtractive decode) [ 1.133246] pci 0000:00:1e.0: bridge window [mem 0x00000000-0xffffffff] (subtractive decode) [ 1.220260] pci 0000:00:1c.1: BAR 14: assigned [mem 0xc0400000-0xc05fffff] [ 1.220360] pci 0000:03:00.0: BAR 0: assigned [mem 0xc0400000-0xc0400fff] [ 1.220385] pci 0000:00:1c.1: bridge window [mem 0xc0400000-0xc05fffff] [ 1.220568] pci_bus 0000:03: resource 1 [mem 0xc0400000-0xc05fffff] [ 1.888652] ehci-pci 0000:00:1d.7: irq 23, io mem 0xc8004000 [ 1.901324] VUB300 Driver rom wait states = 1C irqpoll timeout = 0400 [ 10.454996] usb 3-1: New USB device found, idVendor=0400, idProduct=080a, bcdDevice= 1.00 [ 25.344741] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 26.150469] psmouse serio4: synaptics: Touchpad model: 1, fw: 6.2, id: 0x12a0b1, caps: 0xa04713/0x204000/0x0/0x0, board id: 0, fw id: 41763 [ 26.759259] Bluetooth: Core ver 2.22 [ 26.759308] Bluetooth: HCI device and connection manager initialized [ 26.759315] Bluetooth: HCI socket layer initialized [ 26.759319] Bluetooth: L2CAP socket layer initialized [ 26.759326] Bluetooth: SCO socket layer initialized [ 26.884318] usbcore: registered new interface driver btusb [ 26.886924] Bluetooth: hci0: unexpected event for opcode 0x0000 [ 26.896968] Bluetooth: hci0: unexpected event for opcode 0x0000 [ 109.183367] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 109.183372] Bluetooth: BNEP filters: protocol multicast [ 109.183379] Bluetooth: BNEP socket layer initialized [ 109.201245] Bluetooth: RFCOMM TTY layer initialized [ 109.201257] Bluetooth: RFCOMM socket layer initialized [ 109.201275] Bluetooth: RFCOMM ver 1.11 [ 136.266931] Bluetooth: hci0: unexpected event for opcode 0x0000 [ 629.095899] Bluetooth: hci0: unexpected event for opcode 0x0000- This reply was modified 1 month, 4 weeks ago by sisqonrw.
- This reply was modified 1 month, 4 weeks ago by sisqonrw.
- This reply was modified 1 month, 4 weeks ago by sisqonrw.
Thanks for the efforts, @sisqonrw, but I am out of ideas. The same kernel version, very similar bluetooth and firmware related packages, and the bluetooth related dmesg output is almost identical. I cannot guess what the differences may be between the two, antiX and emmabuntus, except for the desktop environment and maybe one of them has the kernel compiled slightly different, but this is speculation.
It is very unfortunate that we cannot arrive at a good solution through the proposed methods. If anyone has any other ideas, please share.
I hope that you don’t feel that your time was wasted, sisqonrw, and at the very least you may have learned some tricks in troubleshooting Debian based distros.
I will be giving up for now.
Regards,
abc-nixOh, you don’t have to apologize for that. This is not a problem for me.
I like doing something like that.
Maybe someone has another idea.I can try other things.
Is it possible to install an old kernel?
- You must be logged in to reply to this topic.