linux-kernel - Re: [PATCH] [ALSA] Added new pin config for first gen macbook.

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]

Date:	Tue, 04 Sep 2007 14:56:21 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	"Abhijit Bhopatkar" <bain@...slashzero.com>
Cc:	"Ivan N. Zlatev" <contact@...z.net>,
	"Jaroslav Kysela" <perex@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [ALSA] Added new pin config for first gen macbook.

At Tue, 4 Sep 2007 09:12:32 +0530,
Abhijit Bhopatkar wrote:
> 
> On 9/3/07, Ivan N. Zlatev <contact@...z.net> wrote:
> > On 9/3/07, Ivan N. Zlatev <contact@...z.net> wrote:
> > > On 9/3/07, Takashi Iwai <tiwai@...e.de> wrote:
> > > > At Mon, 3 Sep 2007 15:55:18 +0530,
> > > > Abhijit Bhopatkar wrote:
> > > > >
> > > > > commit 5d5d3bc3eddf2ad97b2cb090b92580e7fed6cee1 changed all
> > > > > pin configs for intel macs, but it breaks sound on
> > > > > Macbook first
> > > >
> > > > Please elaborate how does it break.  "it breaks sound" is too
> > > > ambigious like the most popular bug reports "sound doesn't work" :)
> 
> Apologies for the terse report,
> 
> On my macbook with latest kernels
> 
> 1. Alsamixer is showing only three controlls in total,
>     Master PCM and Digital.
> 2. There is absolutely no output sound what so ever.
> 3. There is no capture sound being captured either.

OK, these are real problems.

> Reverting back the pin config to the one in previous kernels is
> working (although not perfect e.g. to enable input sound we need to
> toggle the capture device to mic and linein atlease once, no idea
> whats the deal with that)
> 
> I am willing to do whatever test you people want, though I do not know
> where to look for more info at this point. So please feel free direct
> me to arrive at a better soultion or better info.

Just to be sure, doesn't none of intel-mac-[1-5] model match with your
machine?  If so, putting the pin-config back is the straightforward
solution indeed.

Anyway, it'd be helpful if someone else can check the same MacBook
(1st generation, not Pro?) whether the problem is reproducible.


thanks,

Takashi
-
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/