Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post here if you are a new Porteus member and you're looking for some help.
supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#1 by supertabs » 14 Dec 2024, 05:13

Hello everyone, need some help here.
I'm using Porteus 5.01 Xfce 64bit.
I have some bluetooth devices and I want to connect to it.
Unfortunately I always get this message: Connection Failed: br-connection-profile-unavailable

I have installed this packages:
- blueman
- bluez
- bluez-firmware
- bluez-qt
Those who win the race are those who are slow and steady. :happy62:

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 4160
Joined: 20 Mar 2012, 03:42
Distribution: v5.0-64bit
Location: australia
Contact:

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#2 by ncmprhnsbl » 14 Dec 2024, 07:50

supertabs wrote:
14 Dec 2024, 05:13
I have installed this packages:
those packages are already present in 002-xorg(bluez*) and 003-xfce4(blueman) so shouldn't be necessary.
are you using the bluetooth cheatcode? (on the APPEND line of /boot/sysliunx/porteus.cfg)
otherwise it could be missing kernel firmware
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#3 by supertabs » 14 Dec 2024, 08:30

ncmprhnsbl wrote:
14 Dec 2024, 07:50
are you using the bluetooth cheatcode
I am not sure what you meant about bluetooth cheatcode.
ncmprhnsbl wrote:
14 Dec 2024, 07:50
it could be missing kernel firmware
So how to fix it? What should I install or do?
Those who win the race are those who are slow and steady. :happy62:

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#4 by supertabs » 14 Dec 2024, 08:47

Tried the bluetooth cheatcode, still the same message Connection Failed: br-connection-profile-unavailable
Those who win the race are those who are slow and steady. :happy62:

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#5 by supertabs » 14 Dec 2024, 10:07

Code: Select all

root@porteus:~# hciconfig -a
hci0:	Type: Primary  Bus: USB
	BD Address: E0:2A:82:CB:3C:06  ACL MTU: 1021:8  SCO MTU: 64:1
	UP RUNNING PSCAN 
	RX bytes:3734 acl:11 sco:0 events:98 errors:0
	TX bytes:4007 acl:11 sco:0 commands:84 errors:0
	Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH HOLD SNIFF PARK 
	Link mode: PERIPHERAL ACCEPT 
	Name: 'BlueZ 5.71'
	Class: 0x10010c
	Service Classes: Object Transfer
	Device Class: Computer, Laptop
	HCI Version: 2.1 (0x4)  Revision: 0x132
	LMP Version: 2.1 (0x4)  Subversion: 0x4203
	Manufacturer: Broadcom Corporation (15)

root@porteus:~# lsmod | grep btusb
btusb                  61440  0
btrtl                  24576  1 btusb
btbcm                  20480  1 btusb
btintel                45056  1 btusb
bluetooth             655360  35 btrtl,btintel,btbcm,bnep,btusb,rfcomm
root@porteus:~# dmesg | grep -i bluetooth
[    0.000000] Command line: BOOT_IMAGE=/boot/syslinux/vmlinuz changes=/porteus bluetooth initrd=/boot/syslinux/initrd.xz
[    0.030629] Kernel command line: quiet BOOT_IMAGE=/boot/syslinux/vmlinuz changes=/porteus bluetooth initrd=/boot/syslinux/initrd.xz
[    0.030692] Unknown kernel command line parameters "bluetooth BOOT_IMAGE=/boot/syslinux/vmlinuz changes=/porteus", will be passed to user space.
[    2.380985]     bluetooth
[   13.822752] Bluetooth: Core ver 2.22
[   13.822784] NET: Registered PF_BLUETOOTH protocol family
[   13.822786] Bluetooth: HCI device and connection manager initialized
[   13.822792] Bluetooth: HCI socket layer initialized
[   13.822795] Bluetooth: L2CAP socket layer initialized
[   13.822798] Bluetooth: SCO socket layer initialized
[   16.221029] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   16.221036] Bluetooth: BNEP filters: protocol multicast
[   16.221042] Bluetooth: BNEP socket layer initialized
[   16.222618] Bluetooth: MGMT ver 1.22
[   27.557845] Bluetooth: RFCOMM TTY layer initialized
[   27.557859] Bluetooth: RFCOMM socket layer initialized
[   27.557866] Bluetooth: RFCOMM ver 1.11
Those who win the race are those who are slow and steady. :happy62:

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#6 by supertabs » 14 Dec 2024, 10:13

Code: Select all

root@porteus:~# bluetoothctl show
Controller E0:2A:82:CB:3C:06 (public)
	Manufacturer: 0x000f (15)
	Version: 0x04 (4)
	Name: BlueZ 5.71
	Alias: BlueZ 5.71
	Class: 0x0010010c (1048844)
	Powered: yes
	Discoverable: no
	DiscoverableTimeout: 0x000000b4 (180)
	Pairable: yes
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0547
	Discovering: no
I have tried downloading broadcom bt firmware but still the same happens.
Those who win the race are those who are slow and steady. :happy62:

User avatar
Blaze
DEV Team
DEV Team
Posts: 3962
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#7 by Blaze » 14 Dec 2024, 11:20

Hi supertabs,
can you share log of these commands:

Code: Select all

su
toor
chmpd +x /etc/rc.d/rc.bluetooth
/etc/rc.d/rc.bluetooth start
blueman-manager
cat /proc/cmdline
dmesg | egrep -i 'blue|fw|firmware|fail|error|warn|found'
?
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#8 by supertabs » 14 Dec 2024, 11:29

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# chmod +x /etc/rc.d/rc.bluetooth 
root@porteus:/home/guest# /etc/rc.d/rc.bluetooth start
Starting Bluetooth services:  bluetoothd hciconfig sdptool hciattach
D-Bus setup failed: Name already in use
root@porteus:/home/guest# blueman-
blueman-adapters  blueman-manager   blueman-services  
blueman-applet    blueman-sendto    blueman-tray      
root@porteus:/home/guest# blueman-manager
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)

(blueman-manager:2340): dconf-WARNING **: 19:26:26.465: failed to commit changes to dconf: The connection is closed

(blueman-manager:2340): dconf-WARNING **: 19:26:26.477: failed to commit changes to dconf: The connection is closed

(blueman-manager:2340): dconf-WARNING **: 19:26:26.478: failed to commit changes to dconf: The connection is closed
Blueman applet needs to be running
root@porteus:/home/guest# cat /proc/cmdline
quiet BOOT_IMAGE=/boot/syslinux/vmlinuz changes=/porteus initrd=/boot/syslinux/initrd.xz
root@porteus:/home/guest# dmesg | egrep -i 'blue|fw|firmware|fail|error|warn|found'
[    0.010284] No NUMA configuration found
[    0.215422] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.684498] pnp: PnP ACPI: found 7 devices
[    0.805195] sdhci-pci 0000:44:06.1: SDHCI controller found [1180:0822] (rev 25)
[    0.809031] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[    0.809176] hub 1-0:1.0: USB hub found
[    0.813971]   No soundcards found.
[    0.820882] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[    0.821120] hub 2-0:1.0: USB hub found
[    1.178098] usb 1-1: New USB device found, idVendor=8087, idProduct=0020, bcdDevice= 0.00
[    1.178554] hub 1-1:1.0: USB hub found
[    1.186104] usb 2-1: New USB device found, idVendor=8087, idProduct=0020, bcdDevice= 0.00
[    1.186564] hub 2-1:1.0: USB hub found
[    1.536067] usb 1-1.1: New USB device found, idVendor=03f0, idProduct=231d, bcdDevice= 3.06
[    1.543692] usb 2-1.4: New USB device found, idVendor=03f0, idProduct=004a, bcdDevice= 1.16
[    1.680296] usb 1-1.3: New USB device found, idVendor=138a, idProduct=0007, bcdDevice= 0.72
[    1.862293] usb 1-1.5: New USB device found, idVendor=04f2, idProduct=b15e, bcdDevice=85.54
[    6.304977] ipv6: module verification failed: signature and/or required key missing - tainting kernel
[    7.512643] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances
[    7.512651] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799AC5-9429-4529-927E-DFE13736EEBA has zero instances
[    7.512653] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799ACA-9429-4529-927E-DFE13736EEBA has zero instances
[    7.513208] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]: 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    7.513211] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]: 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    7.776786] hp_accel: hardware type HPB64xx found
[    7.777445] lis3lv02d: 8 bits sensor found
[    7.795606] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20230628/utaddress-204)
[    7.795623] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20230628/utaddress-204)
[    7.795630] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20230628/utaddress-204)
[    7.795636] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20230628/utaddress-204)
[    7.795641] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    7.965420] intel ips 0000:00:1f.6: CPU TDP doesn't match expected value (found 25, expected 29)
[    7.965735] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled until i915 loads
[    8.407066] yenta_cardbus 0000:44:06.2: CardBus bridge found [103c:172a]
[    8.634909] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    8.634923] cfg80211: failed to load regulatory.db
[    8.759630] firewire_core 0000:44:06.0: created device fw0: GUID 5566778811223344, S400
[    8.780044] iwlwifi 0000:43:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
[    8.780128] iwlwifi 0000:43:00.0: Direct firmware load for iwlwifi-6000-5.ucode failed with error -2
[    9.141321] iwlwifi 0000:43:00.0: loaded firmware version 9.221.4.1 build 25532 6000-4.ucode op_mode iwldvm
[    9.973370] ata7: found unknown device (class 0)
[    9.973401] ata7: found unknown device (class 0)
[   13.355031] Bluetooth: Core ver 2.22
[   13.355068] NET: Registered PF_BLUETOOTH protocol family
[   13.355070] Bluetooth: HCI device and connection manager initialized
[   13.355076] Bluetooth: HCI socket layer initialized
[   13.355078] Bluetooth: L2CAP socket layer initialized
[   13.355082] Bluetooth: SCO socket layer initialized
[   13.623745] usb 1-1.5: Found UVC 1.00 device HP Webcam [2 MP Macro] (04f2:b15e)
[   16.283431] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   16.283438] Bluetooth: BNEP filters: protocol multicast
[   16.283445] Bluetooth: BNEP socket layer initialized
[   16.284768] Bluetooth: MGMT ver 1.22
[   26.514069] Bluetooth: RFCOMM TTY layer initialized
[   26.514085] Bluetooth: RFCOMM socket layer initialized
[   26.514094] Bluetooth: RFCOMM ver 1.11
Those who win the race are those who are slow and steady. :happy62:

User avatar
Blaze
DEV Team
DEV Team
Posts: 3962
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#9 by Blaze » 14 Dec 2024, 11:50

supertabs,
hm

Code: Select all

[    8.759630] firewire_core 0000:44:06.0: created device fw0: GUID 5566778811223344, S400
[    8.780044] iwlwifi 0000:43:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
[    8.780128] iwlwifi 0000:43:00.0: Direct firmware load for iwlwifi-6000-5.ucode failed with error -2
how about to download and activate kernel-firmware-20241209_633e866-noarch-1.xzm

Code: Select all

su
toor
getpkg kernel-firmware
# activate kernel-firmware-20241209_633e866-noarch-1.xzm
# and check on firmware load
dmesg | egrep -i 'blue|fw|firmware|fail|error|warn|found'
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#10 by supertabs » 14 Dec 2024, 12:29

My internet is currently unstable and I can't download it now. I gonna post an update soon once I was able to download and activate it.
Those who win the race are those who are slow and steady. :happy62:

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#11 by supertabs » 15 Dec 2024, 08:30

Code: Select all

[    0.010282] No NUMA configuration found
[    0.215435] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.684660] pnp: PnP ACPI: found 7 devices
[    0.815901] sdhci-pci 0000:44:06.1: SDHCI controller found [1180:0822] (rev 25)
[    0.819442] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[    0.819726] hub 1-0:1.0: USB hub found
[    0.830520]   No soundcards found.
[    0.831204] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[    0.831315] hub 2-0:1.0: USB hub found
[    1.186138] usb 1-1: New USB device found, idVendor=8087, idProduct=0020, bcdDevice= 0.00
[    1.186570] hub 1-1:1.0: USB hub found
[    1.193868] usb 2-1: New USB device found, idVendor=8087, idProduct=0020, bcdDevice= 0.00
[    1.194319] hub 2-1:1.0: USB hub found
[    1.544063] usb 1-1.1: New USB device found, idVendor=03f0, idProduct=231d, bcdDevice= 3.06
[    1.551713] usb 2-1.4: New USB device found, idVendor=03f0, idProduct=004a, bcdDevice= 1.16
[    1.688308] usb 1-1.3: New USB device found, idVendor=138a, idProduct=0007, bcdDevice= 0.72
[    1.871304] usb 1-1.5: New USB device found, idVendor=04f2, idProduct=b15e, bcdDevice=85.54
[    6.174327] ipv6: module verification failed: signature and/or required key missing - tainting kernel
[    6.734691] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799AC3-9429-4529-927E-DFE13736EEBA has zero instances
[    6.734699] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799AC5-9429-4529-927E-DFE13736EEBA has zero instances
[    6.734701] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: A1799ACA-9429-4529-927E-DFE13736EEBA has zero instances
[    6.735214] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]: 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    6.735217] wmi_bus wmi_bus-PNP0C14:01: [Firmware Info]: 8F1F6435-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    6.920428] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20230628/utaddress-204)
[    6.920443] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20230628/utaddress-204)
[    6.920450] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20230628/utaddress-204)
[    6.920457] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20230628/utaddress-204)
[    6.920463] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    7.072019] hp_accel: hardware type HPB64xx found
[    7.082446] lis3lv02d: 8 bits sensor found
[    7.124453] yenta_cardbus 0000:44:06.2: CardBus bridge found [103c:172a]
[    7.381658] intel ips 0000:00:1f.6: CPU TDP doesn't match expected value (found 25, expected 29)
[    7.381886] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled until i915 loads
[    7.629593] firewire_core 0000:44:06.0: created device fw0: GUID 5566778811223344, S400
[    7.631724] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    7.631731] cfg80211: failed to load regulatory.db
[    8.003841] iwlwifi 0000:43:00.0: Direct firmware load for iwlwifi-6000-6.ucode failed with error -2
[    8.003994] iwlwifi 0000:43:00.0: Direct firmware load for iwlwifi-6000-5.ucode failed with error -2
[    8.362315] iwlwifi 0000:43:00.0: loaded firmware version 9.221.4.1 build 25532 6000-4.ucode op_mode iwldvm
[    9.471047] ata7: found unknown device (class 0)
[    9.471072] ata7: found unknown device (class 0)
[   13.948496] Bluetooth: Core ver 2.22
[   13.948529] NET: Registered PF_BLUETOOTH protocol family
[   13.948531] Bluetooth: HCI device and connection manager initialized
[   13.948537] Bluetooth: HCI socket layer initialized
[   13.948540] Bluetooth: L2CAP socket layer initialized
[   13.948543] Bluetooth: SCO socket layer initialized
[   14.069193] usb 1-1.5: Found UVC 1.00 device HP Webcam [2 MP Macro] (04f2:b15e)
[   15.922680] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   15.922686] Bluetooth: BNEP filters: protocol multicast
[   15.922692] Bluetooth: BNEP socket layer initialized
[   15.925381] Bluetooth: MGMT ver 1.22
[   26.966224] Bluetooth: RFCOMM TTY layer initialized
[   26.966238] Bluetooth: RFCOMM socket layer initialized
[   26.966250] Bluetooth: RFCOMM ver 1.11
Those who win the race are those who are slow and steady. :happy62:

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#12 by supertabs » 15 Dec 2024, 08:31

Still the same, even when the kernel firmware module is activated
Those who win the race are those who are slow and steady. :happy62:

User avatar
Blaze
DEV Team
DEV Team
Posts: 3962
Joined: 28 Dec 2010, 11:31
Distribution: ⟰ Porteus current ☯ all DEs ☯
Location: ☭ Russian Federation, Lipetsk region, Dankov
Contact:

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#13 by Blaze » 15 Dec 2024, 09:17

supertabs, try to update keenel Porteus Kernel Builder (Пост Blaze #101256)

Code: Select all

# All operations are must be done as root user!

# !!! replace with a new version of 000-kernel.xzm (remove old kernel version) !!!
# remove crippled_sources.xzm
# optionally add 06-crippled_sources-NNN-XXbit.xzm
/path-to/porteus/base

# !!! replace vmlinuz !!!
/path-to/boot/syslinux

# reboot Porteus
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#14 by supertabs » 16 Dec 2024, 02:33

Blaze wrote:
15 Dec 2024, 09:17
try to update keenel

Code: Select all

             `.-:::-.`               guest@porteus.example.net 
         -+ydmNNNNNNNmdy+-           ------------------------- 
      .+dNmdhs+//////+shdmdo.        OS: Porteus 5.01 x86_64 
    .smmy+-`             ./sdy:      Host: Hewlett-Packard 172A 
  `omdo.    `.-/+osssso+/-` `+dy.    Kernel: 6.12.5-porteus 
 `yms.   `:shmNmdhsoo++osyyo-``oh.   Uptime: 31 secs 
 hm/   .odNmds/.`    ``.....:::-+s   Packages: 657 (pkgtool), 167737 (pkginfo) 
/m:  `+dNmy:`   `./oyhhhhyyooo++so   Shell: bash 5.1.16 
ys  `yNmy-    .+hmmho:-.`     ```    Resolution: 1366x768 
s:  yNm+`   .smNd+.                  DE: Xfce 4.16 
`` /Nm:    +dNd+`                    WM: Xfwm4 
   yN+   `smNy.                      WM Theme: Porteus-dark 
   dm    oNNy`                       Theme: Adwaita-dark [GTK2/3] 
   hy   -mNm.                        Icons: elementary-xfce-dark [GTK2], Adwait 
   +y   oNNo                         Terminal: xfce4-terminal 
   `y`  sNN:                         Terminal Font: DejaVu Sans Mono 10 
    `:  +NN:                         CPU: Intel i7 M 620 (4) @ 2.667GHz 
     `  .mNo                         GPU: Intel Core Processor 
         /mm`                        Memory: 828MiB / 3722MiB 
          /my`
           .sy`                                              
             .+:                                             
                `
Still the same, cannot connect to bluetooth devices.
Those who win the race are those who are slow and steady. :happy62:

supertabs
Black ninja
Black ninja
Posts: 62
Joined: 07 Jun 2021, 08:33
Distribution: porteus-4.0-x86_64

Cannot connect bluetooth Connection Failed: br-connection-profile-unavailable

Post#15 by supertabs » 16 Dec 2024, 04:01

Code: Select all

uest@porteus:~$ pactl load-module module-bluetooth-discover
Failure: Module initialization failed
Why does this command fail? module-bluetooth-discover.so is present, so why?
Those who win the race are those who are slow and steady. :happy62:

Post Reply