You are not logged in.
- Topics: Active | Unanswered
#1 2015-10-02 17:54:45
- AnalogKid
- Member
- Registered: 2015-03-05
- Posts: 45
modprobe.d model=... still relevant?
Regarding .conf files in /etc/modprobe.d
Is passing model= ... still relevant?
Example: options snd-hda-intel model=6stack-dig
Some forum pages suggest model=... codes for solving audio problems, others suggest that these are no longer used and are a waste of time.
Before I go through a dozen magic codes and rebooting 100 times looking for a working fix I want to ensure it's not a total time waste.
Offline
#2 2015-10-02 21:24:53
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 14,840
Re: modprobe.d model=... still relevant?
Figure out the audio chipset your system uses. (don't know how to find that info, sorry)
install linux-docs , then goto /usr/lib/modules/4.2.2-1-ARCH/build/Documentation/sound/alsa
Open HD-Audio-Models.txt , look for your chipset and which models it has.
the 6stack-digout model for example is only valid for an ALC880 chipset that has 6 jacks plugs and a SPDIF output .
usually alsa nowadays selects the correct model by itself.
Last edited by Lone_Wolf (2015-10-02 21:25:27)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#3 2015-10-02 21:31:08
- AnalogKid
- Member
- Registered: 2015-03-05
- Posts: 45
Re: modprobe.d model=... still relevant?
That part is easy. It's an ALC889a.
Getting the headphone jack to work? Landing a man on Mars is easier.
Offline
#4 2015-10-04 00:15:11
- AnalogKid
- Member
- Registered: 2015-03-05
- Posts: 45
Re: modprobe.d model=... still relevant?
Can anyone confirm yes or no if using "model = ..." in a .conf file is still acted on or is it ignored and obsolete?
I don't want to waste my time trying a dozen model types if ALSA ignores it.
Offline
#5 2015-10-04 01:22:25
- WorMzy
- Administrator
- From: Scotland
- Registered: 2010-06-16
- Posts: 13,361
- Website
Re: modprobe.d model=... still relevant?
Never come across it myself, but according to the documentation, model= is still used. I don't want to waste my time checking whether this works in a .conf file though, so I'll let you test this out for yourself.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
#6 2015-10-04 02:11:46
- AnalogKid
- Member
- Registered: 2015-03-05
- Posts: 45
Re: modprobe.d model=... still relevant?
I've seen similar lists of "models" around the Internet but none appears to be comprehensive. Computer models are included in one list and missing from another. Documentation is often years out-of-date. Troubleshooting suggestions posted on one forum are dis-credited on another. The state of ALSA appears to remain quite a hack.
None of the direct-match models have been successful on my computer, nor have any of the "worked for me" suggestions posted to forums. The forum posts are often years old, thus my questioning whether model= is still current.
Offline
#7 2015-10-04 12:56:55
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 14,840
Re: modprobe.d model=... still relevant?
AnalogKid, that's why i pointed you to a file in kernel documentation.
If kernel documentation is not enough, the alsa devs and/ orkernel module snd-hda-intel maintainers are likely the only ones that can answer your question.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline