Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Barry Scott <barry.scott@onelan.co.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: ALC260 no sound output on Kernel 2.6.17.1
Date: Fri, 14 Jul 2006 10:35:32 +0100	[thread overview]
Message-ID: <44B76564.8000703@onelan.co.uk> (raw)
In-Reply-To: <1152831906.2961.0.camel@mindpipe>

Lee Revell wrote:
> On Fri, 2006-06-23 at 16:30 +0100, Barry Scott wrote:
>   
>>> This should have been fixed in 1.0.12rc1.
>>>   
>>>       
>> Its the user land code that has the bug not the kernel drivers then? 
>>     
>
> Have you tried the ALSA 1.0.12rc1 kernel drivers yet?
>
> Lee
>   
Yes it works. Something in the ALSA 1.0.12rc1 fixes it. I updated drivers,
lib and utils.

I was waiting for a reply to my messages asking which package I needed to
install. When no further info was forthcoming I explored all the kits.

I was surprised to see 2.6 drivers in the drivers package. All the previous
drivers packages tell me the drivers are shipped with linux kernel. Luck
I checked.

Barry



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-07-14  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 13:11 ALC260 no sound output on Kernel 2.6.17.1 Barry Scott
2006-06-23 14:14 ` Takashi Iwai
2006-06-23 15:30   ` Barry Scott
2006-07-13 23:05     ` Lee Revell
2006-07-14  9:35       ` Barry Scott [this message]
2006-06-27 11:52 ` Barry Scott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44B76564.8000703@onelan.co.uk \
    --to=barry.scott@onelan.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=rlrevell@joe-job.com \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox