Pipewire - Where are my hardware devices?

hugeblank · 2023-10-11 03:06:04

For some background, I usually run plasma, but unfortunately my monitor died and I'm not in the position to get a new one for a while. I decided to try sway, which supports having a headless wayland session, linking that up to wayvnc, and connecting to it through my laptop, as a temporary-ish solution. I start sway through a custom user systemd unit, and then start wayvnc when I need it through an ssh session.

On plasma, all hardware and virtual audio devices registered and configured perfectly normally. On sway, only virtual audio devices work. It's my understanding that the service responsible for hardware devices is either pipewire-media-session or wireplumber. I have wireplumber. All relevant services are enabled, and the USB device registers in the kernel with no errors. Some logs to clarify the situation:

sudo dmesg

[ 3685.305985] usb 3-6.1: USB disconnect, device number 4
[ 3688.768307] usb 3-6.1: new full-speed USB device number 5 using xhci_hcd
[ 3688.922213] usb 3-6.1: New USB device found, idVendor=046d, idProduct=0aba, bcdDevice= 1.00
[ 3688.922223] usb 3-6.1: New USB device strings: Mfr=3, Product=4, SerialNumber=0
[ 3688.922227] usb 3-6.1: Product: PRO X Wireless Gaming Headset
[ 3688.922231] usb 3-6.1: Manufacturer: Logitech
[ 3689.529887] input: Logitech PRO X Wireless Gaming Headset Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.3/usb3/3-6/3-6.1/3-6.1:1.3/0003:046D:0ABA.0004/input/input19
[ 3689.585066] input: Logitech PRO X Wireless Gaming Headset as /devices/pci0000:00/0000:00:01.2/0000:20:00.0/0000:21:08.0/0000:2a:00.3/usb3/3-6/3-6.1/3-6.1:1.3/0003:046D:0ABA.0004/input/input21
[ 3689.585167] hid-generic 0003:046D:0ABA.0004: input,hiddev98,hidraw2: USB HID v1.11 Device [Logitech PRO X Wireless Gaming Headset] on usb-0000:2a:00.3-6.1/input3

the Logitech PRO X is the device that I would expect to see in my patchbay/pw-cli. I do not.

lsusb -t

/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
    |__ Port 5: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 1: Dev 5, If 0, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 1: Dev 5, If 1, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 1: Dev 5, If 2, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 1: Dev 5, If 3, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
    |__ Port 1: Dev 2, If 0, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 1: Dev 2, If 2, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 1: Dev 2, If 3, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 4: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 4: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

systemctl --user status pipewire wireplumber pipewire-pulse

● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
     Active: active (running) since Tue 2023-10-10 13:32:01 PDT; 6h ago
TriggeredBy: ● pipewire.socket
   Main PID: 149338 (pipewire)
      Tasks: 2 (limit: 38369)
     Memory: 5.2M
        CPU: 318ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─149338 /usr/bin/pipewire

Oct 10 13:32:01 murphy systemd[1099]: Started PipeWire Multimedia Service.

● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
     Active: active (running) since Tue 2023-10-10 13:32:01 PDT; 6h ago
   Main PID: 149340 (wireplumber)
      Tasks: 6 (limit: 38369)
     Memory: 7.7M
        CPU: 392ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             └─149340 /usr/bin/wireplumber

Oct 10 13:32:01 murphy systemd[1099]: Started Multimedia Service Session Manager.
Oct 10 13:32:01 murphy wireplumber[149340]: [19:06:43.216735266] [149340] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
Oct 10 13:32:01 murphy wireplumber[149340]: [19:06:43.216747876] [149340] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Oct 10 13:32:01 murphy wireplumber[149340]: [19:06:43.216772197] [149340]  INFO Camera camera_manager.cpp:284 libcamera v0.1.0

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled)
     Active: active (running) since Tue 2023-10-10 13:32:03 PDT; 6h ago
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 149363 (pipewire-pulse)
      Tasks: 2 (limit: 38369)
     Memory: 10.5M
        CPU: 805ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─149363 /usr/bin/pipewire-pulse

Oct 10 13:32:03 murphy systemd[1099]: Started PipeWire PulseAudio.

I need help with either an outright solution, or further debugging steps, as I've gone to a couple other places that offer assistance. This issue has left everyone, including myself clueless. Is there something that plasma does in setting itself up that I'm missing when starting sway?

Last edited by hugeblank (2023-10-11 03:14:50)

V1del · 2023-10-11 08:00:00

Physical devices on your headless server or from the VNC client? Output of

sudo fuser -v /dev/snd/*
pactl list cards
pactl list sinks

To answer the general question, no plasma itself has no hand in how and which devices register on the pipewire server.

hugeblank · 2023-10-12 00:12:42

SO. An update on the situation. After an update, and a reboot to attempt to fix another issue entirely unrelated to the problem, the devices are now being detected:

pw-cli info all | grep "node.description"

info: unsupported type PipeWire:Interface:Profiler
*		node.description = "Family 17h (Models 00h-0fh) HD Audio Controller Digital Stereo (IEC958)"
*		node.description = "Yeti X Digital Stereo (IEC958)"
*		node.description = "PRO X Wireless Gaming Headset Digital Stereo (IEC958)"
*		node.description = "PRO X Wireless Gaming Headset Mono"

Note that I *had* done multiple reboots in the past and this did not work, so I'm very confused.

V1del wrote:

Physical devices on your headless server or from the VNC client?

Devices from my headless server. The server is close enough to me that I think the wireless headset will probably work, so I have the dongle plugged into the machine itself. If the problem occurs again, I'll be sure to run all of those commands you requested.

Arch Linux

#1 2023-10-11 03:06:04

Pipewire - Where are my hardware devices?

#2 2023-10-11 08:00:00

Re: Pipewire - Where are my hardware devices?

#3 2023-10-12 00:12:42

Re: Pipewire - Where are my hardware devices?

Board footer