- This topic has 30 replies, 5 voices, and was last updated Oct 6-11:25 am by caprea.
- Posts
sisqonrw
Hi,
i want to use the last Antix version. i have boot with a live usb Stick.sadly i can not connect with my bluetooth dongel to my bluetooth headset.
i boot for few minutest with Emmabuntüs Version 4 Live USB Stick. The Bluetooth connection works immediately. A photo is attached. Everything is perfect. The music plays immediately via Bluetooth headphones without any problems.
Everything is the same. Same notebook, headphones, Bluetooth dongle. Everything is the same. Only that it does not work on Antix.
Error Report is also in the attachment.
what can be the problem?
What can i do?
Attachments:
Here the translation of the error report.
Connection to Bluez failed
blueman-manager cannot continue because the Bluez service is not active.
This probably means that no Bluetooth adapters were detected or the Bluetooth service was not started.
capreaYou can help us helping you by posting the output of
inxi -FxzSo we can see which version of antiX, full or base, runit or sysvinit, you have installed .
The bluetooth service needs to be enabled. Please go to the control-centre > system > choose startup-services
and enable the service.We can describe details if we know which version is installed.
You mightalso have to enable it in connman (under Status tab)
control-centre- > network > wifi connect connmanHi the bluetooth service is enabled on connman. it it green color.
her the result.
inxi -Fxz
System:
Kernel: 5.10.188-antix.1-486-smp arch: i686 bits: 32 compiler: gcc v: 13.2.0
Desktop: IceWM v: 3.4.1 Distro: antiX-23-runit_386-full Arditi del Popolo
26 August 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Kvm System: Acer product: Aspire 5670 v: N/A
serial: <superuser required>
Mobo: Acer model: Bodensee serial: <superuser required> BIOS: Acer
v: 0.3209 date: 12/21/05
Battery:
ID-1: BAT1 charge: 0.2 Wh (0.0%) condition: 953.5/71.0 Wh (1342.2%)
volts: 0.0 min: 14.8 model: SONY ZB01 status: charging
CPU:
Info: dual core model: Intel T2300 bits: 32 type: MCP arch: M Yonah rev: 8
cache: L1: 128 KiB L2: 2 MiB
Speed (MHz): avg: 1208 high: 1416 min/max: 1000/1667 cores: 1: 1000
2: 1416 bogomips: 6667
Flags: ht nx pae sse sse2 sse3 vmx
Graphics:
Device-1: AMD RV515/M54 [Mobility Radeon X1400]
vendor: Acer Incorporated ALI driver: radeon v: kernel arch: Rage-7
bus-ID: 01:00.0
Display: server: X.Org v: 1.21.1.7 driver: X: loaded: radeon
unloaded: fbdev,modesetting,vesa dri: r300 gpu: radeon
resolution: 1280×800~60Hz
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: ATI RV515 direct-render: Yes
Audio:
Device-1: Intel NM10/ICH7 Family High Definition Audio
vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel
bus-ID: 00:1b.0
Sound API: ALSA v: k5.10.188-antix.1-486-smp running: yes
Sound Server-1: PipeWire v: 0.3.65 running: yes
Network:
Device-1: Intel PRO/Wireless 3945ABG [Golan] Network driver: iwl3945
v: in-tree:s bus-ID: 03:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Broadcom NetLink BCM5789 Gigabit Ethernet PCI Express
vendor: Acer Incorporated ALI driver: tg3 v: kernel port: N/A
bus-ID: 04:00.0
IF: eth0 state: down mac: <filter>
Bluetooth:
Device-1: National Bluetooth Device type: USB driver: btusb v: 0.8
bus-ID: 3-1:4
Report: hciconfig ID: hci0 rfk-id: 4 state: down bt-service: disabled
rfk-block: hardware: no software: no address: <filter>
Drives:
Local Storage: total: 191.81 GiB used: 27.1 MiB (0.0%)
ID-1: /dev/sda vendor: Seagate model: ST98823AS size: 74.53 GiB
ID-2: /dev/sdb type: USB vendor: Transcend model: JetFlash 128GB
size: 117.28 GiB
Partition:
Message: No partition data found.
Swap:
ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) dev: /dev/sda2
Sensors:
System Temperatures: cpu: 52.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 180 Uptime: 2h 20m Memory: 2.95 GiB used: 911.9 MiB (30.2%)
Init: runit runlevel: 2 Compilers: gcc: 12.2.0 Packages: 1671 Shell: Bash
v: 5.2.15 inxi: 3.3.25- This reply was modified 2 months ago by sisqonrw.
- This reply was modified 2 months ago by sisqonrw.
Attachments:
abc-nix
Hi the bluetooth service is enabled on connman.
On connman, you see the bluetooth “technology” enabled, but this doesn’t enable the service.
On live-USB, antiX defaults to disabling many services for a faster boot. I assume this helps booting for older and slower systems.
That is why caprea said:The bluetooth service needs to be enabled. Please go to the control-centre > system > choose startup-services
<—– IGNORE FOR RUNIT EDITION —->
If the choose startup services console app seems too complicated, you can also manually enable the bluetooth service with
sudo service bluetooth start
and add it to automatically start with
sudo update-rc.d bluetooth defaults
And then bluez should work.
<—– IGNORE FOR RUNIT EDITION —->If I am not mistaken, the bluetooth service is disabled by the “disable” boot parameter (not only bluetooth, but a few other services too). This only applies to live-USB. We can deal with this issue later once you can get bluetooth working.
- This reply was modified 2 months ago by abc-nix. Reason: better structure
- This reply was modified 2 months ago by abc-nix. Reason: ignore for runit
capreaPlease also enable it in control-centre > system > choose startup-services
Bluetooth needs to be added to the services by the “add” button
On an installed system this changes would stick but on live not.Or try the way abc-nix suggested.
thanks i have add it and restart it.
i am searching after the headset sadly he do not find it.
i have RUNIT EDITION i ignore the other thinks
- This reply was modified 2 months ago by sisqonrw.
Attachments:
PPC
A couple of years ago I tested the bluetooth dongle my brother gave me in antiX. I did not work.
I tested it again, after reading this thread.- I’m not posting details because, for now, I do not want to waste more time on this problem, but it still fails to work after the recommended steps. I’m using antiX 23 full, sysv, 64bits, kernel 6.1, so:
– I enabled BT via the terminal as shown above
– I enabled bluetooth on connman (it’s “green” reported as powered on, but reported as not connected, on the 4th column)
– On the terminal, running “service bluetooth status” reports that “bluetooth is running”.
– running “blueman-applet” puts the BT applet on the system tray, like in any modern OS
– When I right click the applet, it shows Bluetooth is on. so I set it to always visible… so far so good…
– BUT, when I try to connect to my android phone and then to my bt earbuds, nothing is detected (not even some nearby device my phone picks up). my android phone also does not pick up my computer as a BT device…So, the bluetooth dongle seems to be detected, but fails to work… At least this was my experience up to here.
P.
As I said, a few hours ago I booted up Debian version 4 with Emmabuntüs using a USB iso live stick.
Everything worked there. Dongle was able to connect to headset immediately without any problems. This is not a hardware problem.Everything worked there.
You already explaind that BT works on a different OS, so it’s cleary a problem with antiX. Please wait while folks here try to figure out what the problem may be and help you out.
Unfortunatly, for me, BT was the only thing I never ever was able to get to work on antiX. As far as I checked today, antiX even comes, out of the box with “firmware-realtek” package, that was reported over the internet to be something that Debian 12 required to connect to (at least some) BT devices… There’s probably a small detail missing, in antiX (let’s hope it’s not a big problem, like something Kernel related, etc).
Have patience, antiX is a tiny team, not a huge Company, like the one that created Ubuntu…
anticapitalistaEmmabuntüs Version 4 is based on Debian 11 while antiX-23 is based on Debian 12 so it is not the same.
Did you use the 32bit version of Emmabuntüs Version 4?Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Not sure about antiX 32 bits, but bluetooth does work with same kernel in 64 bits. This is also from live-usb with no changes nor updates.
I understand your processor is 32-bits only, and mine is 64, so really not comparable. I just wanted to post to give contrast that bluetooth can work on antiX 23.
i have use the 32 Bit Version of Emmabuntüs. I use only 32 Bit because my notebook is old. i am using Antix 32 Bit also.
- This reply was modified 2 months ago by sisqonrw.
Just in case it’s usefull, my inxi info (it’s BT 1.1, so really old – are modern devices backwards compatible?… able to connect to older BT versions?):
inxi -Eaz -S System: Kernel: 5.10.188-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 parameters: lang=pt_PT lang=pt_PT quiet splasht Desktop: IceWM v: 3.4.2 vt: 7 dm: slimski v: 1.5.0 Distro: antiX-23_x64 bookworm outubro 02 2023 base: Debian GNU/Linux 12 (bookworm) Bluetooth: Device-1: Roper Class 1 Bluetooth Dongle type: USB driver: btusb v: 0.8 bus-ID: 4-2:2 chip-ID: 1310:0001 class-ID: e001 serial: <filter> Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 1.1 lmp-v: 1.2 sub-v: 757 hci-v: 1.2 Info: acl-mtu: 120:20 sco-mtu: 0:0 link-mode: peripheral accept- This reply was modified 1 month, 4 weeks ago by PPC.
In terminal, check to see if bluetoothctl (the terminal interface for bluetooth) can detect and scan for devices.
To list controller devices:
bluetoothctl list
If no devices are listed, then bluez is not working properly.To scan for other devices:
bluetoothctl scan on
You can exit scanning with Control+CIf no devices are detected, then scanning isn’t working.
I don’t have much experience with bluetoothctl, so this is as far as I can go. At least scanning should also add devices to bluez Manager to be selected.
- You must be logged in to reply to this topic.