From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Schuster Subject: Re: ALC268 (no sound) Date: Wed, 06 Feb 2008 12:06:26 +0100 Message-ID: <47A994B2.3000306@harddisk.is-a-geek.org> References: <200802060617.m166HaYL003540@turbo.physics.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from www.velirat.de (velirat.de [85.25.68.44]) by alsa0.perex.cz (Postfix) with ESMTP id 09FCD24426 for ; Wed, 6 Feb 2008 12:05:18 +0100 (CET) In-Reply-To: <200802060617.m166HaYL003540@turbo.physics.adelaide.edu.au> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Jonathan Woithe , alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org Jonathan Woithe schrieb: >> I have uploaded the driver to >> http://rapidshare.com/files/89478591/ALC268_Compal.rar (but I left out the >> Vista stuff). Do you think it's possible to find out _what_ makes the >> problem with this? >> > > I've had a quick look at the contents and nothing jumps out at me. Others > with more experience with the windoze driver structure and knowledge of how > various files are used may have more success. > > My past experience has shown that in cases like this the best approach is to > poke at the hardware until you find something that works. Admittedly that's > becoming less feasible as time goes on and the hardware gets more complex > and the fragility of hardware increases the likelihood of permanent damage. > > Do you think that