When you stop pulseaudio, you did a good thing. since pulseaudio was
started again, you're probably going to have to mess around in pactl to
get this fixed if that will even be possible.
On Mon, 31 Jan 2022, Pankaj Jangid wrote:
> Andrei POPESCU writes:
>
> >> Thanks Andrei. I followed the
Andrei POPESCU writes:
>> Thanks Andrei. I followed the following steps:
>>
>> 1. Found that it is pulseaudio that is blocking the module unload.
>> 2. systemctl --user stop pulseaudio.socket
>> 3. systemctl --user stop pulseaudio.service
>> 4. Verified that now nothing is blocking
On Du, 30 ian 22, 14:58:29, Pankaj Jangid wrote:
> Andrei POPESCU writes:
>
> > Something is keeping the module busy, but according to lsmod it's not
> > another module.
> >
> > In case you get any output from
> >
> > lsof | grep /dev/snd
> >
> > (this needs root or sudo)
> >
> > try
Andrei POPESCU writes:
> Something is keeping the module busy, but according to lsmod it's not
> another module.
>
> In case you get any output from
>
> lsof | grep /dev/snd
>
> (this needs root or sudo)
>
> try stopping the applications listed in the first column (the second
> column
Jude DaShiell writes:
> rm /var/lock/asound.state.lock
>
>
As I stated in a previous reply, I had tried to remove this file and
then did "alsactl init" but no positive result. Just this output
--8<---cut here---start->8---
pankaj@anant:~$ sudo alsactl init
rm /var/lock/asound.state.lock
On Sun, 30 Jan 2022, Pankaj Jangid wrote:
> Jude DaShiell writes:
>
> > alsactl init I think will find everything.
> >
>
> Then there is something else that is not letting "alsactl init" to
> function properly; lock file as you suggested. But I couldn?t find
>
On Du, 30 ian 22, 12:47:27, Pankaj Jangid wrote:
> Andrei POPESCU writes:
>
> >> During the boot process, the system detects everything. So there must be
> >> something in the init sequence that I can trigger manually.
> >
> > You can try to unload and reload the corresponding kernel module.
Andrei POPESCU writes:
>> During the boot process, the system detects everything. So there must be
>> something in the init sequence that I can trigger manually.
>
> You can try to unload and reload the corresponding kernel module. Check
> the output of
>
> lsmod | grep snd
>
> (it's
On Du, 30 ian 22, 11:02:34, Pankaj Jangid wrote:
> Jude DaShiell writes:
>
> > alsactl --init
> > may help.
> > However alsa makes .lock files in /var/lock/alsa and you may find it
> > helpful to delete the lock file first then once card is set run alsactl
> > store. Those lock files sometimes
Pankaj Jangid writes:
> Jude DaShiell writes:
>
>> alsactl init I think will find everything.
>>
>
> Then there is something else that is not letting "alsactl init" to
> function properly; lock file as you suggested. But I couldn’t find
> anything other than "/var/lock/asound.state.lock".
I
Jude DaShiell writes:
> alsactl init I think will find everything.
>
Then there is something else that is not letting "alsactl init" to
function properly; lock file as you suggested. But I couldn’t find
anything other than "/var/lock/asound.state.lock".
alsactl init I think will find everything.
On Sun, 30 Jan 2022, Pankaj Jangid wrote:
> Jude DaShiell writes:
>
> > alsactl --init
> > may help.
> > However alsa makes .lock files in /var/lock/alsa and you may find it
> > helpful to delete the lock file first then once card is set run alsactl
>
Jude DaShiell writes:
> alsactl --init
> may help.
> However alsa makes .lock files in /var/lock/alsa and you may find it
> helpful to delete the lock file first then once card is set run alsactl
> store. Those lock files sometimes prevent alsa from doing a proper
> detection and change.
>
alsactl --init
may help.
However alsa makes .lock files in /var/lock/alsa and you may find it
helpful to delete the lock file first then once card is set run alsactl
store. Those lock files sometimes prevent alsa from doing a proper
detection and change.
On Sun, 30 Jan 2022, Pankaj Jangid
"Andrew M.A. Cater" writes:
>> Pankaj Jangid writes:
>>
>> > When I boot system afresh, the card is visible in the ‘alsamixer’ and in
>> > Gnome settings as well. Shown as “Blue” S/PDIF input and output
>> > devices. But when system wakes up from sleep (suspended), it doesn’t
>> > show the
On Sat, Jan 29, 2022 at 10:28:32PM +0530, Pankaj Jangid wrote:
> Sorry for the Wrong subject line earlier.
>
> Pankaj Jangid writes:
>
> > I have setup a new system. Apart from the display related issue, that I
> > had posted in another thread, I am facing an issue related to my
> > external
Sorry for the Wrong subject line earlier.
Pankaj Jangid writes:
> I have setup a new system. Apart from the display related issue, that I
> had posted in another thread, I am facing an issue related to my
> external ‘Yeti Blue’ sound card. I use it as Mic and Monitor audio.
>
> pankaj@anant:~$
17 matches
Mail list logo
