You are not logged in.
In attempting to try different options towards getting my Mac Pro's headphone output working, I have read many, many webpages referencing modprobe.d with .conf files using different names such as "alsa-base", "alsa", "alsa_local" and "sound".
My understanding of modprobe is that it will sweep up any *.conf files in /etc/modprobe.d and attempt to interpret them. The file name does not matter, as long as it ends with .conf.
Is this correct or is there something magic about the file names "alsa-base.conf", "alsa.conf", etcetera?
Offline
Is this correct
Yes.
Jin, Jîyan, Azadî
Offline
Thanks. Some posts mention /etc/modprobe.conf but they are old and so such file exists in my system.
Can I assume that references to /etc/modprobe.conf are obsolete?
Offline
It's been deprecated for a few years. The Arch news feed is great with changes like this: https://www.archlinux.org/news/new-modu … -location/
The modprobe.d manpage and the kernel modules wiki are good sources for information on these issues as well.
"We may say most aptly, that the Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves." - Ada Lovelace
Offline
Thanks. I am subscribed to the Arch News, Recent Packages and a few Arch forum RSS feeds to at least keep with the headlines. The news archive you linked might be interesting to page through.
Offline