Capture controls in Alsamixer locked to zero

Off-Topic discussions about science, technology, and non Debian specific topics.
Post Reply
Message
Author
kjellinux
Posts: 23
Joined: 2024-08-18 02:32

Capture controls in Alsamixer locked to zero

#1 Post by kjellinux »

I have an IBM ThinkPad 600X on which I have installed Debian based antiX 23.1. Initially, the system could not find any driver for the audio device.

Code: Select all

Audio:
  Device-1: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio
    Accelerator] vendor: IBM ThinkPad 600X/A20m driver: N/A bus-ID: 00:06.0
    chip-ID: 1013:6003 class-ID: 0401
  API: ALSA v: k5.10.197-antix.1-486-smp status: kernel-api with: apulse
    type: pulse-emulator
  Server-1: PipeWire v: 1.2.1 status: off with: 1: pipewire-pulse
    status: off 2: wireplumber status: off 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
After following the instructions for Debian 8 "Jessie" in the Debian Wiki for snd-cs46xx, I now have an snd-cs46xx driver.

Code: Select all

Audio:
  Device-1: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio
    Accelerator] vendor: IBM ThinkPad 600X/A20m driver: snd_cs46xx v: kernel
    bus-ID: 00:06.0 chip-ID: 1013:6003 class-ID: 0401
  API: ALSA v: k4.19.276-antix.2-486-smp status: kernel-api with: apulse
    type: pulse-emulator
  Server-1: PipeWire v: 1.0.3 status: off with: 1: pipewire-pulse
    status: off 2: wireplumber status: off 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
All should be well, but for some reason the Capture controls for Line, CD, Mic, Video, Phone and Aux are locked to zero and will not change no matter what I do. If I try to open Alsamixer from the terminal with

Code: Select all

alsamixer
I get an error message saying "Host computer is down". After advice from a member of the antiX forum, I managed to open the Alsamixer using

Code: Select all

alsamixer -c 0
In Alsamixer All controls can be toggled and adjusted except for the Capture controls mentioned above. They are locked to zero and will not change no matter what I try to do. After advice from several experienced members of the forum I also tried swithcing from a 5.10 kernel to a 4.19 kernel, but that did not help.

Now I'm hoping that someone here in the Debian User Forums can point me in the right direction so that I can find out what's causing the Capture controls to lock to zero, and how to unlock them.

User avatar
sunrat
Site admin
Site admin
Posts: 7365
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 133 times
Been thanked: 649 times

Re: Capture controls in Alsamixer locked to zero

#2 Post by sunrat »

Debian derivative issues such as for antiX are handled in our Off-Topic subforum as they are not pure Debian. Topic moved.

I didn't think antiX used Pipewire by default. Maybe you should return it to its original audio status which is Pulseaudio IIRC. Using it with apulse may be messing it up completely. Also this looks wrong:

Code: Select all

1: pipewire-pulse status: off 2: wireplumber status: off
antiX also doesn't use systemd so it would make for another major difference for which we average Debian users may not be able to help.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

kjellinux
Posts: 23
Joined: 2024-08-18 02:32

Re: Capture controls in Alsamixer locked to zero

#3 Post by kjellinux »

sunrat wrote: 2024-08-18 03:55 ... we average Debian users may not be able to help.
@sunrat you already helped. I now have several leads to follow.

kjellinux
Posts: 23
Joined: 2024-08-18 02:32

Re: Capture controls in Alsamixer locked to zero [solved]

#4 Post by kjellinux »

After extensive testing and trial and error, it turned out only two things were needed to get the sound working. First, the driver needed to be fixed, as described above. Second, PipeWire needed to be turned on. After these two were done, the sound worked without any problems.

Post Reply