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

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

Sound in Stretch

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

Contents

  Sound in Stretch Joe <joe@jretrading.com> - 2018-09-10 22:20 +0200
    Re: Sound in Stretch Greg Wooledge <wooledg@eeg.ccf.org> - 2018-09-10 22:30 +0200
      Re: Sound in Stretch Joe <joe@jretrading.com> - 2018-09-10 22:40 +0200
        Re: Sound in Stretch deloptes <deloptes@gmail.com> - 2018-09-10 23:00 +0200
          Re: Sound in Stretch arne <sp113438@telfort.nl> - 2018-09-10 23:30 +0200
            Re: Sound in Stretch Joe <joe@jretrading.com> - 2018-09-11 00:00 +0200
              Re: Sound in Stretch Joe <joe@jretrading.com> - 2018-09-11 00:00 +0200
                Re: Sound in Stretch deloptes <deloptes@gmail.com> - 2018-09-11 08:30 +0200
              Re: Sound in Stretch Greg Wooledge <wooledg@eeg.ccf.org> - 2018-09-11 15:00 +0200
                Re: Sound in Stretch Joe <joe@jretrading.com> - 2018-09-12 22:30 +0200
                  Re: Sound in Stretch deloptes <deloptes@gmail.com> - 2018-09-12 23:30 +0200
            Re: Sound in Stretch deloptes <deloptes@gmail.com> - 2018-09-11 08:20 +0200
              Re: Sound in Stretch Curt <curty@free.fr> - 2018-09-11 09:30 +0200
                Re: Sound in Stretch deloptes <deloptes@gmail.com> - 2018-09-11 11:40 +0200
            Re: Sound in Stretch Jude DaShiell <jdashiel@panix.com> - 2018-09-12 21:20 +0200
        Re: Sound in Stretch <tomas@tuxteam.de> - 2018-09-10 23:00 +0200
          Re: Sound in Stretch Joe <joe@jretrading.com> - 2018-09-11 00:00 +0200
            Re: Sound in Stretch deloptes <deloptes@gmail.com> - 2018-09-11 08:30 +0200
              Re: Sound in Stretch Brian <ad44@cityscape.co.uk> - 2018-09-11 09:50 +0200
              Re: Sound in Stretch Joe <joe@jretrading.com> - 2018-09-11 11:00 +0200
                Re: Sound in Stretch deloptes <deloptes@gmail.com> - 2018-09-11 11:30 +0200
                Re: Sound in Stretch deloptes <deloptes@gmail.com> - 2018-09-13 08:40 +0200
                  Re: Sound in Stretch Joe <joe@jretrading.com> - 2018-09-13 10:20 +0200
                    Re: Sound in Stretch [SOLVED] Joe <joe@jretrading.com> - 2018-09-13 12:40 +0200
                      Re: Sound in Stretch [SOLVED] Jude DaShiell <jdashiel@panix.com> - 2018-09-13 13:40 +0200
                        Re: Sound in Stretch [SOLVED] deloptes <deloptes@gmail.com> - 2018-09-13 19:50 +0200
                          Re: Sound in Stretch [SOLVED] Joe <joe@jretrading.com> - 2018-09-13 21:50 +0200
                            Re: Sound in Stretch [SOLVED] Brian <ad44@cityscape.co.uk> - 2018-09-13 22:10 +0200
                              Re: Sound in Stretch [SOLVED] Joe <joe@jretrading.com> - 2018-09-14 00:10 +0200
      Re: Sound in Stretch Ric Moore <wayward4now@gmail.com> - 2018-09-11 03:30 +0200
    Re: Sound in Stretch Brian <ad44@cityscape.co.uk> - 2018-09-11 00:00 +0200
      Re: Sound in Stretch deloptes <deloptes@gmail.com> - 2018-09-11 08:40 +0200
        Re: Sound in Stretch Brian <ad44@cityscape.co.uk> - 2018-09-11 09:50 +0200

Page 1 of 2  [1] 2  Next page →

#199945 — Sound in Stretch

There's no alsa-base in Stretch. 

Should there be some other way of producing sounds?

-- 
Joe

[toc] | [next] | [standalone]

#199946

On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote:
> 
> There's no alsa-base in Stretch. 
> 
> Should there be some other way of producing sounds?

If you're looking for alsamixer, it's in alsa-utils.  ALSA should just
work out of the box for most users who skip the Desktop Environment
during the installation (and therefore do not have to circumvent pulse).

The only steps required for most people are to install alsa-utils,
run alsamixer, unmute the master channels, and raise the volume of the
master channels above zero.

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

#199948

On Mon, 10 Sep 2018 16:22:38 -0400
Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote:
> > 
> > There's no alsa-base in Stretch. 
> > 
> > Should there be some other way of producing sounds?  
> 
> If you're looking for alsamixer, it's in alsa-utils.  ALSA should just
> work out of the box for most users who skip the Desktop Environment
> during the installation (and therefore do not have to circumvent
> pulse).
> 
> The only steps required for most people are to install alsa-utils,
> run alsamixer, unmute the master channels, and raise the volume of the
> master channels above zero.
> 

Thank you for an extremely prompt reply, but I've been there and done
that:

alsa-utils is already installed at the requested version (1.1.3-1)

alsamixer

cannot open mixer: No such file or directory

I always used to start sound troubleshooting by looking in /proc/asound
to find out what the system thought my sound cards were, but that
directory no longer exists.

This, by the way, is a clean no-X installation of Stretch, running in
hardware that previously ran Wheezy, with working sound. The sound
'card' is a cheap generic USB thing, which the kernel is seeing.
Various sound modules are loaded. I presume I've got to install or
configure something else, but I can't find the slightest clue on the
Net. One Debian sound page refers to Sarge...

-- 
Joe

-- 
Joe

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

#199949

Joe wrote:

> alsamixer
> 
> cannot open mixer: No such file or directory
> 
> I always used to start sound troubleshooting by looking in /proc/asound
> to find out what the system thought my sound cards were, but that
> directory no longer exists.

you sure you have the driver loaded?

ls -al /proc/asound/
total 0
dr-xr-xr-x   6 root root 0 Sep 10 19:50 .
dr-xr-xr-x 253 root root 0 Sep 10 21:49 ..
dr-xr-xr-x   8 root root 0 Sep 10 19:50 card0
dr-xr-xr-x   3 root root 0 Sep 10 19:50 card1
-r--r--r--   1 root root 0 Sep 10 19:50 cards
-r--r--r--   1 root root 0 Sep 10 22:48 devices
-r--r--r--   1 root root 0 Sep 10 22:48 hwdep
-r--r--r--   1 root root 0 Sep 10 22:48 modules
dr-xr-xr-x   2 root root 0 Sep 10 22:48 oss
lrwxrwxrwx   1 root root 5 Sep 10 22:48 PCH -> card0
-r--r--r--   1 root root 0 Sep 10 22:48 pcm
dr-xr-xr-x   2 root root 0 Sep 10 22:48 seq
-r--r--r--   1 root root 0 Sep 10 22:48 timers
-r--r--r--   1 root root 0 Sep 10 22:48 version
lrwxrwxrwx   1 root root 5 Sep 10 22:48 Webcam -> card1

stretch

regards

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

#199951

On Mon, 10 Sep 2018 22:49:34 +0200
deloptes <deloptes@gmail.com> wrote:

> Joe wrote:
> 
> > alsamixer
> > 
> > cannot open mixer: No such file or directory
> > 
> > I always used to start sound troubleshooting by looking
> > in /proc/asound to find out what the system thought my sound cards
> > were, but that directory no longer exists.  
> 
> you sure you have the driver loaded?
> 
> ls -al /proc/asound/
> total 0
> dr-xr-xr-x   6 root root 0 Sep 10 19:50 .
> dr-xr-xr-x 253 root root 0 Sep 10 21:49 ..
> dr-xr-xr-x   8 root root 0 Sep 10 19:50 card0
> dr-xr-xr-x   3 root root 0 Sep 10 19:50 card1
> -r--r--r--   1 root root 0 Sep 10 19:50 cards
> -r--r--r--   1 root root 0 Sep 10 22:48 devices
> -r--r--r--   1 root root 0 Sep 10 22:48 hwdep
> -r--r--r--   1 root root 0 Sep 10 22:48 modules
> dr-xr-xr-x   2 root root 0 Sep 10 22:48 oss
> lrwxrwxrwx   1 root root 5 Sep 10 22:48 PCH -> card0
> -r--r--r--   1 root root 0 Sep 10 22:48 pcm
> dr-xr-xr-x   2 root root 0 Sep 10 22:48 seq
> -r--r--r--   1 root root 0 Sep 10 22:48 timers
> -r--r--r--   1 root root 0 Sep 10 22:48 version
> lrwxrwxrwx   1 root root 5 Sep 10 22:48 Webcam -> card1
> 
> stretch
> 
> regards
> 

does the command alsa-info give a clue?

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

#199952

On Mon, 10 Sep 2018 23:26:56 +0200
arne <sp113438@telfort.nl> wrote:

> On Mon, 10 Sep 2018 22:49:34 +0200
> deloptes <deloptes@gmail.com> wrote:
> 
> > Joe wrote:
> >   
> > > alsamixer
> > > 
> > > cannot open mixer: No such file or directory
> > > 
> > > I always used to start sound troubleshooting by looking
> > > in /proc/asound to find out what the system thought my sound cards
> > > were, but that directory no longer exists.    
> > 
> > you sure you have the driver loaded?


I have sound modules loaded, which I thought meant the driver must have
been found.

> > 
> > ls -al /proc/asound/
> > total 0
> > dr-xr-xr-x   6 root root 0 Sep 10 19:50 .
> > dr-xr-xr-x 253 root root 0 Sep 10 21:49 ..
> > dr-xr-xr-x   8 root root 0 Sep 10 19:50 card0
> > dr-xr-xr-x   3 root root 0 Sep 10 19:50 card1
> > -r--r--r--   1 root root 0 Sep 10 19:50 cards
> > -r--r--r--   1 root root 0 Sep 10 22:48 devices
> > -r--r--r--   1 root root 0 Sep 10 22:48 hwdep
> > -r--r--r--   1 root root 0 Sep 10 22:48 modules
> > dr-xr-xr-x   2 root root 0 Sep 10 22:48 oss
> > lrwxrwxrwx   1 root root 5 Sep 10 22:48 PCH -> card0
> > -r--r--r--   1 root root 0 Sep 10 22:48 pcm
> > dr-xr-xr-x   2 root root 0 Sep 10 22:48 seq
> > -r--r--r--   1 root root 0 Sep 10 22:48 timers
> > -r--r--r--   1 root root 0 Sep 10 22:48 version
> > lrwxrwxrwx   1 root root 5 Sep 10 22:48 Webcam -> card1
> > 
> > stretch
> > 
> > regards
> >   
> 
> does the command alsa-info give a clue?
> 

I didn't know about that one. It gives pages of stuff that look like
what I used to find in /proc/asound, it certainly knows all about the
USB device. No error messages, no suggestion as to what might be
missing.

-- 
Joe

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

#199953

On Mon, 10 Sep 2018 22:50:30 +0100
Joe <joe@jretrading.com> wrote:

> On Mon, 10 Sep 2018 23:26:56 +0200
> arne <sp113438@telfort.nl> wrote:
> 
> > On Mon, 10 Sep 2018 22:49:34 +0200
> > deloptes <deloptes@gmail.com> wrote:
> >   
> > > Joe wrote:
> > >     
> > > > alsamixer
> > > > 
> > > > cannot open mixer: No such file or directory
> > > > 
> > > > I always used to start sound troubleshooting by looking
> > > > in /proc/asound to find out what the system thought my sound
> > > > cards were, but that directory no longer exists.      
> > > 
> > > you sure you have the driver loaded?  
> 
> 
> I have sound modules loaded, which I thought meant the driver must
> have been found.
> 

It occurs to me that there are no snd_xxx_codec modules loaded. Is that
significant?

-- 
Joe

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

#199964

Joe wrote:

> It occurs to me that there are no snd_xxx_codec modules loaded. Is that
> significant?

yes - seems like - what is your sound card - manufacturer?

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

#199988

> > does the command alsa-info give a clue?
> 
> I didn't know about that one. It gives pages of stuff that look like
> what I used to find in /proc/asound, it certainly knows all about the
> USB device. No error messages, no suggestion as to what might be
> missing.

Since it's USB, the obvious next step is "lsusb".

Or, really, *any* information you can provide about this USB sound device
would be useful at this point.

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

#200071

On Tue, 11 Sep 2018 08:53:39 -0400
Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> > > does the command alsa-info give a clue?  
> > 
> > I didn't know about that one. It gives pages of stuff that look like
> > what I used to find in /proc/asound, it certainly knows all about
> > the USB device. No error messages, no suggestion as to what might be
> > missing.  
> 
> Since it's USB, the obvious next step is "lsusb".
> 
> Or, really, *any* information you can provide about this USB sound
> device would be useful at this point.
> 

OK, a bit more. After some crawling under furniture, I was able to plug
the device into my netbook, running 32-bit Stretch. It works fine
there. I did lsmod, and apart from some snd_hda_ modules for the
built-in sound, there are no modules there that aren't also in the
server. The codecs are all HDA.

Back on the server:

~$ sudo lsusb
.
.
Bus 004 Device 005: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like
Sound Device .
.

That's not on any compatibility list anywhere, but it has worked OK for
years on Wheezy on the same computer hardware. Anyway, USB is USB, and
there really shouldn't be compatibility issues for at least basic
playback. I'm not trying to record or use SPDIF.

~$ sudo lshw -C sound
  *-usb:1                   
       description: Audio device
       product: USB Sound Device
       vendor: C-Media Electronics, Inc.
       physical id: 5
       bus info: usb@4:5
       version: 0.10
       capabilities: usb-1.10 audio-control
       configuration: driver=usbhid maxpower=500mA speed=12Mbit/s

~$ sudo lsmod | grep usbhid
usbhid                 53248  0
hid                   122880  2 hid_generic,usbhid
usbcore               253952  9
usbhid,snd_usb_audio,usb_storage,ehci_hcd,ohci_pci,snd_usbmidi_lib,uas,ohci_hcd,ehci_pci

~$ sudo lsmod | grep snd
snd_usb_audio         180224  0
snd_usbmidi_lib        28672  1 snd_usb_audio
snd_hwdep              16384  1 snd_usb_audio
snd_rawmidi            32768  1 snd_usbmidi_lib
snd_seq_device         16384  1 snd_rawmidi
snd_pcm               110592  1 snd_usb_audio
snd_timer              32768  1 snd_pcm
snd                    86016  7
snd_hwdep,snd_usb_audio,snd_timer,snd_rawmidi,snd_usbmidi_lib,snd_seq_device,snd_pcm
soundcore              16384  1 snd usbcore               253952  9
usbhid,snd_usb_audio,usb_storage,ehci_hcd,ohci_pci,snd_usbmidi_lib,uas,ohci_hcd,ehci_pci

~$ speaker-test

speaker-test 1.1.3

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4528:(_snd_config_evaluate) function
snd_func_card_driver returned error: No such file or directory ALSA lib
confmisc.c:392:(snd_func_concat) error evaluating strings ALSA lib
conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned
error: No such file or directory ALSA lib
confmisc.c:1246:(snd_func_refer) error evaluating name ALSA lib
conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned
error: No such file or directory ALSA lib
conf.c:5007:(snd_config_expand) Evaluate error: No such file or
directory ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM
default Playback open error: -2,No such file or directory

Presumably this is just a fancy way of saying that /proc/asound isn't
there.

I did the alsa-info, but that produces a really huge ream of stuff, and
I can't see any errors or warnings in it. There was a warning flashed
up for a millisecond or two during the gathering of data: 

pcilib: sysfs_read_vpd: read failed: input/output error

but I'm not sure that is relevant. There is a long list of card
capabilities produced, so there's communication going on.

-- 
Joe

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

#200074

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

Joe wrote:

> That's not on any compatibility list anywhere, but it has worked OK for
> years on Wheezy on the same computer hardware. Anyway, USB is USB, and
> there really shouldn't be compatibility issues for at least basic
> playback. I'm not trying to record or use SPDIF.

could be that support in the snd_usb_audio driver is not provided anymore
for this device or is not working properly ... and BTW USB is not USB -
there is USB1, USB2 and now USB3

I still think if you don't see the device, the card is unsupported in the
usb audio driver

So I looked for you in the kernel config - it looks like the hid you find
are the audio jack controls, but I do not see the second one.

I think it is a problem with the codec or you need to load SND_HDA_GENERIC
and SND_HDA_CODEC_CMEDIA

perhaps they are not autoloaded

you could also try loading the intel hda driver, it should pull related (if
it succeeds to load without hardware)

regards

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

#199963

arne wrote:

> does the command alsa-info give a clue?

what is alsa-info?

$ alsa
alsabat    alsa_in    alsaloop   alsamixer  alsa_out   alsatplg   alsaucm

regards

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

#199967

On 2018-09-11, deloptes <deloptes@gmail.com> wrote:
> arne wrote:
>
>> does the command alsa-info give a clue?
>
> what is alsa-info?
>
> $ alsa
> alsabat    alsa_in    alsaloop   alsamixer  alsa_out   alsatplg   alsaucm
>
> regards
>
>

>

curty@einstein:~$ /usr/sbin/alsa
alsabat-test  alsactl       alsa-info     

You're a hacker all right, bless your heart.

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

#199977

Curt wrote:

> curty@einstein:~$ /usr/sbin/alsa
> alsabat-test  alsactl       alsa-info

thanks - i didn't look in sbin

regards

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

#200067

On Mon, 10 Sep 2018, arne wrote:

> Date: Mon, 10 Sep 2018 17:26:56
> From: arne <sp113438@telfort.nl>
> To: deloptes <deloptes@gmail.com>
> Cc: debian-user@lists.debian.org, sp113438@telfort.nl
> Subject: Re: Sound in Stretch
> Resent-Date: Mon, 10 Sep 2018 21:27:13 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
>
> On Mon, 10 Sep 2018 22:49:34 +0200
> deloptes <deloptes@gmail.com> wrote:
>
> > Joe wrote:
> >
> > > alsamixer
> > >
> > > cannot open mixer: No such file or directory
> > >
> > > I always used to start sound troubleshooting by looking
> > > in /proc/asound to find out what the system thought my sound cards
> > > were, but that directory no longer exists.
> >
> > you sure you have the driver loaded?
> >
> > ls -al /proc/asound/
> > total 0
> > dr-xr-xr-x   6 root root 0 Sep 10 19:50 .
> > dr-xr-xr-x 253 root root 0 Sep 10 21:49 ..
> > dr-xr-xr-x   8 root root 0 Sep 10 19:50 card0
> > dr-xr-xr-x   3 root root 0 Sep 10 19:50 card1
> > -r--r--r--   1 root root 0 Sep 10 19:50 cards
> > -r--r--r--   1 root root 0 Sep 10 22:48 devices
> > -r--r--r--   1 root root 0 Sep 10 22:48 hwdep
> > -r--r--r--   1 root root 0 Sep 10 22:48 modules
> > dr-xr-xr-x   2 root root 0 Sep 10 22:48 oss
> > lrwxrwxrwx   1 root root 5 Sep 10 22:48 PCH -> card0
> > -r--r--r--   1 root root 0 Sep 10 22:48 pcm
> > dr-xr-xr-x   2 root root 0 Sep 10 22:48 seq
> > -r--r--r--   1 root root 0 Sep 10 22:48 timers
> > -r--r--r--   1 root root 0 Sep 10 22:48 version
> > lrwxrwxrwx   1 root root 5 Sep 10 22:48 Webcam -> card1
> >
> > stretch
> >
> > regards
> >
>
> does the command alsa-info give a clue?
>
If that doesn't work, aplay -l may help.
>

-- 

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

#199950

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Sep 10, 2018 at 09:33:30PM +0100, Joe wrote:
> On Mon, 10 Sep 2018 16:22:38 -0400
> Greg Wooledge <wooledg@eeg.ccf.org> wrote:
> 
> > On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote:
> > > 
> > > There's no alsa-base in Stretch. 
> > > 
> > > Should there be some other way of producing sounds?  
> > 
> > If you're looking for alsamixer, it's in alsa-utils.  ALSA should just
> > work out of the box for most users who skip the Desktop Environment
> > during the installation (and therefore do not have to circumvent
> > pulse).
> > 
> > The only steps required for most people are to install alsa-utils,
> > run alsamixer, unmute the master channels, and raise the volume of the
> > master channels above zero.
> > 
> 
> Thank you for an extremely prompt reply, but I've been there and done
> that:
> 
> alsa-utils is already installed at the requested version (1.1.3-1)
> 
> alsamixer
> 
> cannot open mixer: No such file or directory

You could try to list your cards and devices with aplay -l

Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAluW2gIACgkQBcgs9XrR2kb4nQCfX7n92ERILwZehpOfSPeBCQe2
9wcAnAjGPYoWMLBpyI9uu2OjVImBxICg
=4GJO
-----END PGP SIGNATURE-----

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

#199955

On Mon, 10 Sep 2018 22:54:26 +0200
<tomas@tuxteam.de> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Mon, Sep 10, 2018 at 09:33:30PM +0100, Joe wrote:
> > On Mon, 10 Sep 2018 16:22:38 -0400
> > Greg Wooledge <wooledg@eeg.ccf.org> wrote:
> >   
> > > On Mon, Sep 10, 2018 at 09:19:09PM +0100, Joe wrote:  
> > > > 
> > > > There's no alsa-base in Stretch. 
> > > > 
> > > > Should there be some other way of producing sounds?    
> > > 
> > > If you're looking for alsamixer, it's in alsa-utils.  ALSA should
> > > just work out of the box for most users who skip the Desktop
> > > Environment during the installation (and therefore do not have to
> > > circumvent pulse).
> > > 
> > > The only steps required for most people are to install alsa-utils,
> > > run alsamixer, unmute the master channels, and raise the volume
> > > of the master channels above zero.
> > >   
> > 
> > Thank you for an extremely prompt reply, but I've been there and
> > done that:
> > 
> > alsa-utils is already installed at the requested version (1.1.3-1)
> > 
> > alsamixer
> > 
> > cannot open mixer: No such file or directory  
> 
> You could try to list your cards and devices with aplay -l
> 
>

OK, aplay -l as root sees my USB device as card 1. 

I have various sound modules loaded, including snd, soundcore and
snd_usb_audio. I assume from this that my device driver has been found.

Speaker-test is unable to find any sound cards.

-- 
Joe

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

#199965

Joe wrote:

> On Mon, 10 Sep 2018 22:54:26 +0200

> 
> OK, aplay -l as root sees my USB device as card 1.

why as root - are you in the audio group?

$ grep audio /etc/group
audio:x:29:abcdef,pulse,timidity

> 
> I have various sound modules loaded, including snd, soundcore and
> snd_usb_audio. I assume from this that my device driver has been found.
> 
> Speaker-test is unable to find any sound cards.

what is the sound card, mainboard etc.?

For example here I have intel HD based card on the board and a web cam
attached (the usb) and HDMI display link. You can ignore the midi. So good
modules loaded look like this

$ lsmod | grep snd
snd_usb_audio         184320  2
snd_usbmidi_lib        28672  1 snd_usb_audio
snd_rawmidi            32768  1 snd_usbmidi_lib
snd_seq_device         16384  1 snd_rawmidi
snd_hda_codec_hdmi     57344  1
snd_hda_codec_conexant    20480  1
snd_hda_codec_generic    77824  1 snd_hda_codec_conexant
snd_hda_intel          32768  4
snd_hda_codec         118784  4
snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep              16384  2 snd_usb_audio,snd_hda_codec
snd_hda_core           65536  5
snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_pcm               102400  5
snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
snd_timer              32768  1 snd_pcm
snd                    81920  24
snd_hda_codec_generic,snd_hda_codec_conexant,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_timer,snd_pcm,snd_rawmidi
soundcore              16384  1 snd
usbcore               221184  10
xhci_hcd,ehci_pci,snd_usb_audio,usbhid,snd_usbmidi_lib,uvcvideo,ehci_hcd,btusb,xhci_pci,uhci_hcd

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

#199969

On Tue 11 Sep 2018 at 08:23:58 +0200, deloptes wrote:

> Joe wrote:
> 
> > On Mon, 10 Sep 2018 22:54:26 +0200
> 
> > 
> > OK, aplay -l as root sees my USB device as card 1.
> 
> why as root - are you in the audio group?

Having a user in the audio group is unnecessary. ACLs on the devices are
used.

brian@desktop:~$ ls -l /dev/snd/
total 0
drwxr-xr-x  2 root root       60 Jul  9 09:45 by-path
crw-rw----+ 1 root audio 116,  2 Jul  9 09:45 controlC0
crw-rw----+ 1 root audio 116,  4 Aug 28 18:56 pcmC0D0c
crw-rw----+ 1 root audio 116,  3 Sep 10 20:45 pcmC0D0p
crw-rw----+ 1 root audio 116,  6 Jul  9 09:45 pcmC0D1c
crw-rw----+ 1 root audio 116,  5 Jul  9 09:45 pcmC0D1p
crw-rw----+ 1 root audio 116,  1 Jul 14 20:58 seq
crw-rw----+ 1 root audio 116, 33 Jul 14 20:58 timer

brian@desktop:~$ getfacl /dev/snd/timer
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/timer
# owner: root
# group: audio
user::rw-
user:brian:rw-
group::rw-
mask::rw-
other::---

-- 
Brian.

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

#199973

On Tue, 11 Sep 2018 08:23:58 +0200
deloptes <deloptes@gmail.com> wrote:

> Joe wrote:
> 
> > On Mon, 10 Sep 2018 22:54:26 +0200  
> 
> > 
> > OK, aplay -l as root sees my USB device as card 1.  
> 
> why as root - are you in the audio group?

No users in audio yet apart from the original installation user. The
ssh user doesn't need sound, which will only ever be used by www-data.

But the infrastructure should be present without anyone logged in. In
the past, I've always been able to see /proc/asound as root. It's just
not there now. /dev sees the device.

I do have a Stretch workstation, also a clean installation, but that
has on-board Intel sound and is therefore a different beast. It
certainly does have a /proc/asound.

I also plugged in another USB sound device to the server, also as it
happens a C-Media device, but a different, much older one. Exactly the
same: syslog sees it being recognised, aplay -l sees it, but
speaker-test still can't see it and no additional modules are loaded.
Still no sign of /proc/asound, which I think is the main fault symptom.

> 
> $ grep audio /etc/group
> audio:x:29:abcdef,pulse,timidity
> 
> > 
> > I have various sound modules loaded, including snd, soundcore and
> > snd_usb_audio. I assume from this that my device driver has been
> > found.
> > 
> > Speaker-test is unable to find any sound cards.  
> 
> what is the sound card, mainboard etc.?

It's a C-Media USB device, described by lsusb as a 'CM106 Like Sound
Device'. I can't see any obvious problems with this sort of thing on
the Net. The computer is a HP Proliant Microserver with AMD CPU and
graphics. It doesn't appear to have any on-board sound, and lshw
doesn't name the MB.

Again, this computer and sound device did work under Wheezy. I've been
using the device since before Wheezy, and bought it to replace the older
C-Media device. That was a very cheap VOIP device and seemed a bit
flaky, occasionally disconnecting from USB and immediately
reconnecting. Both devices produced sound OK.

Is there conceivably an issue in Stretch of having USB sound but no
on-board sound? Is that causing the boot process not to build the sound
infrastructure properly? There is a spare PCIe slot, but it's tiny, and
I'm not sure I can get a cheap card that will physically fit.

-- 
Joe

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web