On 10/04/2015 08:57 PM, ansible wrote:
So this alsa-base.conf has the effect of making only
the onboard audio
available instead of reordering. I most likely have the 'sunxicodec' name
wrong for the onboard audio, I'm just guessing at that, and have no idea
what the driver name for that is, if there even is one. I'm kind of
suspecting the audio device is part of a monolithic driver for the whole
system-on-chip, is that possible?
The audio codec drivers seem to be built-in and not dynamically loadable
for your kernel. So any settings in /etc/modprobe won't have any effect.
Which kernel are you using? What is the output of uname -a?
Jeremy