You are not logged in.
Pages: 1
Hello everyone,
it's been quite some time since I've last run Arch as my desktop OS at work, but to cut a long story short, let's just say, I migrated back to arch from OSX.
Now I have this rather beefy Mac Pro here at the office, and I've installed Arch on it.
Everything I care about on my work machine runs as intended but there is one last thing I can't get to work: The front audio jack.
This thing has two audio devices, but one is only for HDMI sound:
05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series]
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio ControllerThe audio device (analog outputs) is working, I've got my headphones connected at the back now...
Anyone have any ideas? How do I switch to the front jack (automatically or manually, I don't really care...)
Offline
I am hunting for an answer to this as well, almost 2 years later. There are lots of voodoo answers out there, mostly for Mac Books, but I haven't found anything definitive. Very sad that this problem can be outstanding for years with no one being able to fix it.
I have this 2009 Mac Pro model
I believe that part of the problem is that Apple does things in their own "special" way and the hardware does not behave as drivers expect it to.
This Linux Mint thread from 2011 and this Ubuntu thread from 2010 and this 2008 post report that Mac Book users can get the headphone jack working by using gnome-alsa-mixer to enable the otherwise muted headphone jack. It did not work on my Mac Pro and I don't know why gnome-alsamixer would be any better at this than other alsamixer tools.
There are suggestions in the Ubuntu forums that editing /etc/modprobe.d/alsa-base.conf with appropriate magic words will make the headphone jack work on some Macs. None of the suggestions have worked for me.
This 2012 post suggests that some pin ctl values are wrong
I'll try to keep this thread updated with any new news I learn.
Offline
This post from David Henningsson mentions the hdajackretask tool, which is a part of alsa-tools, for changing the "task" of different audio outputs. I have done some simple experiments with it but have not come up with a winning solution to make the Mac Pro headphone jack work. Maybe other people can also try experimenting. There are obviously too many combinations for one person to try them all.
Offline
I need a sanity check here to confirm that I'm not chasing ghosts with trying different options in /etc/modprobe.d/alsa-base.conf
This old page on Ubuntu.com points to this page on linux.no with a list of possible chip types and magic "options ... model= ..." words to apply. However, the list is old, from Linux 3.2.19.
Viewing the 3.19.1 list, it appears many of the entries for the ACL889 are gone. The closest is a generic "ACL88x" and that section does not list any of the previous option entries for Mac models such as "macpro".
Did these ACL889 configurations truly get dropped between 3.2.19 and now? Is there any point in trying them in present day?
Offline
For people who are following this thread, here is the ALSA output for my Mac Pro. I cannot (yet) interpret it.
I think I have dermined that the internal speaker is being incorrectly doubled as a mic. Clearly, the audio ports of the Mac Pro are not being recognized correctly. Using Windows 7 on the same machine, the Realtek driver controls everything properly, so this is not a case of Apple obsucating the hardware in a way only OS X can understand.
Offline
Does anyone have suggestions on how to investigate this issue further? I have gone so far as to exchange a few e-mail with David Henningsson, but he has many things on the go.
I'm very surprised that a 2009 computer with the very common ACL889 codec does not have a working headphone jack in Linux when both OS X (obviously) and Windows 7 control it fine.
I'm not even sure if the old "options ... model= ..." magic incantations posted to forums in years past are even relelvant in 3.2.19.
Offline
Just updating this activity log for future readers. Problem still exists in kernel 4.
Offline
I have contacted that alsa-devel forum with this problem and received the following suggestion. However, I can't interpret the instructions. Can anyone understand this?
Use hdajacksensetest -a to verify line out support jack detect
clear MISC = NO_PRESENCE bit 8 of pin default of Line out by hdajackretask
Pin Default 0x01010050: [Jack] Line Out at Ext Rear
Conn = 1/8, Color = Unknown
DefAssociation = 0x5, Sequence = 0x0Offline
Pages: 1