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: <2ff216280709040718y4b8e1fa7x1f51cc68f1d18de9@mail.gmail.com>
Date:	Tue, 4 Sep 2007 19:48:23 +0530
From:	"Abhijit Bhopatkar" <bain@...slashzero.com>
To:	"Takashi Iwai" <tiwai@...e.de>
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.

On 9/4/07, Takashi Iwai <tiwai@...e.de> wrote:
> 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,

> OK, these are real problems.
>
> > I am willing to do whatever test you people want, though I do not know
> 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.

To be precise its Macbook 1st Generation non pro.  with subsystem id 0x106b0a00

Well a friend of mine has the same model and i tried things out on his machine.
to my surprise :(, the original 2.6.23-rc5 is working fine on his machine.

So on my machine we booted to windows and tested things out. The sound
on my machine doesn't work in windows either, although its working in
OSX.

So sorry for all the noise its most likely a hardware problem after all.
Although i am baffled as to why old pin config works on this
particular broken hardware.

I hope i didn't bug you too much, i appreciate your quick responses.
Abhijit
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ