On Mon, 10 Sep 2018 23:26:56 +0200 arne <sp113...@telfort.nl> wrote: > On Mon, 10 Sep 2018 22:49:34 +0200 > deloptes <delop...@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