mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Pavel Machek <pavel@suse.cz>,
	Nishanth Aravamudan <nacc@us.ibm.com>,
	Nick Warne <nick@linicks.net>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	tiwai@suse.de, ghrt@dial.kappa.ro, perex@suse.cz,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: No sound from SB live!
Date: Sun, 19 Feb 2006 23:23:08 +0000	[thread overview]
Message-ID: <200602192323.08169.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <1140385837.2733.394.camel@mindpipe>

On Sunday 19 February 2006 21:50, Lee Revell wrote:
> On Sun, 2006-02-19 at 22:47 +0100, Pavel Machek wrote:
> > On Ne 19-02-06 16:30:37, Lee Revell wrote:
> > > On Sun, 2006-02-19 at 12:51 -0800, Nishanth Aravamudan wrote:
> > > > I run Ubuntu Breezy, which has:
> > > >
> > > > alsa-utils = 1.0.9a-4ubuntu5
> > >
> > > The alsa-utils version should not matter, it's alsa-lib that must be
> > > kept in sync with the ALSA version in the kernel.
> >
> > Ugh, not a good news.
>
> This has been the case for ages (distros still get it wrong).  It is not
> an ideal situation.
>
> >  How do I tell if my alsa libs are recent enough?
>
> 1.0.10 should be OK

I'm still using 1.0.9 on 2.6.16-rc4 with no problems, Audigy 2 (one that uses 
emu10k1).

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2006-02-19 23:23 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18 23:14 Pavel Machek
2006-02-18 23:27 ` ghrt
2006-02-18 23:48   ` Pavel Machek
2006-02-19  0:33     ` Richard Mittendorfer
2006-02-19 21:42       ` Pavel Machek
2006-02-19 22:07         ` Richard Mittendorfer
2006-02-19  0:58     ` Lee Revell
2006-02-19 21:44       ` Pavel Machek
2006-02-20  0:33         ` Lee Revell
2006-02-20  0:39           ` Pavel Machek
2006-02-20  1:33             ` Alistair John Strachan
2006-02-20 23:55               ` Pavel Machek
2006-02-19 11:04 ` Jesper Juhl
2006-02-19 11:18   ` Nick Warne
2006-02-19 19:29     ` Lee Revell
2006-02-19 20:20       ` Nick Warne
2006-02-19 20:31         ` Lee Revell
2006-02-20 19:18           ` Nick Warne
2006-02-20 19:31             ` D. Hazelton
2006-02-19 20:33         ` Lee Revell
2006-02-19 20:51     ` Nishanth Aravamudan
2006-02-19 21:30       ` Lee Revell
2006-02-19 21:47         ` Pavel Machek
2006-02-19 21:50           ` Lee Revell
2006-02-19 23:23             ` Alistair John Strachan [this message]
2006-02-19 23:32               ` Lee Revell
2006-02-19 23:46                 ` Pavel Machek
2006-02-19 23:53                   ` Lee Revell
2006-02-20  0:04                     ` Nishanth Aravamudan
2006-02-20  0:11                       ` Lee Revell
2006-02-20  0:57                         ` Nishanth Aravamudan
2006-02-20  0:26                     ` Pavel Machek
2006-02-20  0:30                       ` Lee Revell
2006-02-20  0:42                         ` Pavel Machek
2006-02-20  0:52                           ` Lee Revell
2006-02-19 23:56                 ` Alistair John Strachan
2006-02-20  0:05                   ` Lee Revell
2006-02-20  0:12                     ` David Lang
2006-02-20  0:16                       ` Alistair John Strachan
2006-02-20  0:17                       ` Lee Revell
2006-02-19 21:49         ` Pavel Machek
2006-02-19 21:54           ` Lee Revell
2006-02-19 22:25             ` Pavel Machek
2006-02-19 22:28               ` Lee Revell
2006-02-19 23:04                 ` Lee Revell
2006-02-20 11:15               ` Takashi Iwai
2006-02-20 11:41                 ` Pavel Machek
2006-02-20 19:50                   ` Vojtech Pavlik
2006-02-20 19:52                     ` Pavel Machek
2006-02-19 19:19   ` Pavel Machek
2006-02-22 14:05     ` Takashi Iwai

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=200602192323.08169.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=ghrt@dial.kappa.ro \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nacc@us.ibm.com \
    --cc=nick@linicks.net \
    --cc=pavel@suse.cz \
    --cc=perex@suse.cz \
    --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

all inboxes | Powered by JetHome®