D. R. Evans wrote on 2/18/20 10:21 AM:
> I recently bought a system with a Supermicro MBD-X11SAT-F-O motherboard, which
> includes audio. Previously, this system ran Windows; it is now running debian
> stable (buster).
> Unfortunately, the audio seems to have very low output.
> I have fiddled with all the high-level controls available through alsamixer to
> no avail. (Also PulseAudio, although I think -- to the extent that I
> understand how this all is supposed to work -- that that runs on top of ALSA,
> so if ALSA is providing low audio, PulseAudio won't help.)
> So I'm thinking that there must be an issue with the driver that debian has
> decided to install and use.
> This is a new area for me, and I have no idea how to determine the driver in
> use, or how to change it.
> For what it's worth, "aplay -l" says:
> ----
> card 0: PCH [HDA Intel PCH], device 0: ALC888-VD Analog [ALC888-VD Analog]
>   Subdevices: 0/1
>   Subdevice #0: subdevice #0
> ----
> Guidance would be very much appreciated.

Perhaps this information is also helpful, output from hwinfo --sound:

22: PCI 1f.3: 0403 Audio device
  [Created at pci.386]
  Unique ID: nS1_.f6gxEbd5XS0
  SysFS ID: /devices/pci0000:00/0000:00:1f.3
  SysFS BusID: 0000:00:1f.3
  Hardware Class: sound
  Model: "Intel 100 Series/C230 Series Chipset Family HD Audio Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0xa170 "100 Series/C230 Series Chipset Family HD Audio Controller"
  SubVendor: pci 0x15d9 "Super Micro Computer Inc"
  SubDevice: pci 0x0907
  Revision: 0x31
  Driver: "snd_hda_intel"
  Driver Modules: "snd_hda_intel"
  Memory Range: 0xdf340000-0xdf343fff (rw,non-prefetchable)
  Memory Range: 0xdf320000-0xdf32ffff (rw,non-prefetchable)
  IRQ: 140 (26681 events)
  Module Alias: "pci:v00008086d0000A170sv000015D9sd00000907bc04sc03i00"
  Driver Info #0:
    Driver Status: snd_hda_intel is active
    Driver Activation Cmd: "modprobe snd_hda_intel"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

As before, any guidance would be greatly appreciated. I'm stuck.


PS I see that what sounds like this issue was raised 11 years ago, as part of
At which point it sounds like it was an ALSA issue. But surely after all this
time the problem has been fixed?

PPS If this isn't the correct place to be asking about this issue, could some
kind person please direct me to somewhere more appropriate?

Web:  http://enginehousebooks.com/drevans

Attachment: signature.asc
Description: OpenPGP digital signature

Alsa-user mailing list

Reply via email to