linux-kernel - Re: Audio Jack Out does not work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hoamz6nd8.wl-tiwai@suse.de>
Date:	Wed, 08 Apr 2015 10:22:11 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Taylor Smock <smocktaylor@...il.com>
Cc:	Dan Carpenter <dan.carpenter@...cle.com>, perex@...ex.cz,
	david.henningsson@...onical.com, joe@...ches.com,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: Audio Jack Out does not work

At Tue, 07 Apr 2015 21:07:06 -0400,
Taylor Smock wrote:
> 
> Yes; reverting the patch does fix the problem.

What if you just adjust the new volume manually without reverting the
patch?  Run "alsamixer -c0" (or -c1, depending on the setup).  Once
after the setup, run "alsactl store" as root to save as the system
default volume.

The renamed volume should have been set in full volume as default by
the driver, and this shouldn't matter whether PA is new or old.  If
the mixer adjustment isn't kept after relogin or reboot, it means that
some user-space stuff overrides it.

In anyway, please give alsa-info.sh output before and after the
commit.

Takashi

> On Wed, 2015-04-08 at 01:56 +0300, Dan Carpenter wrote:
> > So it's 03ad6a8c93b6df2 ('ALSA: hda - Fix "PCM" name being used on > one
> > DAC when there are two DACs') which causes the problem?  Have you 
> > tried
> > to just revert that patch?
> > 
> > git show 03ad6a8c93b6df2d65c305b5b5f9474068b45bfb | patch -p1 -R
> > 
> > regards,
> > dan carpenter
> > 
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/