Porteus 5.0 and Bluetooth.

[portypit]

Is Porteus supposed to work with the Bluetooth device in a laptop?
Possibly there is no driver supplied with Porteus.

Having installed Porteus 5.0 onto my laptop, which has a Bluetooth device,
I placed "bluetooth" in /boot/syslinux/porteus.cfg but saw an error message when I clicked on Bluetooth icon on desktop:
"No adapters available".

Windows 8.1 and Ubuntu 14 both work with the device, as I'm able to receive files.

Is it to keep Porteus to the smallest file size possible?

[ncmprhnsbl]

could be missing firmware..
maybe:

Code: Select all

# lspci | grep Bluetooth 

to get an idea of the hardware..
and

Code: Select all

$ getpkg linux-firmware

will get a module of the entire firmware package from slackware( much of which is included in the 000-kernel module already)
another approach could be to try a newer kernel from this topic: Porteus Kernel Builder

[beny]

hi maybe:
/var/log/packages/bluez-5.54-x86_64-1
/var/log/packages/bluez-firmware-1.2-x86_64-2
/var/log/packages/bluez-hcidump-2.5-x86_64-1
/var/log/packages/blueman-2.1.3-x86_64-2

[portypit]

Thanks for the info guys. I will look into that

[rych]

I have 5.0rc3 x64 OpenBox and am trying to connect my BT mouse. I first enabled Bluetooth daemon in Porteus Settings, and then

Code: Select all

root@porteus:~# bluetoothctl 
Agent registered
[CHG] Controller 34:02:86:95:E7:4F Pairable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller 34:02:86:95:E7:4F Discovering: yes
[NEW] Device D4:F0:FA:19:FB:17 BT5.1 Mouse
[bluetooth]# pair D4:F0:FA:19:FB:17 
Attempting to pair with D4:F0:FA:19:FB:17
[CHG] Device D4:F0:FA:19:FB:17 Connected: yes
...
[CHG] Device D4:F0:FA:19:FB:17 ServicesResolved: yes
[CHG] Device D4:F0:FA:19:FB:17 Paired: yes
[BT5.1 Mouse]# paired-devices 
Device D4:F0:FA:19:FB:17 BT5.1 Mouse
[BT5.1 Mouse]# connect D4:F0:FA:19:FB:17 
Attempting to connect to D4:F0:FA:19:FB:17
Connection successful
[BT5.1 Mouse]# trust D4:F0:FA:19:FB:17 
[CHG] Device D4:F0:FA:19:FB:17 Trusted: yes
Changing D4:F0:FA:19:FB:17 trust succeeded
[BT5.1 Mouse]# info D4:F0:FA:19:FB:17 
Device D4:F0:FA:19:FB:17 (random)
	Name: BT5.1 Mouse
	Alias: BT5.1 Mouse
	Appearance: 0x03c2
	Icon: input-mouse
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	WakeAllowed: yes
	LegacyPairing: no
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
	UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (6e40ff01-b5a3-f393-e0a9-e50e24dcca9e)
	Modalias: usb:v32C2p0001d0068
	ManufacturerData Key: 0x0006
	ManufacturerData Value:
  03 00 80                                         ...             
	RSSI: -66
	Battery Percentage: 0x64 (100)
[BT5.1 Mouse]# 

The mouse is not moving the cursor. It's the same mouse I use when I boot into Windows 10 on the same laptop. Something is amiss to tell system it now has a second mouse.

Anyway, I gathered bluetoothctl may not be the right tool for end user, so I did this:

Code: Select all

root@porteus:~# getpkg blueman
...successfully made blueman-2.2.2-x86_64-1.xzm, activated it...
root@porteus:~# /etc/rc.d/rc.bluetooth restart
Starting Bluetooth services:  bluetoothd hciconfig sdptool hciattach
root@porteus:~# blueman-manager
...a void window displayed for a while and closed with a console error:
Blueman applet needs to be running
root@porteus:~# blueman-applet
blueman-applet 21.17.12 ERROR    PluginManager:90 load_plugin: Unable to load plugin module AppIndicator
Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/AppIndicator.py", line 11, in <module>
    require_version('AppIndicator3', '0.1')
  File "/usr/lib64/python3.9/site-packages/gi/__init__.py", line 126, in require_version
    raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace AppIndicator3 not available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/blueman/main/PluginManager.py", line 88, in load_plugin
    importlib.import_module(self.module_path.__name__ + f".{plugin}")
  File "/usr/lib64/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/AppIndicator.py", line 13, in <module>
    raise ImportError("AppIndicator3 not found")
ImportError: AppIndicator3 not found
blueman-applet 21.17.12 WARNING  PluginManager:147 __load_plugin: Not loading DhcpClient because its conflict has higher priority
blueman-applet 21.17.12 WARNING  PluginManager:147 __load_plugin: Not loading PPPSupport because its conflict has higher priority
blueman-applet 21.17.37 ERROR    BasePlugin:83 _load     : Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms)
Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/blueman/main/DBusProxies.py", line 27, in __init__
    self.init()
gi.repository.GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms) (20)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/BasePlugin.py", line 77, in _load
    self.on_load()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/Networking.py", line 28, in on_load
    self.load_nap_settings()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/Networking.py", line 49, in load_nap_settings
    m = Mechanism()
  File "/usr/lib64/python3.9/site-packages/blueman/gobject.py", line 11, in __call__
    cls._instance = super().__call__(*args, **kwargs)
  File "/usr/lib64/python3.9/site-packages/blueman/main/DBusProxies.py", line 34, in __init__
    super().__init__(name='org.blueman.Mechanism', interface_name='org.blueman.Mechanism',
  File "/usr/lib64/python3.9/site-packages/blueman/main/DBusProxies.py", line 29, in __init__
    raise DBusProxyFailed(e.message)
blueman.main.DBusProxies.DBusProxyFailed: Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms)
blueman-applet 21.17.37 ERROR    PluginManager:161 __load_plugin: Failed to load Networking
Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/blueman/main/DBusProxies.py", line 27, in __init__
    self.init()
gi.repository.GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms) (20)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/blueman/main/PluginManager.py", line 159, in __load_plugin
    inst._load()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/AppletPlugin.py", line 51, in _load
    super()._load()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/BasePlugin.py", line 77, in _load
    self.on_load()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/Networking.py", line 28, in on_load
    self.load_nap_settings()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/Networking.py", line 49, in load_nap_settings
    m = Mechanism()
  File "/usr/lib64/python3.9/site-packages/blueman/gobject.py", line 11, in __call__
    cls._instance = super().__call__(*args, **kwargs)
  File "/usr/lib64/python3.9/site-packages/blueman/main/DBusProxies.py", line 34, in __init__
    super().__init__(name='org.blueman.Mechanism', interface_name='org.blueman.Mechanism',
  File "/usr/lib64/python3.9/site-packages/blueman/main/DBusProxies.py", line 29, in __init__
    raise DBusProxyFailed(e.message)
blueman.main.DBusProxies.DBusProxyFailed: Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms)
Traceback (most recent call last):
  File "/usr/lib64/python3.9/site-packages/blueman/main/DBusProxies.py", line 27, in __init__
    self.init()
gi.repository.GLib.Error: g-dbus-error-quark: Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms) (20)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/blueman-applet", line 43, in <module>
    app = BluemanApplet()
  File "/usr/lib64/python3.9/site-packages/blueman/main/Applet.py", line 35, in __init__
    self.Plugins.load_plugin()
  File "/usr/lib64/python3.9/site-packages/blueman/main/PluginManager.py", line 121, in load_plugin
    self.__load_plugin(cls)
  File "/usr/lib64/python3.9/site-packages/blueman/main/PluginManager.py", line 159, in __load_plugin
    inst._load()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/AppletPlugin.py", line 51, in _load
    super()._load()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/BasePlugin.py", line 77, in _load
    self.on_load()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/Networking.py", line 28, in on_load
    self.load_nap_settings()
  File "/usr/lib64/python3.9/site-packages/blueman/plugins/applet/Networking.py", line 49, in load_nap_settings
    m = Mechanism()
  File "/usr/lib64/python3.9/site-packages/blueman/gobject.py", line 11, in __call__
    cls._instance = super().__call__(*args, **kwargs)
  File "/usr/lib64/python3.9/site-packages/blueman/main/DBusProxies.py", line 34, in __init__
    super().__init__(name='org.blueman.Mechanism', interface_name='org.blueman.Mechanism',
  File "/usr/lib64/python3.9/site-packages/blueman/main/DBusProxies.py", line 29, in __init__
    raise DBusProxyFailed(e.message)
blueman.main.DBusProxies.DBusProxyFailed: Error calling StartServiceByName for org.blueman.Mechanism: Failed to activate service 'org.blueman.Mechanism': timed out (service_start_timeout=25000ms)
root@porteus:~# 

So first of all, blueman isn't working for me. Secondly, I only need it if it successfully lets me use my BT mouse and if there is another more promising tool or method, please let me know.

[ncmprhnsbl]

for some crazy reason, blueman in slackware seems to require libappindicator (so: getpkg libappindicator) should fix the first part of the error..
there was also some problem with the daemon, but i think that was more to do with starting at boot..(required a short sleep)
i'll have a closer look tomorrow with bluetooth capable hardware.,

[Bicephale]

Chop! Chop! Chop!

[ncmprhnsbl]

for some crazy reason, blueman in slackware seems to require libappindicator (so: getpkg libappindicator) should fix the first part of the error..

after some tests, it seems this is not so..libappindicator is optional..
blueman seems to start(blueman-manager) and run ok here (running stock RC3 openbox ISO) .. there is however an issue with bluetoothd crashing..
bluez has been updated in slackware a bit lately, so with luck, it might be fixed .. ..further poking required..

[rych]

ncmprhnsbl, now on a fresh reboot, start/restart of the bluetooth daemon, activate/deactivate of
libappindicator-12.10.0-x86_64-3.xzm -- no matter what I get:

Code: Select all

root@porteus:~# blueman-manager 

(blueman-manager:2497): GLib-GIO-ERROR **: 03:40:18.363: Settings schema 'org.blueman.general' is not installed
Trace/breakpoint trap

Is there an alternative to blueman?

[ncmprhnsbl]

(blueman-manager:2497): GLib-GIO-ERROR **: 03:40:18.363: Settings schema 'org.blueman.general' is not installed

that looks like a schema issue.. which should be handled at activation time... try: (as root)

Code: Select all

glib-compile-schemas /usr/share/glib-2.0/schemas

Is there an alternative to blueman?

not really, apart from bluetoothctl ... kde has bluedevil and gnome has it's own set of tools, but neither of those are practical here...
apart from the gui issues, i suggest keeping an eye on the bluetoothd process to see if it's crashing, ie. have lxtask or terminal with top or even `watch pstree` running..
i'll just put this here as a general info/resource: https://wiki.archlinux.org/title/Bluetooth

[beny]

hi ncmprhnsbl if you have bluez bluez-firmware and bluemann and also libappindicator you can do the task:a logitech k400r work like a charm in porteus at boot and have also a touchpad,maybe the dongle don't have a good link to computer ok i have the last version of the bluez and co in porteus 5.ps: my boot is in txt mode so without changes.

[ncmprhnsbl]

thanks beny, sounds like bluez-firmware is the missing piece.. which can also be got from current via getpkg
it's pretty tiny, so might be candidate for inclusion in base/002-xorg..

[francois]

Has there been any advancement on this bluethoot issue. I work with xfce desktop.

In Menu > Settings
I do not see any bluethoot settings.

However according to Fafler I would have bluetooth hardware on my linux box:
https://ubuntuforums.org/showthread.php?t=1135556

Code: Select all

root@porteus:/home/guest# dmesg | grep -i blue
[    2.131934] toshiba_bluetooth: Toshiba ACPI Bluetooth device driver
[    4.174479] Bluetooth: Core ver 2.22
[    4.174497] NET: Registered PF_BLUETOOTH protocol family
[    4.174499] Bluetooth: HCI device and connection manager initialized
[    4.174737] Bluetooth: HCI socket layer initialized
[    4.174740] Bluetooth: L2CAP socket layer initialized
[    4.174745] Bluetooth: SCO socket layer initialized
[    4.195891] Bluetooth: hci0: unexpected event for opcode 0x0000
root@porteus:/home/guest# 

Code: Select all

root@porteus:/home/guest# lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
01:00.0 System peripheral: Ricoh Co Ltd PCIe SDXC/MMC Host Controller (rev 07)
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
root@porteus:/home/guest# 

Code: Select all

root@porteus:/home/guest# lsusb
Bus 002 Device 002: ID 8087:0024  
Bus 002 Device 001: ID 1d6b:0002 Linux 5.18.8-porteus ehci_hcd EHCI Host Controller
Bus 001 Device 003: ID 04f2:b369 Chicony Electronics Co.,Ltd. TOSHIBA Web Camera - HD
Bus 001 Device 004: ID 8087:07da  
Bus 001 Device 002: ID 8087:0024  
Bus 001 Device 001: ID 1d6b:0002 Linux 5.18.8-porteus ehci_hcd EHCI Host Controller
Bus 004 Device 001: ID 1d6b:0003 Linux 5.18.8-porteus xhci-hcd xHCI Host Controller
Bus 003 Device 002: ID 046d:c52b Logitech USB Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux 5.18.8-porteus xhci-hcd xHCI Host Controller
root@porteus:/home/guest# 

Thanks.

[beny]

hi, sh '/etc/rc.d/rc.bluetooth' start
Starting Bluetooth services: bluetoothd hciconfig sdptool hciattach
and you have this:
bash-5.2# dmesg | grep -i blue
[ 7.760647] Bluetooth: Core ver 2.22
[ 7.760757] NET: Registered PF_BLUETOOTH protocol family
[ 7.760826] Bluetooth: HCI device and connection manager initialized
[ 7.760901] Bluetooth: HCI socket layer initialized
[ 7.760971] Bluetooth: L2CAP socket layer initialized
[ 7.761043] Bluetooth: SCO socket layer initialized
[ 8.025220] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=6 rev=22bb; LMP ver=6 subver=22bb; manufacturer=10
[ 3135.605410] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3135.605417] Bluetooth: BNEP filters: protocol multicast
[ 3135.605423] Bluetooth: BNEP socket layer initialized
[ 3135.607365] Bluetooth: MGMT ver 1.22
[ 3135.889046] Bluetooth: RFCOMM TTY layer initialized
[ 3135.889056] Bluetooth: RFCOMM socket layer initialized
[ 3135.889063] Bluetooth: RFCOMM ver 1.11
if you do not have kde blueman is the software but you have to load it via terminal,also bluetoothctl help you for debug and also btmon. but if you start bluetooth daemon you have the blueman-manager on the tray

[francois]

Then as proposed by beny:

Code: Select all

root@porteus:/home/guest#  sh '/etc/rc.d/rc.bluetooth' start
Starting Bluetooth services:  bluetoothd hciconfig sdptool hciattach
root@porteus:/home/guest# 

Then I got a prompt:
Should bluetooth start automatically:
yes.

Thanks beny.