| 1 |
On Sat, Mar 26, 2022 at 10:02 AM Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 2 |
> |
| 3 |
> On Saturday, 26 March 2022 15:14:11 GMT ny6p01 wrote: |
| 4 |
> > Just a shot in the dark, but is alsasound service starting correctly? |
| 5 |
> |
| 6 |
> It doesn't run at all, not even while I'm listening after restarting PA. I |
| 7 |
> have alsa-lib, alsa-topology-conf, alsa-ucm-conf and alsa-plugins installed, |
| 8 |
> but 'ps -ax | grep alsa' finds nothing. Also, I have no alsasound service. |
| 9 |
> |
| 10 |
> I assume that PA doesn't need a running alsa process to function. |
| 11 |
> |
| 12 |
> -- |
| 13 |
> Regards, |
| 14 |
> Peter. |
| 15 |
> |
| 16 |
|
| 17 |
PA might not (or doesn't - my system has no alsa processes) need alsa |
| 18 |
processes but it almost certainly using Alsa drivers. |
| 19 |
|
| 20 |
lsmod | grep snd |
| 21 |
lsmod | sound |
| 22 |
|
| 23 |
However those depend on what you build as modules vs hard code into |
| 24 |
your kernel. |
| 25 |
|
| 26 |
ls /proc/asound would give you a view into what function, if any, alsa is |
| 27 |
performing. |
Archives