[ubuntu-studio-users] Default sound settings

VE4PER Andy ve4per at hotmail.com
Thu Nov 3 16:05:50 UTC 2016


not surprising this is one of the three most aggravating things about 
the *nix universe I find. Something works out great and you get it all 
playing nice together and then along comes an update and the printer 
quits working or the sound quits or the flash player plugins quit 
working and you are back to square one again troubleshooting for a fix 
to one or all of these items every time an update comes out.

sad but true and it seems to happen with all flavors of *nix mint, 
ubuntu studio , ubuntu desktop K and X. They all seem to be affected by 
the widespread malady.


On 2016-11-03 10:49 AM, David Sumbler wrote:
> Thanks for the suggestion.  Unfortunately adding
> 'options snd slots=snd_hda_intel' (as it would be in my case) to
> /etc/modprobe.d/alsa-base.conf has not made any difference, even after
> rebooting the computer.
>
> David
>
>
> On Thu, 2016-11-03 at 14:48 +0100, Ralf Mardorf wrote:
>> Hi,
>>
>> get the driver name of that device by lshw like this
>>
>> ubuntu-mate at ubuntu-mate:~$ sudo lshw -C sound | grep driver
>>    configuration: driver=snd_hdspm latency=0
>>    configuration: driver=snd-usb-audio maxpower=100mA speed=12Mbit/s
>>
>> On my machine the wanted sound card's driver is snd_hdspm.
>>
>> Then generate a file, resp. add to an existing file, that ensures
>> that
>> the wanted sound card always is hw:0 after startup. The below
>> commands
>> first tries to make a copy, assuming /etc/modprobe.d/alsa-base.conf
>> should already exist.
>>
>> ubuntu-mate at ubuntu-mate:~$ sudo -i
>> root at ubuntu-mate:~# cp -ai /etc/modprobe.d/alsa-base.conf /root/alsa-
>> base.conf.backup
>> root at ubuntu-mate:~# echo "options snd slots=snd_hdspm" >>
>> /etc/modprobe.d/alsa-base.conf
>>
>> Just replace snd_hdspm with your driver. On my machine this does
>> cause
>> that the device that belongs to the driver snd_hdspm is always hw:0
>> and
>> the other device becomes hw:1.
>>
>> This might solve your issue, if not you simply could delete the file
>> or
>> replace a file that already existed with the backup.
>>
>> Regards,
>> Ralf
>>
>>
>>



More information about the ubuntu-studio-users mailing list