From owner-freebsd-multimedia@FreeBSD.ORG Sun Sep 28 09:12:49 2008 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F7381065688; Sun, 28 Sep 2008 09:12:49 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 791BF8FC08; Sun, 28 Sep 2008 09:12:47 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.1.14) with ESMTPSA id 222623573; Sun, 28 Sep 2008 12:12:47 +0300 Message-ID: <48DF589D.1010700@FreeBSD.org> Date: Sun, 28 Sep 2008 13:12:45 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.16 (X11/20080726) MIME-Version: 1.0 To: Ian FREISLICH References: <48DF32B2.7080407@FreeBSD.org> <48CBF399.9080801@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-multimedia@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: New snd_hda driver came in. X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2008 09:12:49 -0000 Ian FREISLICH wrote: > Alexander Motin wrote: >> Ian FREISLICH wrote: >>> I just noticed that my speakers still play (very softly) when my >>> headphone jack is inserted. >> May be your codec has no muter on speaker pin and driver uses it's >> volume control instead. > > It used to work. As I can see, Speaker pin has neither muter nor volume control. In such case driver usually tries to disable pin OUT control to silent it. Previous driver does it same way, because of quirks. New driver should do it automatically, but it doesn't because of broken codec configuration (see below). Did I understand right that on headphone connection speaker volume is decreasing? May be hardware itself just disables power amplifier on jack connection, but it does not disconnects it completely, neither the driver does. >>> Also, when playing back, the optical port is activated. >> Is it good or bad? :) I have no optical ports, but my copper one seems >> to be enabled only when data stream present there. At least by receiver >> displays so. > > Neither good nor bad. Also, the built in mic has never worked, but > it looks promising from this boot message. Your BIOS writes completely broken configuration into the codec. You should update it or use device hints to fix the situation. >>> My hardware is a MacBook Pro. Let me know what to do to extract >>> the information you need to debug this. >> Verbose kernel boot messages would be good. > > hdac0: 3 associations found: > hdac0: Association 0 (1) in: > hdac0: Pin nid=11 seq=2 mic alone, no problem, let it be. > hdac0: Association 1 (2) out: > hdac0: Pin nid=12 seq=1 Speaker, fine. > hdac0: Pin nid=10 seq=2 Line-out. It pretend to work as rear channel pair. If it should work as headphones with speaker auto mute it should have "Speaker" device type and seq=15. > hdac0: Pin nid=16 seq=3 SPDIF-out. It pretend to work as center/sub channels. That's why it activates when you playing audio. I would recommend you do move it to separate association to use it properly. > hdac0: Association 2 (3) in: > hdac0: Pin nid=15 seq=1 Line-in. Strange that it is placed to the same association as SPDIF-in. UAA specification strictly denies it! I would move it to as=1, it will fix both. > hdac0: Pin nid=17 seq=2 SPDIF-in. Driver unable to use it now as it can;t be routed to the same DAC with Line-in. > hdac0: Tracing association 0 (1) > hdac0: Pin 11 traced to ADC 6 > hdac0: Association 0 (1) trace succeded > hdac0: Tracing association 1 (2) > hdac0: Pin 12 traced to DAC 3 > hdac0: Pin 10 traced to DAC 2 > hdac0: Pin 16 traced to DAC 8 > hdac0: Association 1 (2) trace succeded > hdac0: Tracing association 2 (3) > hdac0: Pin 15 traced to ADC 7 > hdac0: Unable to trace pin 17 to ADC 7, undo traces > hdac0: Unable to trace pin 15 to ADC 9, undo traces > hdac0: Association 2 (3) trace failed Here you can see how driver processed this situation. -- Alexander Motin