Bluetooth in Porteus 5.0rc3 XFCE

[rchase]

(On a 2008 iMac) the bluetooth module ncmprhnsbl prepared for Porteus 5.0rc1 XFCE (viewtopic.php?t=8804) no longer works; after activating it, "bluetooth-adapters" and "bluetooth-manager" return "Failed to execute command ... (No such file or directory"; I noticed that bluez was not loaded and included a Porteus module of bluez-firmware with no change. I see no reference to bluetooth in the output of "lspci -knn":

Code: Select all

root@porteus:~# lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel modules: intel_agp
00:01.0 PCI bridge [0604]: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port [8086:2a01] (rev 03)
	Kernel driver in use: pcieport
00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 04)
	Kernel driver in use: uhci_hcd
00:1a.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: uhci_hcd
00:1a.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 04)
	Kernel driver in use: pcieport
00:1c.3 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 [8086:2845] (rev 04)
	Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 [8086:2847] (rev 04)
	Kernel driver in use: pcieport
00:1c.5 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 [8086:2849] (rev 04)
	Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: uhci_hcd
00:1d.1 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: uhci_hcd
00:1d.2 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: uhci_hcd
00:1d.7 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 [8086:2836] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: ehci-pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f4)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801HM (ICH8M) LPC Interface Controller [8086:2815] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.1 IDE interface [0101]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: ata_piix
00:1f.2 SATA controller [0106]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) SMBus Controller [8086:283e] (rev 04)
	Subsystem: Apple Inc. Device [106b:00a0]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV610/M74 [Mobility Radeon HD 2400 XT] [1002:94c8]
	Subsystem: Apple Inc. Device [106b:0084]
	Kernel driver in use: radeon
	Kernel modules: radeon
03:00.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW643 [TrueFire] PCIe 1394b Controller [11c1:5901] (rev 06)
	Subsystem: LSI Corporation FW643 [TrueFire] PCIe 1394b Controller [11c1:5900]
	Kernel driver in use: firewire_ohci
	Kernel modules: firewire_ohci
04:00.0 Network controller [0280]: Broadcom Corporation BCM4321 802.11a/b/g/n [14e4:4328] (rev 05)
	Subsystem: Apple Inc. AirPort Extreme [106b:008c]
	Kernel driver in use: b43-pci-bridge
	Kernel modules: ssb
05:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8058 PCI-E Gigabit Ethernet Controller [11ab:436a] (rev 13)
	Subsystem: Marvell Technology Group Ltd. Imac 8,1 Wired Ethernet Adapter [11ab:00ba]
	Kernel driver in use: sky2
	Kernel modules: sky2
root@porteus:~# 

lsmod:

Code: Select all

root@porteus:~# lsmod
Module                  Size  Used by
ccm                    16384  6
rfcomm                 32768  4
bnep                   16384  2
b43                   360448  0
cordic                 12288  1 b43
uvcvideo               81920  0
bcma                   32768  1 b43
videobuf2_vmalloc      12288  1 uvcvideo
videobuf2_memops       12288  1 videobuf2_vmalloc
videobuf2_v4l2         20480  1 uvcvideo
mac80211              356352  1 b43
videobuf2_common       32768  4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
btusb                  45056  0
btrtl                  12288  1 btusb
btbcm                  12288  1 btusb
btintel                20480  1 btusb
hid_appleir            12288  0
bluetooth             327680  27 btrtl,btintel,btbcm,bnep,btusb,rfcomm
cfg80211              274432  2 b43,mac80211
input_leds             12288  0
ecdh_generic           12288  1 bluetooth
ecc                    20480  1 ecdh_generic
rfkill                 20480  4 bluetooth,cfg80211
libarc4                12288  1 mac80211
rng_core               12288  1 b43
applesmc               16384  0
coretemp               12288  0
kvm_intel             167936  0
kvm                   356352  1 kvm_intel
radeon               1101824  10
irqbypass              12288  1 kvm
firewire_ohci          36864  0
i2c_i801               24576  0
snd_hda_codec_realtek    98304  1
snd_hda_codec_generic    53248  1 snd_hda_codec_realtek
ledtrig_audio          12288  1 snd_hda_codec_generic
led_class              12288  4 snd_hda_codec_generic,b43,input_leds,applesmc
firewire_core          49152  1 firewire_ohci
lpc_ich                24576  0
ssb                    53248  1 b43
snd_hda_intel          28672  0
snd_intel_dspcfg       12288  1 snd_hda_intel
snd_hda_codec          81920  3 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_realtek
pcmcia                 36864  1 ssb
crc_itu_t              12288  1 firewire_core
drm_ttm_helper         12288  1 radeon
snd_hda_core           45056  4 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
pcmcia_core            16384  1 pcmcia
sky2                   49152  0
ttm                    45056  2 radeon,drm_ttm_helper
snd_hwdep              12288  1 snd_hda_codec
snd_pcm                65536  3 snd_hda_intel,snd_hda_codec,snd_hda_core
intel_agp              16384  0
snd_timer              24576  1 snd_pcm
apple_bl               12288  0
intel_gtt              16384  1 intel_agp
acpi_cpufreq           12288  1
ipv6                  323584  138
hfsplus                86016  2
root@porteus:~# 

I'll try KDE, but I'd like a bluetooth module for XFCE.

[beny]

hi rchase terminal rfkill list show you if the bluetooth is on or off, hardware side

[rchase]

Code: Select all

root@porteus:~# rfkill list
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
root@porteus:~# 

It doesn't indicate whether the daemon is running, but the graphical daemon control says it is. In the meantime, I can't boot a copy of Porteus 5.0rc3 KDE off the same hard drive as XFCE no matter what I do. I'll prepare a copy on a gpt-formatted flash drive and try to load it with Apple's firmware, but I'd love to know why I can boot one copy of Porteus but not another.

[beny]

hi try to load the daemon manually:bluetoothctl is a powerfull tool to debug and run bluetooth, bluetoothctl --help show you what you can do with....try it

Code: Select all

  
bash-5.1# sh '/etc/rc.d/rc.bluetooth' start
Starting Bluetooth services:  bluetoothd hciconfig sdptool hciattach
bash-5.1# bluetoothctl
Agent registered
[bluetooth]# list
Controller 00:1A:7D:DA:71:0D BlueZ 5.63 [default]
[bluetooth]# devices
Device FC:D9:08:00:66:6D POCO X3 Pro
[bluetooth]# scan
Missing on/off argument
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:0D Discovering: yes
[NEW] Device 45:A6:9F:FF:52:5D 45-A6-9F-FF-52-5D
[bluetooth]#

[rchase]

Code: Select all

root@porteus:/etc/rc.d# sh rc.bluetooth start
Starting Bluetooth services:  bluetoothd hciconfig sdptool hciattach
D-Bus setup failed: Name already in use
root@porteus:/etc/rc.d# 

[rchase]

Sorry, I only issued one command:

Code: Select all

root@porteus:~# cd /etc/rc.d
root@porteus:/etc/rc.d# sh rc.bluetooth start
Starting Bluetooth services:  bluetoothd hciconfig sdptool hciattach
D-Bus setup failed: Name already in use
root@porteus:/etc/rc.d# bluetoothctl
Agent registered
[CHG] Controller 00:1F:F3:AD:E1:64 Pairable: yes
[bluetooth]# list
Controller 00:1F:F3:AD:E1:64 BlueZ 5.59 [default]
[bluetooth]# devices
[bluetooth]# scan
Missing on/off argument
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1F:F3:AD:E1:64 Discovering: yes
[NEW] Device 00:00:00:00:00:00 00-00-00-00-00-00
[NEW] Device F8:8A:3C:35:2D:83 Mpow X3
[bluetooth]#

So bluletooth is apparently functioning, but not the interface -- both bluetooth-adapters and bluetooth-manager return "Failed to execute command ...".

[beny]

hi try if pair and connect work and there is also trust command
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:0D Discovering: yes
[NEW] Device 40:42:35:98:4B:53 40-42-35-98-4B-53
[bluetooth]# pair
Missing device address argument
[bluetooth]# pair 40:42:35:98:4B:53
Attempting to pair with 40:42:35:98:4B:53
[CHG] Device 40:42:35:98:4B:53 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationTimeout
[CHG] Device 40:42:35:98:4B:53 Connected: no
[bluetooth]# connect 40:42:35:98:4B:53
Attempting to connect to 40:42:35:98:4B:53
[CHG] Device 40:42:35:98:4B:53 Connected: yes

[rchase]

Code: Select all

root@porteus:/etc/rc.d# sh rc.bluetooth start
Starting Bluetooth services:  bluetoothd hciconfig sdptool hciattach
root@porteus:/etc/rc.d# bluetoothctl
Agent registered
[CHG] Controller 00:1F:F3:AD:E1:64 Pairable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1F:F3:AD:E1:64 Discovering: yes
[NEW] Device F8:8A:3C:35:2D:83 Mpow X3
[bluetooth]# pair F8:8A:3C:35:2D:83
Attempting to pair with F8:8A:3C:35:2D:83
[CHG] Device F8:8A:3C:35:2D:83 Connected: yes
[CHG] Device F8:8A:3C:35:2D:83 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device F8:8A:3C:35:2D:83 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device F8:8A:3C:35:2D:83 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device F8:8A:3C:35:2D:83 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device F8:8A:3C:35:2D:83 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device F8:8A:3C:35:2D:83 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device F8:8A:3C:35:2D:83 UUIDs: 8a482a08-5507-42ac-b673-a88df48b3fc7
[CHG] Device F8:8A:3C:35:2D:83 ServicesResolved: yes
[CHG] Device F8:8A:3C:35:2D:83 Paired: yes
Pairing successful
[CHG] Device F8:8A:3C:35:2D:83 ServicesResolved: no
[CHG] Device F8:8A:3C:35:2D:83 Connected: no
[CHG] Device F8:8A:3C:35:2D:83 RSSI: -69
[CHG] Device F8:8A:3C:35:2D:83 RSSI: -55
[bluetooth]# pair F8:8A:3C:35:2D:83
Attempting to pair with F8:8A:3C:35:2D:83
Failed to pair: org.bluez.Error.AlreadyExists
[CHG] Device F8:8A:3C:35:2D:83 RSSI: -64
[bluetooth]# 

[beny]

hi rchase follow the next step: trust your device and connect your device,maybe the porteus5 bluez version starting to be old but the bluetoothctl is a good tool to debug and run device in a separate xfce-terminal type bluetoothctl --help to reference.

[ncmprhnsbl]

the bluetooth module ncmprhnsbl prepared for Porteus 5.0rc1 XFCE (viewtopic.php?t=8804) no longer works;

yep, bluetoothctl is probly the best way..
but if you want blueman, one these packages from around the time rc3 was released:
https://slackware.uk/cumulative/slackwa ... 6_64-5.txz (2021-02-13)
https://slackware.uk/cumulative/slackwa ... 6_64-1.txz (2021-06-06)
should work..
just rclick>convert txz to xzm(sic)

[rchase]

I successively txz2dir(ed) bluez-firmware, bluez, and blueman together and dir2txz(ed) the result -- the module seem to work. I'll post it under modules.