On Tue, Feb 20, 2024 at 10:28:17AM -0700, Michael Nelson wrote:
> > Then, why no caluse proded. Are no audio devices seen? It this what
> > you would view as "failure"?
>
> Yes, the last lines of 'wpctl status' should describe the audio sources
> and sinks of your audio hardware. E.g., this is what 'wpctl status'
> reports when I run it on my box:

I get

    $ wpctl status
    "Could not connect to PipeWire"

> Did you create the two configuration files as I described much earlier
> in this thread? E.g.:
>
> /etc/pipewire/pipewire.conf.d/10-wireplumber.conf
> /etc/pipewire/pipewire.conf.d/20-pipewire-pulse.conf

Yes, I dod, but I worry about the contant of the latter. What I have
in 20-pipewire-pulse.conf is:

     context.exec = [ { path = "/usr/bin/pipewire" args = "-c
     pipewire-pulse.conf" } ]

Is two lines legit here?
    

    $ alsamixer
    cannot open mixer: Host is down

    $ alsamixer -c0 
    [opens alsamixer to card HDA Intel  PCH. F6 does not list Pipewire 
    as option}         

    $ alsamixer -c1
    [opens USB camera]

Both pipewirr and wireplumber are running:
    

    $ ps x | grep pipewire
    26207 pts/16   S+     0:00 grep pipewire

    $ ps x | grep wireplumber
    26210 pts/16   S+     0:00 grep wireplumber

--

     Haines Brown