Re: Sound problems
Felix Miata wrote:
> deloptes composed on 2016-03-17 0:05 (UTC+0100):
>> Felix Miata wrote:
>> Hi your post is interesting for me.
>> on the debian one it is /etc/modprobe.d/ - no?
> I screwed up, fingers badly out of sync with eyeballs. :-p modprobe.d/ it
>> I have similar chip if not same
>> 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller
>> (rev 0b) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio
>> Controller (rev 04)
>> so there I put sound.conf in /etc/modprobe.d/ and it has
>> ## ALSA portion
>> alias char-major-116 snd
>> alias snd-card-0 snd-hda-intel
>> alias snd-card-1 snd-usb-audio
>> ## module options should go here
>> options snd-hda-intel index=0 model=ref enable_msi=1 enable=0,1
>> options snd-usb-audio index=1
>> which means HDMI is disabled (enable=0,1)
>> But according your proposal it should be possible to invert the order of
>> how it is initialized - correct?
> I probably would never have figured out on my own to swap 0 and 1.
> is where it came from. Follow-up to that bug comment begins here:
When I setup the machine I use I read a lot about the issue - the only
proposed work around was to enable/disable.
I played with alsa years ago to understand how it works, but last time I
checked the kernel driver docs I did not find this option. Anyway it is
worth trying. I just do not understand how this indexing works in the
different contexts, but I'll figure out.
>> Now for the setup above perhaps I should change to
>> options snd-hda-intel index=1,0 model=ref enable_msi=1
>> options snd-usb-audio index=2
>> What do you think Mr Miata?
> Sound config makes me crazy, sometimes just working, other times
> impossible to make work, and occasionally working via minimal effort. I
> would have to try your proposal to begin to know what to think. As the
> machine it applies to is this one rather than one of my many test
> installations, and I have no current sound system complaints, I won't be
> disturbing the sleeping dog.
As far as you have good driver it always works. I found out the key is to
tell the machine which is your audio card and which model it has.
Why being so frustrated?
The problem I guess is the variety of audio chips out there, some of which
are really cheep (and bad).
I always check the kernel driver doc - but this also changed recently and
got more confusing (at least the intel part)
I am not afraid of the "sleeping dog" - we are friends.
>> Why should it be related to TDE? I do not think your statement is
>> rectified here. However I did not test anything else.
> I only mentioned TDE because I know Lisi uses it.
Yes, but you are on a public list and your comment is of no favor to TDE,
neither it is related to TDE in any way.