[SOLVED] System not recognising bluetooth USB adapter

[LemonadeLlama]

Hello everyone. I recently purchased a bluetooth USB adapter, but it's not working on my system. It's a Sennheiser BTD 600.

I assumed it would work because a customer review of the product on pbtech says it works on Debian 11.

My kernel was installed by emerging gentoo-kernel, and I have not changed any kernel configuration beyond that.

I emerged the bluez package as per the wiki's instructions, and I also emerged it with the deprecated flag.

This device is not appearing in the output of rfkill, hciconfig, or bluetoothctl. I added it to my openrc and it's running fine:

Code: Select all

$sudo rc-service bluetooth status
 * status: started

$ hciconfig -a
$

$ bluetoothctl
Agent registered
[bluetooth]# list
[bluetooth]# exit

$ rfkill list
$ 

When I connected the adapter, the following message appeared in dmesg:

Code: Select all

[ 1816.072293] usb 3-4: USB disconnect, device number 2
[ 1826.717239] usb 3-4: new full-speed USB device number 6 using xhci_hcd
[ 1827.103179] usb 3-4: New USB device found, idVendor=0a12, idProduct=4010, bcdDevice=20.52
[ 1827.103185] usb 3-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1827.111652] hub 3-4:1.0: USB hub found
[ 1827.114565] hub 3-4:1.0: 4 ports detected
[ 1827.427232] usb 3-4.1: new full-speed USB device number 7 using xhci_hcd
[ 1827.722594] usb 3-4.1: New USB device found, idVendor=3542, idProduct=3000, bcdDevice=28.38
[ 1827.722600] usb 3-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 1827.722601] usb 3-4.1: Product: BTD 600
[ 1827.722602] usb 3-4.1: Manufacturer: BTD 600
[ 1827.722603] usb 3-4.1: SerialNumber: 90ADAD1A997191AB3C08
[ 1827.754820] input: BTD 600 BTD 600 Consumer Control as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/0000:03:0c.0/0000:0b:00.0/usb3/3-4/3-4.1/3-4.1:1.0/0003:3542:3000.0006/input/input25
[ 1827.810690] input: BTD 600 BTD 600 as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/0000:03:0c.0/0000:0b:00.0/usb3/3-4/3-4.1/3-4.1:1.0/0003:3542:3000.0006/input/input26
[ 1827.810727] input: BTD 600 BTD 600 as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/0000:03:0c.0/0000:0b:00.0/usb3/3-4/3-4.1/3-4.1:1.0/0003:3542:3000.0006/input/input27
[ 1827.810757] input: BTD 600 BTD 600 as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/0000:03:0c.0/0000:0b:00.0/usb3/3-4/3-4.1/3-4.1:1.0/0003:3542:3000.0006/input/input28
[ 1827.810828] hid-generic 0003:3542:3000.0006: input,hiddev99,hidraw5: USB HID v1.11 Device [BTD 600 BTD 600] on usb-0000:0b:00.0-4.1/input0
[ 1827.819876] hid-generic 0003:3542:3000.0007: hiddev100,hidraw6: USB HID v1.11 Device [BTD 600 BTD 600] on usb-0000:0b:00.0-4.1/input1
[ 1827.833575] mc: Linux media interface: v0.10
[ 1827.929769] usbcore: registered new interface driver snd-usb-audio

This is how the device appears in the output of lsusb:

Code: Select all

Bus 003 Device 006: ID 0a12:4010 Cambridge Silicon Radio, Ltd 

Am I missing some firmware? Is this device simply not supported? I'm not sure what to check from here.

[alamahant]

Does something like

Code: Select all

[*] Networking support --->
     <*> Bluetooth subsystem support --->
        [*]   Bluetooth Classic (BR/EDR) features
        <*>     RFCOMM protocol support
        [*]       RFCOMM TTY support
        <*>     BNEP protocol support
        [*]       Multicast filter support
        [*]       Protocol filter support
        <*>     HIDP protocol support 
        [*]     Bluetooth High Speed (HS) features (NEW) 
        [*]   Bluetooth device drivers
              <*> HCI USB driver             

help?
Also please install
linux-firmware

[Logicien]

Do this Usb to Bluetooth device need firmware files that are not installed on your Gentoo or unavailable?

[LemonadeLlama]

Does something like

Code: Select all

[*] Networking support --->
     <*> Bluetooth subsystem support --->
        [*]   Bluetooth Classic (BR/EDR) features
        <*>     RFCOMM protocol support
        [*]       RFCOMM TTY support
        <*>     BNEP protocol support
        [*]       Multicast filter support
        [*]       Protocol filter support
        <*>     HIDP protocol support 
        [*]     Bluetooth High Speed (HS) features (NEW) 
        [*]   Bluetooth device drivers
              <*> HCI USB driver             

help?
Also please install
linux-firmware

I have the linux-firmware package emerged.
I also have Bluetooth subsystem support enabled in my kernel, but as a module and not built-in. Same for BNEP protocol support. This is how it was in the emerged gentoo-kernel, butI will try changing that.

[LemonadeLlama]

Does something like

Code: Select all

[*] Networking support --->
     <*> Bluetooth subsystem support --->
        [*]   Bluetooth Classic (BR/EDR) features
        <*>     RFCOMM protocol support
        [*]       RFCOMM TTY support
        <*>     BNEP protocol support
        [*]       Multicast filter support
        [*]       Protocol filter support
        <*>     HIDP protocol support 
        [*]     Bluetooth High Speed (HS) features (NEW) 
        [*]   Bluetooth device drivers
              <*> HCI USB driver             

help?

I reconfigured my kernel and restarted my PC. It now has all the settings you've suggested and still no luck.

To compare, I tested the adapter with my old Sony Vaio laptop that has built-in bluetooth and runs Manjaro, thus uses the gnome-bluetooth tool for managing bluetooth.
With the adapter connected to my PC, the laptop can pick up the adapter and show it in the devices. It still doesn't appear in my PC's bluetoothctl output, but at least my laptop with working bluetooth can detect it.

I'm not sure what I'm missing now.

[Anon-E-moose]

What drivers do you have enabled?

under HCI USB driver area you select protocols.

I have broadcom and realtek protocols selected. but there are other choices depending on the device.

Edit to add: I use a TP bluetooth adapter, so your's will vary.

This is from my .config, I have mine as a module, but these are all the bluetooth settings (for my device)

Code: Select all

CONFIG_BT=m
CONFIG_BT_BREDR=y
CONFIG_BT_RFCOMM=y
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=y
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=y
CONFIG_BT_HS=y
CONFIG_BT_LE=y
CONFIG_BT_AOSPEXT=y
CONFIG_BT_DEBUGFS=y

CONFIG_BT_INTEL=m
CONFIG_BT_BCM=m
CONFIG_BT_RTL=m
CONFIG_BT_HCIBTUSB=m
CONFIG_BT_HCIBTUSB_BCM=y
CONFIG_BT_HCIBTUSB_RTL=y

[LemonadeLlama]

What drivers do you have enabled?

Here is my config:

Code: Select all

CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m
CONFIG_CAN_GW=m
CONFIG_CAN_J1939=m
CONFIG_CAN_ISOTP=m
CONFIG_BT=y
CONFIG_BT_BREDR=y
CONFIG_BT_RFCOMM=y
CONFIG_BT_RFCOMM_TTY=y
CONFIG_BT_BNEP=y
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
CONFIG_BT_HIDP=y
# CONFIG_BT_HS is not set
CONFIG_BT_LE=y
CONFIG_BT_6LOWPAN=y
CONFIG_BT_LEDS=y
CONFIG_BT_MSFTEXT=y
CONFIG_BT_AOSPEXT=y
CONFIG_BT_DEBUGFS=y

#
# Bluetooth device drivers
#
CONFIG_BT_INTEL=m
CONFIG_BT_BCM=m
CONFIG_BT_RTL=m
CONFIG_BT_QCA=m
CONFIG_BT_MTK=m
CONFIG_BT_HCIBTUSB=m
CONFIG_BT_HCIBTUSB_AUTOSUSPEND=y
CONFIG_BT_HCIBTUSB_BCM=y
CONFIG_BT_HCIBTUSB_MTK=y
CONFIG_BT_HCIBTUSB_RTL=y
CONFIG_BT_HCIBTSDIO=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIUART_SERDEV=y
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_NOKIA=m
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_ATH3K=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIUART_3WIRE=y
CONFIG_BT_HCIUART_INTEL=y
CONFIG_BT_HCIUART_BCM=y
CONFIG_BT_HCIUART_RTL=y
CONFIG_BT_HCIUART_QCA=y
CONFIG_BT_HCIUART_AG6XX=y
CONFIG_BT_HCIUART_MRVL=y
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIVHCI=m
CONFIG_BT_MRVL=m
CONFIG_BT_MRVL_SDIO=m
CONFIG_BT_ATH3K=m
CONFIG_BT_MTKSDIO=m
CONFIG_BT_MTKUART=m
CONFIG_BT_HCIRSI=m
CONFIG_BT_VIRTIO=m
# end of Bluetooth device drivers

I can see that only CONFIG_BT_HS is not set, so I'll enable that and see if that makes any difference.

[LemonadeLlama]

I can see that only CONFIG_BT_HS is not set, so I'll enable that and see if that makes any difference.

It didn't change anything

[Banana]

I do use a jabra adapter. But without any bluetooth stuff enabled and it just works. Maybe those kind of adapters do bluetooth but do not appear as a bluetooth device as itself?
Does your adapter work with a senheiser device?

[Anon-E-moose]

The only other thing to do, is run it with a live cd and see what config options are set.

I would also look at the the usb options, especially hid ones

Edit to add: there are hid options under device drivers that have a few options that might affect stuff.

and have you looked at https://wiki.gentoo.org/wiki/Bluetooth


What does "dmesg | grep -i blue" return?

[LemonadeLlama]

Alright, I've tried booting from an Ubuntu 22 USB, to see if the adapter would work from there, and still nothing.
I have followed the Bluetooth wiki article to the best of my ability.

What does "dmesg | grep -i blue" return?

With the adapter plugged in from boot, It returns this:

Code: Select all

$ dmesg | grep -i blue
[    0.348053] Bluetooth: Core ver 2.22
[    0.348053] NET: Registered PF_BLUETOOTH protocol family
[    0.348053] Bluetooth: HCI device and connection manager initialized
[    0.348053] Bluetooth: HCI socket layer initialized
[    0.348053] Bluetooth: L2CAP socket layer initialized
[    0.348053] Bluetooth: SCO socket layer initialized
[    0.775042] Bluetooth: RFCOMM TTY layer initialized
[    0.775055] Bluetooth: RFCOMM socket layer initialized
[    0.775074] Bluetooth: RFCOMM ver 1.11
[    0.775084] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    0.775098] Bluetooth: BNEP filters: protocol multicast
[    0.775112] Bluetooth: BNEP socket layer initialized
[    0.775125] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    0.775140] Bluetooth: HIDP socket layer initialized

Disconnecting the adapter printed this:

Code: Select all

[  256.508986] usb 7-1: USB disconnect, device number 2
[  256.508990] usb 7-1.1: USB disconnect, device number 3

And reconnecting the adapter printed this:

Code: Select all

[  291.384371] usb 3-4: new full-speed USB device number 5 using xhci_hcd
[  291.768025] usb 3-4: New USB device found, idVendor=0a12, idProduct=4010, bcdDevice=20.52
[  291.768031] usb 3-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  291.775763] hub 3-4:1.0: USB hub found
[  291.778713] hub 3-4:1.0: 4 ports detected
[  292.091087] usb 3-4.1: new full-speed USB device number 6 using xhci_hcd
[  292.386747] usb 3-4.1: New USB device found, idVendor=3542, idProduct=3000, bcdDevice=28.38
[  292.386752] usb 3-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[  292.386754] usb 3-4.1: Product: BTD 600
[  292.386755] usb 3-4.1: Manufacturer: BTD 600
[  292.386756] usb 3-4.1: SerialNumber: 90ADAD1A997191AB3C08
[  292.418883] input: BTD 600 BTD 600 Consumer Control as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/0000:03:0c.0/0000:0b:00.0/usb3/3-4/3-4.1/3-4.1:1.0/0003:3542:3000.0008/input/input29
[  292.474210] input: BTD 600 BTD 600 as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/0000:03:0c.0/0000:0b:00.0/usb3/3-4/3-4.1/3-4.1:1.0/0003:3542:3000.0008/input/input30
[  292.474242] input: BTD 600 BTD 600 as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/0000:03:0c.0/0000:0b:00.0/usb3/3-4/3-4.1/3-4.1:1.0/0003:3542:3000.0008/input/input31
[  292.474265] input: BTD 600 BTD 600 as /devices/pci0000:00/0000:00:02.1/0000:02:00.0/0000:03:0c.0/0000:0b:00.0/usb3/3-4/3-4.1/3-4.1:1.0/0003:3542:3000.0008/input/input32
[  292.474328] hid-generic 0003:3542:3000.0008: input,hiddev97,hidraw2: USB HID v1.11 Device [BTD 600 BTD 600] on usb-0000:0b:00.0-4.1/input0
[  292.483975] hid-generic 0003:3542:3000.0009: hiddev98,hidraw3: USB HID v1.11 Device [BTD 600 BTD 600] on usb-0000:0b:00.0-4.1/input1

Additionally, my searching led me to this reported issue on the kernel, to do with unusable Cambridge Silicon Radio bluetooth devices (the same type my adapter has).
https://bugzilla.kernel.org/show_bug.cgi?id=60824#c93
Is there any change applying any of the suggested patches from here would help?

[Anon-E-moose]

This is what I see from boot

Code: Select all

 $ dmesg|grep -i blue
[    2.000971] Bluetooth: Core ver 2.22
[    2.001001] NET: Registered PF_BLUETOOTH protocol family
[    2.001004] Bluetooth: HCI device and connection manager initialized
[    2.001011] Bluetooth: HCI socket layer initialized
[    2.001015] Bluetooth: L2CAP socket layer initialized
[    2.001020] Bluetooth: SCO socket layer initialized
[    2.007603] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[    2.009559] Bluetooth: hci0: RTL: rom_version status=0 version=1
[    2.009563] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[    2.010380] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[    2.010433] Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814
[    2.260596] Bluetooth: hci0: RTL: fw version 0x09a98a6b

Lots of hci* loading include the firmware.

In my (vague) searching for your problem, I ran across a screen shot that showed the sennheiser/cambridge being in hci mode
So, I would look around to see what it takes to put that dongle in hci mode and see if that doesn't work

Edit to add:
https://device.report/manual/5708495

As per that link I would try putting the device in sbc mode (vs aptx) just to get it started.
There are 2 libs for aptx, but not sure how you would use them.

ETA2: In looking at your .config, I see some are modules (didn't check all). They do need to be modules to pick up firmware loading properly.
Are you sure that all the modules are being loaded?

ETA3: From your link

Good news on my end, it seems like Greg Kroah-Hartman has added my two latest patches to both the 5.10-stable and 6.0-stable trees.

So if running either 6.0+ or the 5.10 series you wouldn't need to add it.

ETA4:
From my 5.17 kernel sources

Code: Select all

config BT_HCIUART_BCSP
    bool "BCSP protocol support"
    depends on BT_HCIUART
    select BITREVERSE
    help
      BCSP (BlueCore Serial Protocol) is serial protocol for communication
      between Bluetooth device and host. This protocol is required for non
      USB Bluetooth devices based on CSR BlueCore chip, including PCMCIA and
      CF cards.

      Say Y here to compile support for HCI BCSP protocol.

And you have that selected, but I think part of the problem is some things module, some builtin, make them all one or the other (when you have a choice)
This selection is built in, ie Y in .config, while things it needs are set as modules.

[LemonadeLlama]

Alright, my sony headset just arrived today, so I was able to do testing with my real setup.

Despite the adapter not appearing in bluetoothctl, rfkill, or hciconfig, my headset was still able to pair. Now we're getting somewhere. I had no idea that bluetooth devices could work and not show up under those commands.

After pairing, there is no audio. I have pipewire installed, so I thought there might be a pipewire issue.

This is the output I get from gentoo-pipewire-launcher:

Code: Select all

[W][01004.423506] pw.context   | [       context.c:  339 pw_context_new()] 0x555c71488dd0: can't load dbus library: support/libspa-dbus
[W][01004.423598] mod.rt       | [     module-rt.c:  969 pipewire__module_init()] regular realtime scheduling not available (RTKit fallback disabled)
[W][01004.423774] pw.context   | [       context.c:  339 pw_context_new()] 0x55e9dcd9ddd0: can't load dbus library: support/libspa-dbus
[W][01004.423869] mod.rt       | [     module-rt.c:  969 pipewire__module_init()] regular realtime scheduling not available (RTKit fallback disabled)
[W][01004.424298] default      | [        thread.c:  121 impl_acquire_rt()] acquire_rt thread:0x7f573efd16c0 prio:-1 not implemented
[W][01004.424854] default      | [        thread.c:  121 impl_acquire_rt()] acquire_rt thread:0x7f8a35aaa6c0 prio:-1 not implemented
M 23:33:44.677943         pw.context ../pipewire-0.3.63/src/pipewire/context.c:339:pw_context_new: 0x56496a9db150: can't load dbus library: support/libspa-dbus
M 23:33:44.678069             mod.rt ../pipewire-0.3.63/src/modules/module-rt.c:969:pipewire__module_init: regular realtime scheduling not available (RTKit fallback disabled)
M 23:33:44.678361            default ../pipewire-0.3.63/src/pipewire/thread.c:121:impl_acquire_rt: acquire_rt thread:0x7fe2591646c0 prio:-1 not implemented
M 23:33:44.683839          wp-device ../wireplumber-0.4.13/lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.v4l2.enum.udev' could not be loaded; is it installed?
M 23:33:44.683845        script/v4l2 v4l2.lua:164:chunk: PipeWire's V4L SPA missing or broken. Video4Linux not supported.
M 23:33:44.685266          wp-device ../wireplumber-0.4.13/lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
M 23:33:44.685271   script/libcamera libcamera.lua:168:chunk: PipeWire's libcamera SPA missing or broken. libcamera not supported.
M 23:33:44.686704          wp-device ../wireplumber-0.4.13/lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed?
M 23:33:44.686709       script/bluez bluez.lua:277:createMonitor: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported.
M 23:33:45.570516    m-lua-scripting ../wireplumber-0.4.13/modules/module-lua-scripting/api/api.c:376:object_activate_done: <WpSiAudioAdapter:0x56496ac2e040> Object activation aborted: proxy destroyed
M 23:33:45.570532 script/create-item create-item.lua:80:chunk: <WpSiAudioAdapter:0x56496ac2e040> failed to activate item: Object activation aborted: proxy destroyed

This looks like it's relevant:

Code: Select all

M 23:33:44.686709       script/bluez bluez.lua:277:createMonitor: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported.

I will add some more USE flags to pipewire and keep investigating.

[Anon-E-moose]

There is a bluetooth use flag for pipewire.

[LemonadeLlama]

bluetooth was already added to my make.conf file:

Code: Select all

USE="alsa bluetooth elogind examples ffmpeg ipv6 multilib opengl pipewire pulseaudio udev vaapi vdpau vulkan wayland X xwayland -emacs -gnome -kde -systemd -wifi"

However, I decided to rebuild pipewire just in case.

Code: Select all

$ sudo emerge -av pipewire

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] media-video/pipewire-0.3.63-r2:0/0.4::gentoo  USE="X bluetooth lv2 pipewire-alsa readline sound-server ssl test udev v4l -dbus -doc -echo-cancel -extra -flatpak -gsettings -gstreamer -jack-client -jack-sdk -modemmanager (-system-service) -systemd -zeroconf" ABI_X86="(64) -32 (-x32)" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB

Would you like to merge these packages? [Yes/No] Yes
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) media-video/pipewire-0.3.63-r2::gentoo
>>> Installing (1 of 1) media-video/pipewire-0.3.63-r2::gentoo
>>> Jobs: 1 of 1 complete                           Load avg: 6.24, 2.14, 0.92

Still nothing:

Code: Select all

$ gentoo-pipewire-launcher 
[W][00506.275408] pw.context   | [       context.c:  339 pw_context_new()] 0x56143d735dd0: can't load dbus library: support/libspa-dbus
[W][00506.275538] mod.rt       | [     module-rt.c:  969 pipewire__module_init()] regular realtime scheduling not available (RTKit fallback disabled)
[W][00506.275593] pw.context   | [       context.c:  339 pw_context_new()] 0x5609e418cdd0: can't load dbus library: support/libspa-dbus
[W][00506.275731] mod.rt       | [     module-rt.c:  969 pipewire__module_init()] regular realtime scheduling not available (RTKit fallback disabled)
[W][00506.276321] default      | [        thread.c:  121 impl_acquire_rt()] acquire_rt thread:0x7fec42bed6c0 prio:-1 not implemented
[W][00506.276776] default      | [        thread.c:  121 impl_acquire_rt()] acquire_rt thread:0x7f5cc29916c0 prio:-1 not implemented
M 23:57:38.229928         pw.context ../pipewire-0.3.63/src/pipewire/context.c:339:pw_context_new: 0x5576504dc150: can't load dbus library: support/libspa-dbus
M 23:57:38.230058             mod.rt ../pipewire-0.3.63/src/modules/module-rt.c:969:pipewire__module_init: regular realtime scheduling not available (RTKit fallback disabled)
M 23:57:38.230356            default ../pipewire-0.3.63/src/pipewire/thread.c:121:impl_acquire_rt: acquire_rt thread:0x7fbf869416c0 prio:-1 not implemented
M 23:57:38.239300          wp-device ../wireplumber-0.4.13/lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
M 23:57:38.239315   script/libcamera libcamera.lua:168:chunk: PipeWire's libcamera SPA missing or broken. libcamera not supported.
M 23:57:38.241959          wp-device ../wireplumber-0.4.13/lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed?
M 23:57:38.241969       script/bluez bluez.lua:277:createMonitor: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported.
M 23:57:39.274957    m-lua-scripting ../wireplumber-0.4.13/modules/module-lua-scripting/api/api.c:376:object_activate_done: <WpSiAudioAdapter:0x557650706040> Object activation aborted: proxy destroyed
M 23:57:39.274975 script/create-item create-item.lua:80:chunk: <WpSiAudioAdapter:0x557650706040> failed to activate item: Object activation aborted: proxy destroyed

EDIT:
Forget what I said. It seems that despite the warnings, as long as I run gentoo-pipewire-launcher, the audio works. I tested the behaviour after rebooting the system and it's consistent.

So why do these warnings appear? Also, I'm using SDDM, so it's supposed to start pipewire when I log in:

Code: Select all

$ cat /etc/xdg/autostart/pipewire.desktop 
[Desktop Entry]
Version=1.0
Name[de]=PipeWire Mediensystem
Name=PipeWire Media System
Comment[de]=Das PipeWire Mediensystem starten
Comment=Start the PipeWire Media System
Exec=/usr/bin/gentoo-pipewire-launcher
Terminal=false
Type=Application
X-GNOME-HiddenUnderSystemd=true
X-KDE-HiddenUnderSystemd=true
X-systemd-skip=true

So why should I have to manually start pipewire myself to make this work? What's causing pipewire to exit on login?

[Anon-E-moose]

I use a shell script to start wayland and I have this as part of the script, and I do have to start pipewire (and wireplumber for alsa in my case) and then kill it when it's done.

Code: Select all

    /usr/bin/pipewire &
    /usr/bin/wireplumber &

    eval $(ssh-agent)
    /usr/bin/env dbus-run-session -- /usr/bin/$compositor $WF_DBG >$WF_LOG 2>&1

    # clean up after session
    killall wbg.pl
    killall ssh-agent
    pkill -u "${USER}" -x pipewire\|wireplumber 1>/dev/null 2>&1

As for why pipewire exits for you, probably something to do with sddm

Edit to add:

https://wiki.gentoo.org/wiki/PipeWire

You could also add gentoo-pipewire-launcher to the wm/compositor launching script.

[LemonadeLlama]

I have SDDM installed, but even though I have the file /etc/xdg/autostart/pipewire.desktop that the pipewire package installs, it doesn't run anything. I'm using dwl with an autostart patch. I can get audio that way by running gentoo-pipewire-launcher from dwl.

Thanks for your help, everyone.