Search Results for 'bluetooth'

[Moderator Brian Masinick]

I agree with you. I am not satisfied that I have found the actual issue, though the failure of the bluetoothctl program on Debian provided me with the best clue so far.

My intention is to chase this on Debian because I am almost certain that Bluetooth headphones used to work with MX Linux.

Only a couple of weeks ago I was listening to programs on MX Linux.
When I noticed it not working there I don’t suspect a regression just in our code, I’m seeing it in each Debian based distribution I currently have installed.

I may pull in one of the *buntu varieties to further confirm my suspicion and double check exactly what was failing on Debian and check for recent Bluetooth defect reports in their reporting system.

I’m definitely not seeing this confined to antiX, I’m seeing it across each Debian-based distribution I have installed on my Dell Inspiron laptop.

I’ll pursue this, report anything I can actually and accurately reproduce, assuming that I don’t find any existing, recently reported defects.

--
Brian Masinick

[Member Xecure]

We can try to figure this out if you can share with us the bluetooth device information and the dmesg error outputs related to bluetooth.
I can tell you that I got bluetooth+headset to work on antiX, but my bluetooth device is different than yours. As you say, it could be firmware related (we could compare firmware files for your specific bluetooth device between antiX/Debian and arch), driver related (Depending on the kernel version, we could explore if there were any changes) or, as you suspect, related to the bluetooth Bluez package.

We should first diagnose and discard other reasons. If it is in fact as you say, Bluez related, then we can better report the error to Debian maintainers, but I think we should try to diagnose it ourselves first.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator Brian Masinick]

I have tested several things over the past week.

As I mentioned last week Bluetooth headphones, specifically my Soundcore Life Q10 Bluetooth headphones and I checked another pair of Bluetooth earphones. Both still work fine with my Google Pixel 3 Android phone. They both also work with Endeavor OS as previously discussed.

I tried adding the BlueZ package and the firmware that goes with it. So far no luck. I have problems with it on MX Linux and Debian. It definitely used to work with MX Linux.

However I got it to work with another Linux distribution, openSUSE, suggesting that the RPM and Arch .bz2 packages work. I still think that there is an unresolved Debian package regression, probably in the firmware library.

On Debian when I added the BlueZ package and firmware, then invoked the bluetoothctl command, just after starting the command I had a fatal program error that kills the command but doesn’t crash the entire system. That’s a new problem.

Once I am able to repeat the steps I will create a defect report to either Debian or the package team after checking for existing defects.

This one doesn’t appear to be caused by anything we build in antiX.

--
Brian Masinick

[Member Xecure]

You can change the website language. This is in english:
https://www.aliexpress.com/item/1005001458043499.html?spm=a2g0s.9042311.0.0.12ba63c0ZGUJk7

Note:.
The adaper don’t support ThinkPad Wlan card(FRU#)
Not Includes the NGFF Wlan Card !!

Meaning it is only the PCIe adapter, but does not include the wireless card. See the video I linked above. The user also bought it without knowing that it did not include the wifi card and had to buy it separately.

Contact the seller and ask them to recommend a compatible wifi+bluetooth card that works with this PCIe adapter. Then, let us know and we will check if it has Linux driver support.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member roland]

https://es.aliexpress.com/item/1005001458043499.html?spm=a2g0s.9042311.0.0.12ba63c0ZGUJk7

Thisis the www page where I bought the device. It is described as a Bluetooth wireless card, wlan adapter, if I have understood the Spanish text below correctly. It would not surprise me top learn that it isn’t a wlan adapter, the price alone makes me suspicious, and the fact that only 8 have been sold.

Tarjeta inalámbrica Bluetooth para pciE-1X a ngff-ekey PCIE, ordenador portátil, tarjeta WIFI, adaptador WLAN, placa adaptadora de antena Dual
8 vendidos

The photo of the card in its slot may be an early one while the build was ongoing, it is now connected by a short loom to an internal USB port on the mainboard, but I take your point and will remove the side and check that out. The card is so devoid of components there is no heat sink as such.

[Member Xecure]

Looking at your other post about how you set up your desktop PC, I cropped one of the photos and am displaying it here:

Is the above (blue) your pci wifi card? If so, is the connector (red) a USB connector that needs to be connected to a USB 2.0 port on your motherboard?
Maybe it is the angle of the photo, but it seems you are missing the bluetooth/wifi card on that PCI device (at least we cannot see the heat sink, that should be where the pink square indicates).

Please provide the link to the device you bought. My guess is that this is only the PCI adapter, but the wifi card (with bluetooth functionality) is missing, so this PCI card does nothing at all. it only has USB connector for the bluetoth functionality, but without the wireless card, this connector also does nothing.

I hope I am mistaken, and the link you will provide will prove me wrong. This way we can finally find the device you bought and start searching for drivers.

EDIT: See the first 2 minutes of this video so you understand what I mean by “missing the wifi card” – https://www.youtube.com/watch?v=wjCDti0RV-s

• This reply was modified 2 years, 4 months ago by Xecure. Reason: video link
• This reply was modified 2 years, 4 months ago by Xecure.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member roland]

The device was described as a PCIe wlan adapter with bluetooth capability. It is plugged into a PCIe single lane slot and also to an internal PCI port via cable. But I am using a TP-Link USB wlan adapter as an interim measure to get network access ,until this is fully installed.

The issue dvd appears to contain drivers for a range of devices and operating systems, I used the folders /media/cdrom/USB LAN/ASIX/88179/Linux to locate driver source tar file.

The PC is a new build and I am aware certain devices may not be correctly installed. I am giving priority to a dependable network installation before turning to several other known issues such as occasional freezing which I thought I had cured with kernel 4.19.152.

I have never been able to satisfactorily install Nvidia drivers on any PC! My excuse is that I do little that requires fancy graphics capability, being mainly text and simple browsing, and the default software usually suffices.

lspci -nn delivers a list of messages which mean little to me.

sudo dmesg | grep -i “ax88179\|0df6:0072″` it seems finds nothing corresponding to the text.

Thanks to all contributors for your valuable time. Here I work under adverse conditions, it’s almost 0 degrees farenheit and I have a very poor wlan connexion.

Attachments:

1. 

   issue_dvd.jpg
   

2. 

   sudo_dmesg.jpg
   

1. lspci_nn.pdf

[Member Xecure]

Some of the feedback was split to: https://www.antixforum.com/forums/topic/split-bluetooth-testing/

If your post is missing and you didn’t know where it went, it is there now.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Xecure]

roland wrote:

I recently bought a PCIe/USB wlan + bluetooth card

Is it PCI or USB? Are we taking about ONE device or 2 different devices?

Looking again at the readme file you uploaded earlier:

ASIX AX88179_178A USB 3.0/2.0 Gigabit Ethernet Network Adapter

The driver is only for the ethernet part of the USB device. Are you sure the device matches the CD/DVD? It doesn’t mention any wireless or bluetooth chips or functionality.

Did you connect the PCI card yet? If you did, we need to see if it is being detected at all.
lspci -nn

Was the PCI device connected when you performed the inxi command, which output you just shared? If it was, then it seams it is not detected properly. We will have to start from the pci information and try different solutions little by little.

The firmware may already be included inside of the PCI device (some have it inside, and some don’t need it), or it may be a file somewhere in the firmware folder.
We could start with the device id.
sudo dmesg | grep -i “ax88179\|0df6:0072″`

But I think we first need to make sure we are talking about the same device.

• This reply was modified 2 years, 4 months ago by Xecure. Reason: typo

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator Brian Masinick]

Most, if not all of the dialog about Bluetooth that was not already in a different topic has been SPLIT to another topic entitled “Split: Bluetooth Testing”.
I believe that there is also at least one other topic concerning similar issues. If necessary we can merge these or create another separate space, but hopefully this will keep this topic focused on the overall “antiX-bullseye-a1-x64-bullseye-full available” concerns.

Note to readers: if you have issues concerning Bluetooth with the new test release, please find one of the other Bluetooth threads and put your issue there or in a new message, if you feel it is different and needs a different emphasis.

--
Brian Masinick

[Member Xecure]

Just tested on a live USB with antiX 19.2.1 base x64 (not updated) on my laptop.
0. Enabled bluetooth with the connman gui.

1. I installed
bluez blueman pulseaudio pulseaudio-module-bluetooth pavucontrol

2. I checked that bluetooth was enabled

service bluetooth status
...is running ...

3. I ran the blueman applet so I have a systemtray icon to keep experimenting
blueman-applet &

4. Right-clicked the tary icon, and selected Devices. Hit search and it found my phone. Right-click on the phone, selected “trust”. Then right-click egain and selected “pair”. A pop up message appeared, telling me to verify if the small code is correct and asking to allow connecting in my phone. I unlocked my phone’s screenlock and saw the same message with the same code. I “allowed” the connection both on the phone and on the laptop and it paired correctly. I tried sending an image from my phone to my laptop and I recieved it correctly (now I think I know how to do it).

5. I enabled pulseaudio daemon
pulseaudio -D &

6. I pressed the pairing button on my bluetooth headset. Then I clicked search on the opened blueman devices window. It found my bluetooth headset. I right click, select “trust”. Then right-click again, and selected “pair”. It paired correctly and gave me 3 options to connect to the headset (I selected the one that is set as “Headset”, as that is how I wanted it to work like, and not as microphone. I then heard a sound from my headset and knew it paired correctly. I open pavucontrol to make sure the headset was the main output device. I then opened firefox-esr, went to youtube, selected a video and it played the sound on my headset.

I cannot say for your specific device, but maybe a kernel update is necessary for better bluetooth driver support for your device.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Xecure]

Not enough information.
First we need to know the bluetooth device

lsusb
inxi -Nxxx

Second, we need to be sure that bluetooth is working properly. You need to check the dmesg output to see if there is any error related to the bluetooth.
sudo dmesg | grep -i “bl\|bluetooth”
if we knew the device and driver loaded, we could check for other patterns to find any output related to the device and drivers.
We also need to make sure that the bluetooth service is running
service bluetooth status

Third, we need to make sure that connman enabled bluetooth. Check /var/lib/connman/settings to see if

[Bluetooth]
Enable=true

If this is on, then connman is not blocking the bluetooth signal.

You also need to make sure that pulseaudio (launching pavucontrol will tell you if the pulseaudio daemon is running)

PPC wrote:

I installed pulse audio, with all dependencies, pavucontrol.

Did you also install pulseaudio-module-bluetooth (or else pairing won’t work).

PPC wrote:

– I start “blueman-manager”, I hit the “bluetooth” button on my column, click “search” on blueman. My column name appears on blueman (as JBL go 2). I right click my column’s icon and select “pair”.

Did you also select “trust” before pairing and connecting?

PPC wrote:

A window asking for the column’s pin pops up, I enter it (“0000”).

…

After many tries, I tried to connect my android phone to my PC- same outcome- it’s correctly identified, asks for PIN

My bluetooth headset has no security pin feature, so this may be the real reason for the problem. I will see if I can figure out how to enable it on my phone and see if this is the reason.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

Hi! I have a problem connecting to devices using bluetooth:
Because my onboard soundboard is busted (no sound at all, after some days with very bad sound), I borrowed a bluetooth stick and tried to pair my antiX 19.X PC with a portable JBL column, to have sound on my PC (while I’m waiting for my new soundboard to arrive from China, it’s seems to be on it’s way by mule…).
I don’t think inxi of my system is relevant to this question, but I’m using a BlueWalker BW-UD02.

What I did- on antiX 19.X 64bits full:
– I reenabled bluethoot on sysV on Control Centre and rebooted
– I installed pulse audio, with all dependencies, pavucontrol.
– I searched on-line, and in the forum, and installed “blueman” with all dependencies. I installed “bluetoothctl”.
– I start “blueman-manager”, I hit the “bluetooth” button on my column, click “search” on blueman. My column name appears on blueman (as JBL go 2). I right click my column’s icon and select “pair”. A window asking for the column’s pin pops up, I enter it (“0000”). To the right of the columns id in blueman, some statisctics appear, and it says “connected”, but the column is not paired (it’s light does not stop blinking, and it does not make any sound)- the statistics disappear after about 1 minute.

What happens:
– No pairing ever happens,
– On cli I get this output:

`Generate (/usr/lib/python3/dist-packages/blueman/gui/manager/ManagerDeviceMenu.py:173)
JBL GO 2
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/dbus/connection.py”, line 607, in msg_reply_handler
*message.get_args_list()))
File “/usr/lib/python3/dist-packages/blueman/bluez/Device.py”, line 33, in err
raise exception
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.`

Note: the same set up, Bluetooth adapter and column were testes on a windows 10 machine and worked fine.

After many tries, I tried to connect my android phone to my PC- same outcome- it’s correctly identified, asks for PIN, but pairing is not achieved…
So, blueman does not pair with any bluetooth device, dispite identifying them…

I also tested connection via cli, launching bluetoothctl and then:
[bluetooth]# power on
[bluetooth]# agent on
[bluetooth]# default-agent
[bluetooth]# scan on

But no device is ever even found this way… the outcome is

Discovery started
[CHG] Controller 00:0B:0D:0A:68:41 Discovering: yes

Do I have to remove “policy kit” like in the thread about testing Bluetooth on antiX 21 alpha? I don’t like to mess with my system packages unless I have to…

P.

• This topic was modified 2 years, 4 months ago by PPC.

[Moderator Brian Masinick]

caprea wrote:

Brian, is pulseaudio running ?

In Debian and MX Linux, yes.

I suspect a defect that affects access to the Bluetooth library calls.

Everything except the actual Bluetooth connect command works.

--
Brian Masinick

[Member ile]

Hello anticapitalista

System:    Host: antix1 Kernel: 4.9.240-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
           v: 10.2.0 Desktop: Fluxbox 1.3.5 dm: SLiM 1.3.6 
           Distro: antiX-bullseye-a1_x64-full Grup Yorum 3 January 2021 
           base: Debian GNU/Linux bullseye/sid 
Machine:   Type: Laptop System: LENOVO product: 20428 v: Lenovo Yoga 2 11 
           serial: <root required> Chassis: type: 10 v: Lenovo Yoga 2 11 
           serial: <root required> 
           Mobo: LENOVO model: VIUU4 v: 31900058WIN serial: <root required> UEFI: LENOVO 
           v: AACN21WW date: 01/30/2015 
Battery:   ID-1: BAT0 charge: 29.5 Wh condition: 29.5/34.0 Wh (87%) volts: 8.2/7.4 
           model: Lenovo IdeaPad type: Unknown serial: BAT20101001 status: Full 
CPU:       Dual Core: Intel Core i3-4012Y type: MT MCP arch: Haswell speed: 1500 MHz 
           min/max: 600/1500 MHz 
Graphics:  Device-1: Intel vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0a1e 
           Display: x11 server: X.Org 1.20.10 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4200 (HSW GT2) v: 4.5 Mesa 20.2.6 
           compat-v: 3.0 direct render: Yes 
Network:   Device-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter 
           vendor: Lenovo driver: ath9k v: kernel port: 3040 bus ID: 01:00.0 
           chip ID: 168c:0036 
           Device-2: Qualcomm Atheros AR3012 Bluetooth 4.0 type: USB driver: btusb 
           bus ID: 2-5:7 chip ID: 0cf3:3004 
Drives:    Local Storage: total: 473.03 GiB used: 1.28 GiB (0.3%) 
           ID-1: /dev/sda vendor: Seagate model: ST500LX012-SSHD-8GB size: 465.76 GiB 
           speed: 3.0 Gb/s rotation: 5400 rpm serial: W3N1A0QN rev: LVM1 scheme: GPT 
           ID-2: /dev/sdb type: USB vendor: Kingston model: DataTraveler 2.0 
           size: 7.27 GiB serial: 1C6F654E572CEE80890E0A8D rev: PMAP scheme: MBR 
Weather:   Temperature: 7.8 C (46 F) Conditions: Clear sky 
           Wind: from NNE at 1.3 m/s (5 km/h, 3 mph) Cloud Cover: 0% Humidity: 28% 
           Dew Point: -9.6 C (15 F) Pressure: 1011.8 mb (34 in) 
           Location: Washington, D.C., DC, US, 20500 
           Current Time: Sat 09 Jan 2021 08:07:13 AM EST 
           Observation Time: 2021-01-09 14:37:00 (America/New_York -0500) 
           Source: WeatherBit.io 
Info:      Processes: 155 Uptime: 13m Memory: 3.76 GiB used: 454.7 MiB (11.8%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 Compilers: gcc: 10.2.1 alt: 10 
           Shell: bash v: 5.1.0 running in: roxterm inxi: 3.0.36 
demo@antix1:~
$ env-info

OS: antiX-bullseye-a1 Grup Yorum
Kernel: Linux 4.9.240-antix.1-amd64-smp x86_64
CPU: Intel(R) Core(TM) i3-4012Y CPU @ 1.50GHz
Uptime: 0d 0h 13m
Packages: 1611
Shell: /bin/bash
WM: space-fluxbox
Init: sysvinit
GTK Theme: Arc-EvoPro2
GTK Icons: papirus-antix
Font: Ubuntu 10.5
Disk: 61M / 3.0G
Mem: 404Mi / 3.8Gi