Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #244759 > unrolled thread

USB sound device present but visible in ‘alsamixer’

Back to article view | Back to linux.debian.user

Contents

  USB sound device present but visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-29 07:30 +0100
    Re: USB sound device present but NOT visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-29 18:00 +0100
      Re: USB sound device present but NOT visible in ‘alsamixer’ "Andrew M.A. Cater" <amacater@einval.com> - 2022-01-29 18:30 +0100
        Re: USB sound device present but NOT visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-30 04:50 +0100
          Re: USB sound device present but NOT visible in ‘alsamixer’ Jude DaShiell <jdashiel@panix.com> - 2022-01-30 05:30 +0100
            Re: USB sound device present but NOT visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-30 06:40 +0100
              Re: USB sound device present but NOT visible in ‘alsamixer’ Jude DaShiell <jdashiel@panix.com> - 2022-01-30 06:40 +0100
                Re: USB sound device present but NOT visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-30 07:00 +0100
                  Re: USB sound device present but NOT visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-30 08:10 +0100
                  Re: USB sound device present but NOT visible in ‘alsamixer’ Jude DaShiell <jdashiel@panix.com> - 2022-01-30 10:00 +0100
                    Re: USB sound device present but NOT visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-30 10:10 +0100
              Re: USB sound device present but NOT visible in ‘alsamixer’ Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-30 08:10 +0100
                Re: USB sound device present but NOT visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-30 08:20 +0100
                  Re: USB sound device present but NOT visible in ‘alsamixer’ Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-30 09:40 +0100
                    Re: USB sound device present but NOT visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-30 10:30 +0100
                      Re: USB sound device present but NOT visible in ‘alsamixer’ Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-30 12:40 +0100
                        Re: USB sound device present but NOT visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-01-30 21:20 +0100
                          Re: USB sound device present but NOT visible in ‘alsamixer’ Jude DaShiell <jdashiel@panix.com> - 2022-01-31 00:40 +0100
    Re: USB sound device present but visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-02-06 16:50 +0100
      Re: USB sound device present but visible in ‘alsamixer’ Nicholas Geovanis <nickgeovanis@gmail.com> - 2022-02-08 06:10 +0100
        Re: USB sound device present but visible in ‘alsamixer’ Pankaj Jangid <pankaj@codeisgreat.org> - 2022-02-09 14:00 +0100

Page 1 of 2  [1] 2  Next page →

#244759 — USB sound device present but visible in ‘alsamixer’

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.

--8<---------------cut here---------------start------------->8---
pankaj@anant:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye
pankaj@anant:~$ uname -a
Linux anant 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux
--8<---------------cut here---------------end--------------->8---

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 devices.

However, ‘lsusb’ shows it and ‘/proc/asound/cards’ has an entry. But
these devices (mic and speaker) are not taking any input or producing
sound. Because they are not visible to Gnome and ‘alsamixer’.

--8<---------------cut here---------------start------------->8---
pankaj@anant:~$ lsusb
Bus 006 Device 002: ID 2109:0813 VIA Labs, Inc. VL813 Hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 002: ID 2109:2813 VIA Labs, Inc. VL813 Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 002: ID 0db0:a073 Micro Star International USB Audio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 1462:7d54 Micro Star International MYSTIC LIGHT 
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 1b1c:1b75 Corsair CORSAIR HARPOON RGB PRO Gaming Mouse
Bus 001 Device 015: ID 8087:0032 Intel Corp. 
Bus 001 Device 003: ID 046d:0ab7 Logitech, Inc. Blue Microphones
Bus 001 Device 002: ID 13ba:0018 PCPlay Barcode PCP-BCG4209
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pankaj@anant:~$ cat /proc/asound/cards
 0 [HDMI_1         ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xfca60000 irq 102
 1 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xfce60000 irq 104
 2 [Generic        ]: HDA-Intel - HD-Audio Generic
                      HD-Audio Generic at 0xfcd00000 irq 106
 3 [Microphones    ]: USB-Audio - Blue Microphones
                      Generic Blue Microphones at usb-0000:2a:00.1-2, high speed
 4 [Audio          ]: USB-Audio - USB Audio
                      Generic USB Audio at usb-0000:2a:00.3-5, high speed
--8<---------------cut here---------------end--------------->8---

I have tried to restart just the sound subsystem using
‘/etc/init.d/asound restart’. But it did not lead to any good
results.

Can somebody tell me what could be wrong at my end?

Regards ~Pankaj

[toc] | [next] | [standalone]

#244766 — Re: USB sound device present but NOT visible in ‘alsamixer’

Sorry for the Wrong subject line earlier.

Pankaj Jangid <pankaj@codeisgreat.org> 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:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID:	Debian
> Description:	Debian GNU/Linux 11 (bullseye)
> Release:	11
> Codename:	bullseye
> pankaj@anant:~$ uname -a
> Linux anant 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux
>
>
> 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 devices.
>
> However, ‘lsusb’ shows it and ‘/proc/asound/cards’ has an entry. But
> these devices (mic and speaker) are not taking any input or producing
> sound. Because they are not visible to Gnome and ‘alsamixer’.
>
> pankaj@anant:~$ lsusb
> Bus 006 Device 002: ID 2109:0813 VIA Labs, Inc. VL813 Hub
> Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 005 Device 002: ID 2109:2813 VIA Labs, Inc. VL813 Hub
> Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
> Bus 003 Device 002: ID 0db0:a073 Micro Star International USB Audio
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 007: ID 1462:7d54 Micro Star International MYSTIC LIGHT 
> Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
> Bus 001 Device 005: ID 1b1c:1b75 Corsair CORSAIR HARPOON RGB PRO Gaming Mouse
> Bus 001 Device 015: ID 8087:0032 Intel Corp. 
> Bus 001 Device 003: ID 046d:0ab7 Logitech, Inc. Blue Microphones
> Bus 001 Device 002: ID 13ba:0018 PCPlay Barcode PCP-BCG4209
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> pankaj@anant:~$ cat /proc/asound/cards
>  0 [HDMI_1         ]: HDA-Intel - HDA ATI HDMI
>                       HDA ATI HDMI at 0xfca60000 irq 102
>  1 [HDMI           ]: HDA-Intel - HDA ATI HDMI
>                       HDA ATI HDMI at 0xfce60000 irq 104
>  2 [Generic        ]: HDA-Intel - HD-Audio Generic
>                       HD-Audio Generic at 0xfcd00000 irq 106
>  3 [Microphones    ]: USB-Audio - Blue Microphones
>                       Generic Blue Microphones at usb-0000:2a:00.1-2, high speed
>  4 [Audio          ]: USB-Audio - USB Audio
>                       Generic USB Audio at usb-0000:2a:00.3-5, high speed
>
> I have tried to restart just the sound subsystem using
> ‘/etc/init.d/asound restart’. But it did not lead to any good
> results.
>
> Can somebody tell me what could be wrong at my end?
>
> Regards ~Pankaj

[toc] | [prev] | [next] | [standalone]

#244767 — Re: USB sound device present but NOT visible in ‘alsamixer’

On Sat, Jan 29, 2022 at 10:28:32PM +0530, Pankaj Jangid wrote:
> Sorry for the Wrong subject line earlier.
> 
> Pankaj Jangid <pankaj@codeisgreat.org> 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:~$ lsb_release -a
> > No LSB modules are available.
> > Distributor ID:	Debian
> > Description:	Debian GNU/Linux 11 (bullseye)
> > Release:	11
> > Codename:	bullseye
> > pankaj@anant:~$ uname -a
> > Linux anant 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux
> >
> >
> > 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 devices.
> >
> > However, ‘lsusb’ shows it and ‘/proc/asound/cards’ has an entry. But
> > these devices (mic and speaker) are not taking any input or producing
> > sound. Because they are not visible to Gnome and ‘alsamixer’.
> >
> > pankaj@anant:~$ lsusb
> > Bus 006 Device 002: ID 2109:0813 VIA Labs, Inc. VL813 Hub
> > Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 005 Device 002: ID 2109:2813 VIA Labs, Inc. VL813 Hub
> > Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
> > Bus 003 Device 002: ID 0db0:a073 Micro Star International USB Audio
> > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 001 Device 007: ID 1462:7d54 Micro Star International MYSTIC LIGHT 
> > Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
> > Bus 001 Device 005: ID 1b1c:1b75 Corsair CORSAIR HARPOON RGB PRO Gaming Mouse
> > Bus 001 Device 015: ID 8087:0032 Intel Corp. 
> > Bus 001 Device 003: ID 046d:0ab7 Logitech, Inc. Blue Microphones
> > Bus 001 Device 002: ID 13ba:0018 PCPlay Barcode PCP-BCG4209
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > pankaj@anant:~$ cat /proc/asound/cards
> >  0 [HDMI_1         ]: HDA-Intel - HDA ATI HDMI
> >                       HDA ATI HDMI at 0xfca60000 irq 102
> >  1 [HDMI           ]: HDA-Intel - HDA ATI HDMI
> >                       HDA ATI HDMI at 0xfce60000 irq 104
> >  2 [Generic        ]: HDA-Intel - HD-Audio Generic
> >                       HD-Audio Generic at 0xfcd00000 irq 106
> >  3 [Microphones    ]: USB-Audio - Blue Microphones
> >                       Generic Blue Microphones at usb-0000:2a:00.1-2, high speed
> >  4 [Audio          ]: USB-Audio - USB Audio
> >                       Generic USB Audio at usb-0000:2a:00.3-5, high speed
> >
> > I have tried to restart just the sound subsystem using
> > ‘/etc/init.d/asound restart’. But it did not lead to any good
> > results.
> >
> > Can somebody tell me what could be wrong at my end?
> >
> > Regards ~Pankaj


Hi Pankaj,

It might be nothing more than the power handling, sleep modes and USB 
enumeration after a laptop goes to sleep.

If you unplug/replug the USB plug which is the external sound card, is
it magically recognised again?

All the very best, as ever,

Andy Cater
> 

[toc] | [prev] | [next] | [standalone]

#244795 — Re: USB sound device present but NOT visible in ‘alsamixer’

"Andrew M.A. Cater" <amacater@einval.com> writes:

>> Pankaj Jangid <pankaj@codeisgreat.org> 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 devices.
>> >
> It might be nothing more than the power handling, sleep modes and USB 
> enumeration after a laptop goes to sleep.
>
> If you unplug/replug the USB plug which is the external sound card, is
> it magically recognised again?

Thanks Andy, for the reply. I really appreciate this gesture.

And I am sorry I wasn’t complete in the original email. I had tried to
unplug and replug. But that also doesn’t list the device in ‘alsamixer’
and hence doesn’t work after a suspend/wakeup operation.

Is there a way to force the scan of USB sound devices manually if that
is not happening automatically? As I had posted earlier that ‘lsusb’ and
‘cat /proc/asound/cards’ do list the device. It is just that ALSA is not
seeing it.


Regards ~Pankaj

[toc] | [prev] | [next] | [standalone]

#244797 — Re: USB sound device present but NOT visible in ‘alsamixer’

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 wrote:

> "Andrew M.A. Cater" <amacater@einval.com> writes:
>
> >> Pankaj Jangid <pankaj@codeisgreat.org> 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 devices.
> >> >
> > It might be nothing more than the power handling, sleep modes and USB
> > enumeration after a laptop goes to sleep.
> >
> > If you unplug/replug the USB plug which is the external sound card, is
> > it magically recognised again?
>
> Thanks Andy, for the reply. I really appreciate this gesture.
>
> And I am sorry I wasn?t complete in the original email. I had tried to
> unplug and replug. But that also doesn?t list the device in ?alsamixer?
> and hence doesn?t work after a suspend/wakeup operation.
>
> Is there a way to force the scan of USB sound devices manually if that
> is not happening automatically? As I had posted earlier that ?lsusb? and
> ?cat /proc/asound/cards? do list the device. It is just that ALSA is not
> seeing it.
>
>
> Regards ~Pankaj
>
>

[toc] | [prev] | [next] | [standalone]

#244799 — Re: USB sound device present but NOT visible in ‘alsamixer’

Jude DaShiell <jdashiel@panix.com> 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.
>
Thanks Jude, for the reply.

On my installation there is no ‘--init’ option. But it has ‘init’
command. I just tried that ‘alsactl init’. And there is no
‘/var/lock/alsa’ directory. But there is
‘/var/lock/asound.state.lock’. I removed this and tried with ‘alsactl
init’ again. But no positive results in both cases.

During the boot process, the system detects everything. So there must be
something in the init sequence that I can trigger manually.

Regards ~Pankaj

[toc] | [prev] | [next] | [standalone]

#244800 — Re: USB sound device present but NOT visible in ‘alsamixer’

alsactl init I think will find everything.


On Sun, 30 Jan 2022, Pankaj Jangid wrote:

> Jude DaShiell <jdashiel@panix.com> 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.
> >
> Thanks Jude, for the reply.
>
> On my installation there is no ?--init? option. But it has ?init?
> command. I just tried that ?alsactl init?. And there is no
> ?/var/lock/alsa? directory. But there is
> ?/var/lock/asound.state.lock?. I removed this and tried with ?alsactl
> init? again. But no positive results in both cases.
>
> During the boot process, the system detects everything. So there must be
> something in the init sequence that I can trigger manually.
>
> Regards ~Pankaj
>
>

[toc] | [prev] | [next] | [standalone]

#244802 — Re: USB sound device present but NOT visible in ‘alsamixer’

Jude DaShiell <jdashiel@panix.com> 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".

[toc] | [prev] | [next] | [standalone]

#244807 — Re: USB sound device present but NOT visible in ‘alsamixer’

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> Jude DaShiell <jdashiel@panix.com> 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 should have attached this before as well. The "alsactl init" command
is producing error messages as well. See this,

--8<---------------cut here---------------start------------->8---
pankaj@anant:~$ sudo alsactl init
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xfca60000 irq 102)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" "0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xfce60000 irq 120)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" "0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HD-Audio Generic at 0xfcd00000 irq 122)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -6
Found hardware: "HDA-Intel" "" "" "0x1462" "0xed54"
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:3 use case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB046d:0ab7" "" ""
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:4 use case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB0db0:a073" "" ""
Hardware is initialized using a generic method
--8<---------------cut here---------------end--------------->8---

[toc] | [prev] | [next] | [standalone]

#244811 — Re: USB sound device present but NOT visible in ‘alsamixer’

rm /var/lock/asound.state.lock


On Sun, 30 Jan 2022, Pankaj Jangid wrote:

> Jude DaShiell <jdashiel@panix.com> 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".
>
>
>

[toc] | [prev] | [next] | [standalone]

#244812 — Re: USB sound device present but NOT visible in ‘alsamixer’

Jude DaShiell <jdashiel@panix.com> 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
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xfca60000 irq 118)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" "0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xfce60000 irq 120)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" "0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HD-Audio Generic at 0xfcd00000 irq 122)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -6
Found hardware: "HDA-Intel" "" "" "0x1462" "0xed54"
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:3 use case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB046d:0ab7" "" ""
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:4 use case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB0db0:a073" "" ""
Hardware is initialized using a generic method
--8<---------------cut here---------------end--------------->8---

Regards ~Pankaj

[toc] | [prev] | [next] | [standalone]

#244806 — Re: USB sound device present but NOT visible in ‘alsamixer’

[Multipart message — attachments visible in raw view] — view raw

On Du, 30 ian 22, 11:02:34, Pankaj Jangid wrote:
> Jude DaShiell <jdashiel@panix.com> 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.
> >
> Thanks Jude, for the reply.
> 
> On my installation there is no ‘--init’ option. But it has ‘init’
> command. I just tried that ‘alsactl init’. And there is no
> ‘/var/lock/alsa’ directory. But there is
> ‘/var/lock/asound.state.lock’. I removed this and tried with ‘alsactl
> init’ again. But no positive results in both cases.
> 
> 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 probably snd-usb-audio)

If it works it might be possible to add the module to some list so that 
it is removed on suspend and loaded on resume.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#244808 — Re: USB sound device present but NOT visible in ‘alsamixer’

Andrei POPESCU <andreimpopescu@gmail.com> 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 probably snd-usb-audio)
>
> If it works it might be possible to add the module to some list so that 
> it is removed on suspend and loaded on resume.

Thanks Andrei.

"lsmod|grep snd" results in,

--8<---------------cut here---------------start------------->8---
pankaj@anant:~$ sudo lsmod |grep snd
snd_usb_audio         315392  3
snd_usbmidi_lib        40960  1 snd_usb_audio
snd_rawmidi            45056  1 snd_usbmidi_lib
snd_seq_device         16384  1 snd_rawmidi
mc                     61440  1 snd_usb_audio
snd_hda_codec_hdmi     73728  2
snd_hda_intel          57344  3
snd_intel_dspcfg       28672  1 snd_hda_intel
soundwire_intel        45056  1 snd_intel_dspcfg
snd_soc_core          315392  1 soundwire_intel
snd_compress           32768  1 snd_soc_core
snd_hda_codec         172032  2 snd_hda_codec_hdmi,snd_hda_intel
snd_hda_core          110592  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_hwdep              16384  2 snd_usb_audio,snd_hda_codec
snd_pcm               135168  8 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,soundwire_intel,snd_compress,snd_soc_core,snd_hda_core
snd_timer              49152  1 snd_pcm
snd                   110592  24 snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi
soundcore              16384  1 snd
usbcore               323584  6 xhci_hcd,snd_usb_audio,usbhid,snd_usbmidi_lib,btusb,xhci_pci
--8<---------------cut here---------------end--------------->8---

when I say "modprobe -r snd_usb_audio". It says "Module snd_usb_audio is
in use". I tried with "-f" option as well. Still cannot unload. Then I
tried to it again after "alsactl kill quit"; but still cannot unload.

Also "alsactl init" is producing some errors also. I shared in my
previous email. Copying here again for the context.

--8<---------------cut here---------------start------------->8---
pankaj@anant:~$ sudo alsactl init
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xfca60000 irq 102)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" "0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HDA ATI HDMI at 0xfce60000 irq 120)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100700" "0x1462" "0xaaf0"
Hardware is initialized using a generic method
alsa-lib parser.c:260:(error_node) UCM is not supported for this HDA model (HD-Audio Generic at 0xfcd00000 irq 122)
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -6
Found hardware: "HDA-Intel" "" "" "0x1462" "0xed54"
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:3 use case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB046d:0ab7" "" ""
Hardware is initialized using a generic method
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:4 use case configuration -2
Found hardware: "USB-Audio" "USB Mixer" "USB0db0:a073" "" ""
Hardware is initialized using a generic method
--8<---------------cut here---------------end--------------->8---

What other options may I try?


Regards ~Pankaj

[toc] | [prev] | [next] | [standalone]

#244809 — Re: USB sound device present but NOT visible in ‘alsamixer’

[Multipart message — attachments visible in raw view] — view raw

On Du, 30 ian 22, 12:47:27, Pankaj Jangid wrote:
> Andrei POPESCU <andreimpopescu@gmail.com> 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 probably snd-usb-audio)
> >
> > If it works it might be possible to add the module to some list so that 
> > it is removed on suspend and loaded on resume.
> 
> Thanks Andrei.
> 
> "lsmod|grep snd" results in,
> 
> --8<---------------cut here---------------start------------->8---
> pankaj@anant:~$ sudo lsmod |grep snd
> snd_usb_audio         315392  3
> snd_usbmidi_lib        40960  1 snd_usb_audio
> snd_rawmidi            45056  1 snd_usbmidi_lib
> snd_seq_device         16384  1 snd_rawmidi
> mc                     61440  1 snd_usb_audio
> snd_hda_codec_hdmi     73728  2
> snd_hda_intel          57344  3
> snd_intel_dspcfg       28672  1 snd_hda_intel
> soundwire_intel        45056  1 snd_intel_dspcfg
> snd_soc_core          315392  1 soundwire_intel
> snd_compress           32768  1 snd_soc_core
> snd_hda_codec         172032  2 snd_hda_codec_hdmi,snd_hda_intel
> snd_hda_core          110592  3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
> snd_hwdep              16384  2 snd_usb_audio,snd_hda_codec
> snd_pcm               135168  8 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,soundwire_intel,snd_compress,snd_soc_core,snd_hda_core
> snd_timer              49152  1 snd_pcm
> snd                   110592  24 snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi
> soundcore              16384  1 snd
> usbcore               323584  6 xhci_hcd,snd_usb_audio,usbhid,snd_usbmidi_lib,btusb,xhci_pci
> --8<---------------cut here---------------end--------------->8---
> 
> when I say "modprobe -r snd_usb_audio". It says "Module snd_usb_audio is
> in use". I tried with "-f" option as well. Still cannot unload. Then I
> tried to it again after "alsactl kill quit"; but still cannot unload.

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 is the process number).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#244813 — Re: USB sound device present but NOT visible in ‘alsamixer’

Andrei POPESCU <andreimpopescu@gmail.com> 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 is the process number).

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 snd_usb_audio (using lsof)
5. Unloaded module using "modprobe -r"
6. Loaded again using "modeprob"
7. Started pulseaudio again

Still the device is not listed in alsamixer and hence cannot play.

"alsactl init" also producing same errors as before.

Regards ~Pankaj

[toc] | [prev] | [next] | [standalone]

#244814 — Re: USB sound device present but NOT visible in ‘alsamixer’

[Multipart message — attachments visible in raw view] — view raw

On Du, 30 ian 22, 14:58:29, Pankaj Jangid wrote:
> Andrei POPESCU <andreimpopescu@gmail.com> 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 is the process number).
> 
> 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 snd_usb_audio (using lsof)
> 5. Unloaded module using "modprobe -r"
> 6. Loaded again using "modeprob"
> 7. Started pulseaudio again
> 
> Still the device is not listed in alsamixer and hence cannot play.
> 
> "alsactl init" also producing same errors as before.

Try also unplugging the device after removing the module.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#244821 — Re: USB sound device present but NOT visible in ‘alsamixer’

Andrei POPESCU <andreimpopescu@gmail.com> 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 snd_usb_audio (using lsof)
>> 5. Unloaded module using "modprobe -r"
>> 6. Loaded again using "modeprob"
>> 7. Started pulseaudio again
>> 
>> Still the device is not listed in alsamixer and hence cannot play.
>> 
>> "alsactl init" also producing same errors as before.
>
> Try also unplugging the device after removing the module.
>

After step 5, I unplugged the device and plugged it again and then
followed 6, 7. Now the interval sound card is also not visible; that was
showing as generic usb.

Regards ~Pankaj

[toc] | [prev] | [next] | [standalone]

#244831 — Re: USB sound device present but NOT visible in ‘alsamixer’

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 <andreimpopescu@gmail.com> 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 snd_usb_audio (using lsof)
> >> 5. Unloaded module using "modprobe -r"
> >> 6. Loaded again using "modeprob"
> >> 7. Started pulseaudio again
> >>
> >> Still the device is not listed in alsamixer and hence cannot play.
> >>
> >> "alsactl init" also producing same errors as before.
> >
> > Try also unplugging the device after removing the module.
> >
>
> After step 5, I unplugged the device and plugged it again and then
> followed 6, 7. Now the interval sound card is also not visible; that was
> showing as generic usb.
>
> Regards ~Pankaj
>
>
>

[toc] | [prev] | [next] | [standalone]

#245044

Pankaj Jangid <pankaj@codeisgreat.org> 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 devices.
>
> However, ‘lsusb’ shows it and ‘/proc/asound/cards’ has an entry. But
> these devices (mic and speaker) are not taking any input or producing
> sound. Because they are not visible to Gnome and ‘alsamixer’.
>
> pankaj@anant:~$ lsusb
> ...
> Bus 001 Device 003: ID 046d:0ab7 Logitech, Inc. Blue Microphones
> ...
> pankaj@anant:~$ cat /proc/asound/cards
> ...
>  3 [Microphones    ]: USB-Audio - Blue Microphones
>                       Generic Blue Microphones at usb-0000:2a:00.1-2, high speed
> ...

I am trying to make it work; so here is the update.

I tried to experiment with my machine and found that if I plug-out and
plug-in the USB sound card again, it is not shown by "aplay -l" command
as normal user. But when I do "sudo aplay -l" it lists the USB
device. But I am part of "audio" group. "groups" command output:

--8<---------------cut here---------------start------------->8---
ankaj@anant:~$ groups
pankaj cdrom floppy sudo audio dip video plugdev netdev bluetooth scanner docker
--8<---------------cut here---------------end--------------->8---

I don’t know what other configuration is required to list my card using
"aplay -l" as a normal user? It lists the card when I reboot the
machine. But not when I plug-out and plug-in again. Any hints for this?

This could be root cause of my original problem i.e. no sound after
sleep and wake-up.

[toc] | [prev] | [next] | [standalone]

#245089

[Multipart message — attachments visible in raw view] — view raw

On Sun, Feb 6, 2022, 9:42 AM Pankaj Jangid <pankaj@codeisgreat.org> wrote:

> Pankaj Jangid <pankaj@codeisgreat.org> 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 devices.
> >
> > However, ‘lsusb’ shows it and ‘/proc/asound/cards’ has an entry. But
> > these devices (mic and speaker) are not taking any input or producing
> > sound. Because they are not visible to Gnome and ‘alsamixer’.
> >
> > pankaj@anant:~$ lsusb
> > ...
> > Bus 001 Device 003: ID 046d:0ab7 Logitech, Inc. Blue Microphones
> > ...
> > pankaj@anant:~$ cat /proc/asound/cards
> > ...
> >  3 [Microphones    ]: USB-Audio - Blue Microphones
> >                       Generic Blue Microphones at usb-0000:2a:00.1-2,
> high speed
> > ...
>
> I am trying to make it work; so here is the update.
>
> I tried to experiment with my machine and found that if I plug-out and
> plug-in the USB sound card again, it is not shown by "aplay -l" command
> as normal user. But when I do "sudo aplay -l" it lists the USB
> device. But I am part of "audio" group. "groups" command output:
>
> --8<---------------cut here---------------start------------->8---
> ankaj@anant:~$ groups
> pankaj cdrom floppy sudo audio dip video plugdev netdev bluetooth scanner
> docker
> --8<---------------cut here---------------end--------------->8---
>
> I don’t know what other configuration is required to list my card using
> "aplay -l" as a normal user?


You may need to give normal users added privileges. Or it may be that you
need to set your running group or user identity to something else in order
to use aplay effectively. Could that be the group named audio?

See help for the newgrp command. Or just as you have done, try to craft the
right sudo command to invoke it the way you want. Then you could add a
shorthand to it in sudoers or create a shell alias accordingly.

Or, not recommended, you could change the aplay executable or front-end to
it in order to make it a set[ug]id executable.

It lists the card when I reboot the
> machine. But not when I plug-out and plug-in again. Any hints for this?
>
> This could be root cause of my original problem i.e. no sound after
> sleep and wake-up.
>
>
>

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web