On Thursday 23 April 2009 02.17.10 Jacob Meuser wrote: > On Wed, Apr 22, 2009 at 09:22:56PM +0000, Jacob Meuser wrote: > > On Wed, Apr 22, 2009 at 01:41:59PM +0200, LEVAI Daniel wrote: [...] > > > > might work better if you remove beep sources. I mean: > > > > $ mixerctl inputs.mix2_source=dac,sel4,sel6,cd > > bleh. that won't work on this particular mixer. > > and the intel docs say, "When the beep generator is actively generating > a tone, its output drives all Pin Widgets which are currently defined > output pins in a method of the vendor's choice, either by switching the > pin to the beep signal or by mixing the tone into the currently playing > stream. This node is never listed on any other node's connection list. > The actual vendor-defined connection only persists while the Beep > Generator is actively generating a tone. This widget may contain an > optional amplifier." > > the beep generator is what you are seeing as "beep". notice that this > codec (AD1981HD) violates the standard by listing the beep generator > in another node's connection list (inputs.sel2_source=beep). and it > appears that there's no control over the beep through azalia. > > the intel docs continue, "This Beep Generator feature is independent of > any optional "PC Beep Pin" or "Analog Beep Pin" input which is intended > to receive and externally generated tone or sound. The presence of > such a beep input is not exposed to software, nor defined in this > specification. If used, this type of beep input would be connected > through the codec to output pins in a vendor defined way, but such a > connection may be maintained only while the Link reset (RST#) is > asserted." > > interestingly, the codec's datasheet lists a "PC BEEP IN" at nid 16, > but the codec tells us nid 16 is: > > azalia0: black16 wcap=400000 > cap=20<INPUT> > [15/00] color=black device=other conn=none conntype=atapi > location=spec2 chassis=internal special=atapi > > I guess that follows the spec, which says "The presence of such a beep > input is not exposed to software" :/ this is common though. on several > realtek codecs, the beep input is similarly obscured, but they are > controllable like any other input. remember, the behaviour is "vendor > defined". but anyway, there is again apparently no way for you to turn > this off through azalia because, well, it is turned off through azalia > but you still hear it. > > so I guess you just have to use wsconsctl.
Alright, thank you for the great support and the explanation. I was happy to help testing this with azalia, and it is totally ok and working with wsconsctl. Daniel -- LIVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
