Search Results for 'bluetooth'

I recently bought a PCIe/USB wlan + bluetooth card, when it arrived with a small dvd I realised the required driver was source code, and needs to be compiled and linked in order to run. (please forgive my mainframe terminology).
I have never needed to do this before with a PC so I am looking for pointers and suggestions to enable me to complete the process.
Attached is the readme file which describes the procedure to be followed. I was immediately suspicious when I read that the kernel source must be present in order to produce the executable module. I do not really believe that, having a mainframe background, where such matters as linking or consolidation are usually handled by the operating system, or can be optional only for efficiency. Maybe using modprobe will achieve the required inclusion of the new module into the kernel without kernel source being present? Does the make procedure have to be run on the target machine or can it be run on another with the same kernel then copied to the required machine? The make you see in the screenshot was not on the target machine, which requires kernel 4.19.152.

I ran make as described in the readme file, using the Makefile which is attached, which I presume used the 2 files supplied, asix.h and ax88179_178a.c.

I now have a new file created by make named modules.order, it is not an executable object module as it contains text.
make reported 2 errors which may be merely warnings that do not affect the compile. However no module was produced and error 1 was reported, please see terminal screenshot.
Any pointers or comments will be thankfully received, many thanks in advance.

Attachments:

1. 

   make_driver_1.jpg
   

[Moderator Brian Masinick]

pulseaudio-module-bluetooth installed is not the only factor. I have done this without success.

--
Brian Masinick

[Moderator Brian Masinick]

I’m pretty sure that we need the Bluetooth/Wireless firmware installed for our specific devices.
For me, I think it is the Intel Wifi package; I’ll get the name and also the specific library files necessary within the package and check BOTH.
Hopefully that will restore access.

--
Brian Masinick

[Moderator caprea]

BobC, until now for getting audio-bluetooth devices to work, pulseaudio-module-bluetooth needs to be installed.and for that pulseaudio.(Otherwise you have to compile bluez-alsa, sounds like Xecure is working on a deb-package))

Tested the only bluetooth- device I own, a nice bluetooth-speaker and this worked without any problems with the new version.(pulseaudio is installed now ,though)

$ LANG=C apt policy policykit-1
policykit-1:
  Installed: (none)
  Candidate: 0.105-29+antix1
  Version table:
     0.105-29+antix1 500
        500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/testing testing/nosystemd amd64 Packages
     0.105-29 500
        500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
helga@antix1:~
$ LANG=C apt policy blueman
blueman:
  Installed: 2.1.4-1.0antix1
  Candidate: 2.1.4-1.0antix1
  Version table:
 *** 2.1.4-1.0antix1 100
        100 /var/lib/dpkg/status
     2.1.4-1+b1 500
        500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages
     2.0.8-1.antix1 500
        500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/antix/testing testing/main amd64 Packages

[Moderator BobC]

I did get anti’s packages installed and got bluetooth to pair with my phone and headphones without the policykit-1 getting installed.

I did not get the headphones to work and couldn’t figure out how to configure them. I tested them from my phone and they worked fine from there. Perhaps there is some other package needed or something that I need to do that isn’t on the menu?

PS: I was able to send a file to my phone but didn’t see a way to send one from the phone to my computer via bluetooth…

Pss: i was able to send a file from the phone to the pc also.

• This reply was modified 2 years, 4 months ago by BobC.
• This reply was modified 2 years, 4 months ago by BobC.

Brian Masinick wrote:

If you have any ideas or see any clear issues, let me know and I’ll try again soon.

I would start with a new thread, and first test:
1. With a similar kernel to EndeavourOS (5.8 antiX kernel, for example).
2. Copy the corresponding firmware file from EndeavourOS to your antiX system.
3. Start debugging with sudo dmesg and see if there are any errors there.

• This topic was modified 2 years, 4 months ago by Brian Masinick.
• This topic was modified 2 years, 3 months ago by Brian Masinick.

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

[Moderator Brian Masinick]

I’m giving up for today but I will come back to this. It sure looks like a software problem since I have three different systems and two different Bluetooth devices that can communicate, and I’ve been able to get one of my operating systems on the problem system to work.

If you have any ideas or see any clear issues, let me know and I’ll try again soon.

--
Brian Masinick

[Moderator Brian Masinick]

In spite of getting Bluetooth to work and to achieve listening with my Soundcore Life Q10 headset on Endeavor OS, the same hardware where I’ve been running MX Linux, antiX 19.3, antiX Alpha Bullseye and Debian Bullseye Alpha 3, only Endeavor OS is working, suggesting something is wrong with the entire set of packages available with Debian-based systems (sample size 4) yet working with another OS on the same hardware.

Has anyone seen anything else? Any other thoughts on what has caused this apparent regression?

--
Brian Masinick

[Member Robin]

OK, I only thought of helping in test of bluetooth as asked here. But never mind, I’ll wait for things to happen 🙂

Windows is like a submarine. Open a window and serious problems will start.

[Member Xecure]

Brian Masinick wrote:

Could that be what is causing me problems? I STILL see
“Connection Failed, Protocol not available”

You need pulseaudio and pulseaudio-module-bluetooth for a bluetooth headset to work, as indicated by other threads (that is why it worked on MX, which does, as far as I know, use pulseaudio).

Off-topic: A bluez-alsa .deb package would make it possible to stream audio to the headphones using alsa + bluetooth without pulseaudio. I was trying to use the raspberry pie build as reference to build a .deb for antiX, but that requires systemd, so I will continue investigating (didn’t have much time to experiment) on the weekend and possibly come with something that does not require pulseaudio. But this is not related to this thread.

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

[Member Robin]

Since I have already tested blueman on 17.4.1 version, I could check your new version also. On 17.4.1 the cellphone paired and connected without any problems, but when it came to transfer files there was no way to make this work. I had to use an old Win2000 in Virtualbox in order to transfer files finally. So it would be interesting to find out whether your new version will do the job.
So my question is: Will this version of yours work on 17er antiX also, or do I have to create an 19er stick for this testing?
If 19 is necessery, I’ll have to check whether graphics driver is fixed for this nvidia go 6600 card, before I can proceed to bluetooth tests therein.
Greetings and best wishes for the New Year
Robin

Windows is like a submarine. Open a window and serious problems will start.

[Moderator Brian Masinick]

I don’t know what is STILL wrong. I did
sudo apt purge policykit-1
and then

wget https://download.tuxfamily.org/antix/Testing/blueman_2.1.4-1.0antix1_amd64.deb
sudo apt install ./blueman_2.1.4-1.0antix1_amd64.deb

and I confirm that
$ `apt policy blueman
blueman:
Installed: 2.1.4-1.0antix1
Candidate: 2.1.4-1.0antix1
Version table:
*** 2.1.4-1.0antix1 100
100 /var/lib/dpkg/status`

although I also see:

     2.1.4-1+b1 500
        500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages
     2.0.8-1.antix1 500
        500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/main amd64 Packages

Could that be what is causing me problems? I STILL see
“Connection Failed, Protocol not available”

dmesg shows a few Bluetooth messages, but I did not see any obvious error indications.

I’m going to check another system that I previously thought was working and see if it is still working on this hardware.
If it is, I have something set up wrong on this system. If the other system doesn’t work anymore, I may have another issue.
I’ll follow up when I have more diagnostic details available.

--
Brian Masinick

[Moderator BobC]

After rebooting and updating, i went to install blueman and modem-manager-gui, but it says its going to install policykit-1 as an additional package, so I didn’t say yes.

Let me know what to do next…

From my bullseye test system:

Fetched 23.4 MB in 7s (3,573 kB/s)                                             
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
demo@antix1:~
$ sudo apt install blueman modem-manager-gui
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  policykit-1
Suggested packages:
  evolution-data-server libindicate5 | libmessaging-menu0
Recommended packages:
  pulseaudio-module-bluetooth modem-manager-gui-help yelp policykit-1-gnome
  | polkit-1-auth-agent
The following NEW packages will be installed:
  blueman modem-manager-gui policykit-1
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,213 kB of archives.
After this operation, 5,250 kB of additional disk space will be used.
Do you want to continue? [Y/n] n 
Abort.
demo@antix1:~
$ apt policy blueman modem-manager-gui policykit-1
blueman:
  Installed: (none)
  Candidate: 2.1.4-1+b1
  Version table:
     2.1.4-1+b1 500
        500 http://mirror.steadfast.net/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     2.0.8-1.antix1 500
        500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/main amd64 Packages
modem-manager-gui:
  Installed: (none)
  Candidate: 0.0.20-2
  Version table:
     0.0.20-2 500
        500 http://mirror.steadfast.net/debian bullseye/main amd64 Packages
policykit-1:
  Installed: (none)
  Candidate: 0.105-29+antix1
  Version table:
     0.105-29+antix1 500
        500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/nosystemd amd64 Packages
        100 /var/lib/dpkg/status
     0.105-29 500
        500 http://mirror.steadfast.net/debian bullseye/main amd64 Packages
demo@antix1:~

• This reply was modified 2 years, 4 months ago by BobC.
• This reply was modified 2 years, 4 months ago by BobC.

[Moderator Brian Masinick]

I am able to listen to audio and video on this release, just not via Bluetooth. That’s the only capability I have tried that definitely is not working on my system.
I will try the same on antiX 19.3 to compare.

--
Brian Masinick

[Moderator Brian Masinick]

apt policy policykit-1
policykit-1:
  Installed: 0.105-29+antix1
  Candidate: 0.105-29+antix1
  Version table:
 *** 0.105-29+antix1 500
        500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/nosystemd amd64 Packages
        100 /var/lib/dpkg/status
     0.105-29 500
        500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages

apt policy blueman
blueman:
  Installed: 2.1.4-1+b1
  Candidate: 2.1.4-1+b1
  Version table:
 *** 2.1.4-1+b1 500
        500 http://ftp.us.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     2.0.8-1.antix1 500
        500 http://mirrors.rit.edu/mxlinux/mx-packages/antix/testing testing/main amd64 Packages

I am able to see my “Soundcore Life Q10” Bluetooth headset, which I have used many times on the same computer, (definitely with MX Linux, possibly with other distros too. I’ve also used this device (and others) successfully with my Google Pixel 3 Android Phone and my Acer Chromebook 715.

I cannot connect to this device:
“Connection Failed, Protocol not available”

--
Brian Masinick