Search Results for 'bluetooth'

[Member Xecure]

Just in case others haven’t seen it, here are some things anticapitalista would like tested:

– blueman (64 bits only)- Graphical bluetooth manager (first purge policykit-1 before testing) – Feedback here

– modem-manager-gui (64 bits only – also install modem-manager-gui-help )- Graphical interface for mobile 3G/4G connection (It can send, receive and store SMS messages, send USSD requests and read answers in GSM7 and UCS2 formats, and scan for available mobile networks.) First purge policykit-1 before installing and testing – Feedback here

– xserver-xorg-video-sis671 (64 bits, but available in 32 bits also)- xorg graphics driver for SIS chipsets (should work on both antiX 19 and bullseye alpha) – Feedback here

• This reply was modified 2 years, 4 months ago by Xecure. Reason: Added proper links to all files

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

[Member Xecure]

I was lucky and got to borrow for today a bluetooth keyboard.
I am writing with it from antiX bullseye alpha write now, while also listening to music on my bluetooth headset (though I needed puseaudio, but this is not related to this blueman software.

Pairing and connecting worked perfectly at first go for both, so at least on these cases, your blueman package works perfectly.
You can see that policykit-1 is not installed:

$ 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

and that I have the correct blueman version:

$ 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

Thanks for everything you do anticapitalista.

PD: Wasn’t able to get pairing with the android mobile phone, but that may be related to incompetence (I had never done it before). If someone who knows how to and has done it before on antiX 19, please see if that works on the alpha with the blueman package built by anticapitalista.

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

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

[Member ile]

from live-session a1

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 
  Distro: antiX-bullseye-a1_x64-full Grup Yorum 3 January 2021 
  base: Debian GNU/Linux bullseye/sid 
Machine:
  Type: Laptop System: Acer product: Aspire E5-571 v: V1.04 
  serial: <root required> Chassis: type: 10 serial: <root required> 
  Mobo: Acer model: EA50_HB v: V1.04 serial: <root required> UEFI: Insyde 
  v: 1.04 date: 05/06/2014 
Battery:
  ID-1: BAT1 charge: 49.5 Wh condition: 49.5/55.9 Wh (88%) volts: 12.9/11.1 
  model: SANYO 0032334134314C41 serial: 0000 status: Full 
CPU:
  Dual Core: Intel Core i3-4030U type: MT MCP arch: Haswell speed: 874 MHz 
  min/max: 800/1900 MHz 
Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics 
  vendor: Acer Incorporated ALI driver: N/A bus ID: 00:02.0 
  chip ID: 8086:0a16 
  Display: x11 server: X.Org 1.20.10 driver: none unloaded: fbdev 
  resolution: 1366x768~N/A 
  OpenGL: renderer: llvmpipe (LLVM 11.0.0 256 bits) v: 4.5 Mesa 20.2.6 
  compat-v: 3.1 direct render: Yes 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Acer Incorporated ALI driver: r8169 v: 2.3LK-NAPI port: 3000 
  bus ID: 01:00.1 chip ID: 10ec:8168 
  Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter 
  vendor: Lite-On driver: ath9k v: kernel port: 3000 bus ID: 02:00.0 
  chip ID: 168c:0036 
  Device-3: Lite-On Atheros AR3012 Bluetooth type: USB driver: btusb 
  bus ID: 2-5:5 chip ID: 04ca:300b 
Drives:
  Local Storage: total: 473.03 GiB used: 1.22 GiB (0.3%) 
Info:
  Processes: 160 Uptime: 7m Memory: 7.76 GiB used: 242.0 MiB (3.0%) 
  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:~

[Moderator BobC]

I will try it tomorrow with my android phone and a bluetooth headset I have.

[Member Xecure]

Tested again, first purging blueman and policykit-1, reboot, reinstall blueman, and got to set up the wireless controller again. This worked. Could scan and find my mobile phone, trust, pair and connect, but couldn’t send or receive files. This may be me not knowing how to do it properly, so don’t trust this result.
I will ask tomorrow to borrow a bluetooth keyboard (and maybe even a mouse) and see if I can pair and use them.

Pairing bluetooth headset with bluez-alsa will have to wait. I will try to see tomorrow if with pulseaudio I can stream audio through bluetooth (paring with blueman and such) and report my findings.

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

[Member Xecure]

I have tested the new blueman version and works perfectly (live-USB with persistence). I tried to pair for the first time a Bluetooth ps3 controller, and it worked very well.
Had to first enable Bluetooth using cmst and then added blueman-applet to the startup file. The first time it launches, it will ask to enable the bluetooth service at startup, (first time I said no, and it didn’t ask again, so I had to enable the service manually). Tried it on two computers (different bluetooth cards) and it works. I don’t have any keyboard or mouse that uses bluetooth technology, but will try to transfer files t/from my mobile phone in a bit.

Once I figure out how to package bluez-alsa, I will also test with a bluetooth headphone, but the interface worked for me well to conned/disconnect, pair and unpair, remove and add Devices, etc, so I don’t expect any trouble there.

Cannot give any feedback for modem-manager-gui (sorry).

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

Several dual cpu mainboards have appeared on the Chinese markets under the tag X79 using socket R or LGA2011 cpu format. There is a variant under the tag X99 which uses a somewhat different socket type cpu. This text describes what I did to make a dual cpu X79 mainboard into a working PC running antiX 19, hopefully at minimal cost. There are minor hardware variations within this family of X79 tagged mainboards, mainly concerning the number of memory slots per cpu 2 or 4) and the number of SATA ports (4 or 6), and the positions of certain components and power input sockets on the board.

The board format is a variant of ATX a couple of inches or so wider than standard ATX but not so long as some, because the number of PCI-express expansion slots has been kept to 4, a practical minimum. This results that in the usual PC ATX case not all the screw holes on the right hand side will correspond to a threaded hole in the backsheet, although the holes to the left will all line up as intended. Some cases will not accept this board at all, the back sheet not being flat enough nor wide enough to take the board, or having a step or fold in the back sheet towards the right.

I looked through my junk cases and found one with a flat back sheet, without folds or corrugations over the width and length of the board. However part of 3 of the 4 drive bays overlapped one corner of the board, masking certain power sockets and attachment points. I therefore with tinsnips clipped out the lower 2 bays completely where they overlapped the board, and half of the bay above, thus making enough room around the board for the screws, cables and components required. This left just 1 full length 5 1/4″ expansion bay for a DVD/RW and another half length bay for a short media device reader, but no bay for any hard drive.

I screwed threaded brass 1/4″ board spacers into all the existing threaded holes in the back sheet, and attached the board to these, then marked through all the unused holes in the board onto the back sheet with an automatic centre-pop. Removing the board I drilled 2mm holes where marked, then crudely threaded them using a 4mm self-tapping screw, and screwed into these holes the required threaded brass 4mm spacers, with a drop of loctite to fix them. Some small holes in the board extremities only required a plastic spacer of the push-in type for support. Now I had the board securely attached with a full set of screwed and plastic spacers through the assigned holes.

I made a 3 1/2″ hard drive tower to fix onto the floor at the front of the case, using 1/2″ x 1/8″ steel strip cut and welded into a rigid rectangular stack and drilled and countersunk to accept 5 drives. Modern hard drives are thinner than they once were, so the stack still provides adequate clearance for the right hand cpu cooling radiator. The base of the stack has threaded holes for fixing with machine screws from underneath the case.

A tip to get all hard drive fixing holes in the right place is to carefully mark and double-check one strip for the drive fixing holes, drill 5mm through all 4 strips clamped together, countersink the holes if required by the screws you are using, then weld up the stack using cast-off hard drives screwed through these holes in 2 or 3 places, to obtain correct alignment of all the pieces and above all the drive fixing holes. I keep a set of terminally failed old heavy 3 1/2″ drives for just this purpose.

I did not want 2 large fans roaring away continually. Besides that, some powered coolers will not physically fit into such a moderate size case anyway. I therefore used 2 passive cooling radiators attached to 2 steel mounting strips, as no mounting hardware came with the radiators, These strips were cut to shape as necessary to clear board components, then drilled, countersunk and threaded to attach to the mainboard cooler fixing holes, using 1/4″ spacers and countersunk 4×0.7mm screws, and tapped 4×0.7mm to receive the selected cooling radiators mounting screws. Some very careful marking and drilling was required at this stage. These radiators are large finned sheet metal assemblies and the memory slots are very close at top and bottom, but there is just clearance enough for DDR3 ECC REG memory with cooling sleeves. I decided on heavy copper 8mm thick heat sinks made from 40mm x 4mm solid copper strip, screwed together with conductive gel, then squeezed between these radiators and the cpu tops. The radiator fixing screws are lightly spring loaded to keep the heat sinks in place, assisted by a coat of conductive gel on all contact surfaces.

To start with I used 2 matched very cheap Xeon 4-core cpus cast off from old servers running at 2400mhz, intending to move up to faster ones later, if appropriate. DDR3 Server ECC REG ram is required for these boards, I used 4 x 8gb dimm with cooling sleeves, again cast off from old servers. A 16-lane PCIe graphics card from my junk box, a new SATA-3 DVD/RW in the top bay, a new media device reader in the half length bay, a new PCIe Wlan and Bluetooth card, a new 6-port SATA expansion card and a new modular 750w power supply completed the components. The 4 hard drives, DVD/RW and Media device reader took up 7 SATA ports so I installed a 4-port SATA expansion card to bring the SATA2 and SATA3 combined total to 10.

The modular power supply is almost a necessity as the case is now crowded with components, and this power unit permitted only the necessary looms to be present and to be most neatly routed. A bifurcated cpu power cable was also required as only one cpu 8-pin power cable came with the psu. 4 x 500gb 3.5″ new SATA-3 hard drives were fitted into the HD stack. Later I may put a 250gb solid disk in the spare hard drive bay as a boot disk.

There is no onboard default graphics chipset but an onboard sound chipset is present, and there are 2xPCIe 16-lane slots and 2xPCIe 1 -lane slots, 2xSATA-3 and 4xSATA-2 ports and a PCIe-1 SATA expansion card provides 4 extra SATA-3 ports. There are 2 fast network ports and the associated chipsets onboard. USB 2.1 and USB 3.0 ports abound internally and externally. There are even the now mainly unwanted PS/2 keyboard and mouse ports.

I installed a small case fan and also fitted a small fan arranged to blow through the hard drive stack, besides the power supply internal fan.

A coat of paint inside and out before final assembly completed the hardware aspect of this project.

The build fired up immediately and ran well allowing installation and updating of 19.2 in the first instance. Following installation antiX support advised that a different kernel was required as I experienced random freezing, so a fresh install of 19.3 with kernel 4.19.152 and using only Ceni to handle networking, has cured that trouble, and I am now setting things up as I prefer them. After a 2-hour run cpu temperature hovers around 48C-52C which sounds high but appears to cause no trouble – so far. This PC is not quite silent having 3 fans but is a much appreciated very quiet PC.

It runs very fast, I have not done enough with it yet to appreciate quite fast, and my other old slow PCs make poor comparison material. But the usual bottlenecks of networking and plug-in external devices are still there to hold things up somewhat.

I hope this build description will be of help to any antiX user wishing to build a similar PC, good luck to all experimenters!

Attachments:

1. 

   DSC01379.jpg
   

2. 

   DSC01905.jpg
   

3. 

   DSC01955.jpg
   

4. 

   DSC01958.jpg
   

[Moderator Brian Masinick]

Also a reminder that Wifi is usually not “activated” by default in the Connman interface. If you are using the graphical version of Connman make sure that the interface (Ethernet, Bluetooth, or WiFi) that you want to use is enabled. Once the method you are using is enabled, particularly with WiFi and Bluetooth, you should be able to locate the network you want to use.

The tutorial that has been previously shared has all of the details too; I am merely reminding you about this…

--
Brian Masinick

[Member pepitofer]

I have applied this configuration:

Xecure wrote:

[global]
OfflineMode=false
TimeUpdates=manual
TimezoneUpdates=auto

and the NTP traffic is now only coming from the ntpd in a more “relaxed” way.
So the system is still updating the time and the configuration of ntp can be setup to query on a desired basis. I don’t know how to configure this with connman or if it is even possible at all in an easy way.

Before that I tried the UseGatewaysAsTimeservers = false option but it didn’t seem to work as it kept sending traffic to the gateway.

Having ntpd active and the ntp feature in connman seems redundant to me, and in my environment I believe that ntpd is enough.

About having WIFI and Bluetooth activated by default in the liveUSB seems a very good idea in my opinion.

• This reply was modified 2 years, 4 months ago by pepitofer.
• This reply was modified 2 years, 4 months ago by pepitofer. Reason: add info an typos

[Moderator BobC]

PPC, you are correct that the network detection and internet detection are separately called by the startup script. That’s an easy fix.

The autoscale only affects the screen setups on computers with HiDPI displays, but for other computers it will create the folder arandr expects to find and a blank default.sh script that can be overlaid by the user if they want an unusual setup as their default, for example a system with 3 screens needs to know how they are arranged for the mouse to work correctly.

As for internet, there are many ways to connect, as you can see on the cmst screen, they might use their phone or bluetooth i think. In my case, I go someplace and am not connected and it pops up the screen to alert me that I dont have a connection, and I might tether it to my phone if wifi works on the phone but I can’t connect due to some unusal setup. If at home I might plug it in, or connect to a different wifi hub.

Do you think it’s better to pop up a box saying No Internet Connection and offer to connect or cancel? If you want that, I suggest using the text from someplace it already exists if possible. Would we need it to be a separate script to do that translation? It could give Connman (Easy) or Ceni (fallback) as options as well. I was happy with just popping up connman myself, but that might make everyone happier.

I feel really bad every time I see someone who couldn’t get connected complaining on a review or DW, or lost needing help, and even more so when it happens at my bosses house or a friend who I suggested antiX to. I think anti must also get frustrated by those situations, but I don’t speak for him.

[Member ModdIt]

So it seems a number of the connman features listed below are at present unused or even causing some problems.

source: https://git.kernel.org/pub/scm/network/connman/connman.git/about/

The following features are built-in into Connection Manager:
– Generic plugin infrastructure
– Device and network abstraction (with basic storage support)
– IPv4, IPv4-LL (link-local) and DHCP
– IPv4 address conflict detection (ACD) according to RFC 5227
– IPv6, DHCPv6 and 6to4 tunnels
– Advanced routing and DNS configuration
– Built-in DNS proxy and intelligent caching
– Built-in WISPr hotspot logins and portal detection
– Time and timezone configuration (manual and automatic with NTP)
– Proxy handling (manual and automatic with WPAD)
– Tethering support (USB, Bluetooth and WiFi AP mode)
– Detailed statistics handling (home and roaming)

Various plugins can be enabled for networking support:
– Ethernet plugin
– WiFi plugin with WEP40/WEP128 and WPA/WPA2 (personal and enterprise)
– Bluetooth plugin (using BlueZ)
– 2G/3G/4G plugin (using oFono)

Also plugins with additional features are available:
– Loopback interface setup
– PACrunner proxy handling
– PolicyKit authorization support
——————————————————————————————
#Regarding: Except if there is something really wrong with the computer (or you need some software to be in perfect sync with time),
calling the ntp server for updating the time once a day is more than enough (I would even argue once a week is more than enough).
Once a minute is overkill. Once an hour is good for people who need it.

Standard for NTP: as below, from https://linux.die.net/man/8/ntpd
according to the manpage the polling interval can be increased but that can be detrimental. For sure connman is at first polling way too often at about 3 seconds.

default, ntpd runs in continuous mode where each of possibly several external servers is polled at
intervals determined by an intricate state machine. The state machine measures the incidental
roundtrip delay jitter and oscillator frequency wander and determines the best poll interval using a
heuristic algorithm. Ordinarily, and in most operating environments, the state machine will start
with 64s intervals and eventually increase in steps to 1024s. A small amount of random variation is
introduced in order to avoid bunching at the servers. In addition, should a server become unreachable
for some time, the poll interval is increased in steps to 1024s in order to reduce network overhead.

[Anonymous]

found via forum search “rtl8723bs” :

https://www.antixforum.com/forums/topic/backported-firmware-nonfree-from-debian-sid-testers-needed/

After many months, I finally got my bluetooth to work on my cheap chinese tablet. But the firmware I needed wasn’t included in the firmware-realtek package.
Could you ask the MX team if they can include rtl8723bs_config-OBDA8723.bin and rtl8723bs_fw.bin in the next firmware-realtek package version? I just tested them and they work (finally I have bluetooth on my cherrytrail tablet!).

[Member ModdIt]

Hi PPC, some old tabs can share a connection with a developer options setting, I guess you already checked
though..

OT here, but with many tabs a bluetooth portable keyboard can be used.

I have one small keyboard from CSL, up to now it works on almost all the devices I have tried it with.
Exception, Rotten fruit ones. Android fine.

My tab is an anchient Ployer Momo 11 i imported from China. Case is disentegrating, historic android 4.4.
Excellent HiRes screen. Rarely used now.

• This reply was modified 2 years, 5 months ago by ModdIt.

[Member lgj100]

Hi,

This is what I had to do in order to get pairing to work:

PC PRE REQUISITES
Install bluetooth packages, including:
bluez
blueman
pulseaudio-module-bluetooth package

START NECESSARY SOFTWARE ON PC
(1) sudo /etc/init.d/bluetooth start (start bluetooth)
(2) open connman and turn on bluetooth
(3) pulseaudio –start (to start pulseaudio)
(4) open blueman under “Adapters” check that “Always visible” is checked.

PAIRING
In blueman, pair/connect as necessary using “Setup” or “Setup New Device”

Lars.

[Member Xecure]

To get bluez to talk to alsa (and vice-versa) you need a package named bluealsa that isn’t included in any Debian derivative I know (nor Debian official repos), because “everyone” now uses pulseaudio.
If you can compile it yourself, you can use it. https://github.com/Arkq/bluez-alsa

The alternative is installing pulseaudio with bluetooth module. That is the path I had to follow, the same as roky mentions.

Xecure wrote:

Getting pulseaudio in your system:

1. Installing pulseaudio:
Open a terminal and execute
sudo apt update && sudo apt-get install pulseaudio pavucontrol pulseaudio-module-bluetooth

2. Make pulseaudio launch on startup
Edit startup file
geany ~/.desktop-session/startup
Uncomment the line related to pulseaudio. It should look like this:

# Uncomment if using pulseaudio (you need to install it)
pulseaudio -D &

Save and exit

3. Making volume-icon use pulseaudio (and manage volume and properties)
right-click the volume icon in your systray and click on Preferences.
Have External mixer execute pavucontrol. It originally says:
External mixer desktop-defaults-run -t alsamixer
Replace it with:
External mixer pavucontrol

4. Reboot your system.
From this moment on, pulseaudio will autlaunch on startup.

5. Configure your Bluetooth headphone with pavucontrol.
Launch blueman as you have before (if you have it set to autolaunch even better).
Go to Bluetooth devices (your second image). Remove your headset (HD 4.50BTNC) from the list (right-click and Remove) because you are going to set it up again.
Get your bluetooth headset to search for devices/sync, hit the “Search” button on the Bluetooth Devices window. When it appears on the list, select it and click on “Trust” and then “Pair”. Finally, right-click on it and select “Audio sync”.
Open pavucontrol (right-click volume icon, then select “Open Mixer”). Go to the “Output Devices” tab and make sure pavucontrol can find your headset. Then try playing an audio file or a video and check that the application is outputing sound to the Bluetooth headset (you will be able to see this in the “Playback” tab in pavucontrol).

6. The end

Let us know what path you followed and if it worked for you.

Regards.

• This reply was modified 2 years, 5 months ago by Xecure. Reason: Typos

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