From: David Ford <david+powerix@blue-labs.org>
To: Norbert Wolff <norbert_wolff@t-online.de>
Cc: Andy Pfiffer <andyp@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: ALSA busted in 2.5.69
Date: Sat, 10 May 2003 19:20:33 -0400 [thread overview]
Message-ID: <3EBD8941.7070403@blue-labs.org> (raw)
In-Reply-To: <20030510080440.3446cc96.norbert_wolff@t-online.de>
Shrug :)
I use devfs, all is magic. All is [nearly always] correct.
David
Norbert Wolff wrote:
>On 09 May 2003 12:12:10 -0700
>Andy Pfiffer <andyp@osdl.org> wrote:
>
>
>
>>I'm not using devfs, and I've had no luck getting ALSA to work on my
>>i810-audio system. OSS works fine.
>>
>>Is there a step-by-step writeup available for morons like me that
>>haven't gotten ALSA working?
>>
>>
>
>Hi Andy !
>
>The Problem seems to be that ALSA has moved their devices some weeks ago.
>In the alsa-driver-0.9.3a-Package (ftp://ftp.alsa-project.org) is a script
>called snddevices (attached) which creates the needed devices and links.
>
>Execute it as root and all should be fine ...
>
>Maybe this Script should be distributed with the Kernel too ?
>
>Regards,
>
> Norbert
>
>
>
>
next prev parent reply other threads:[~2003-05-10 23:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.j6n4o02.sl813a@ifi.uio.no>
[not found] ` <fa.juutvqv.1inovpj@ifi.uio.no>
2003-05-09 18:14 ` ALSA busted in 2.5.69 walt
2003-05-09 19:12 ` Andy Pfiffer
2003-05-09 19:41 ` David van Hoose
2003-05-10 6:04 ` Norbert Wolff
2003-05-10 23:20 ` David Ford [this message]
2003-05-11 0:12 ` [RFC] devfs [was Re: ALSA busted in 2.5.69] David van Hoose
2003-05-11 0:36 ` David Ford
2003-05-11 0:14 ` ALSA busted in 2.5.69 David van Hoose
2003-05-09 19:48 Downing, Thomas
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 23:39 Torrey Hoffman
2003-05-09 8:09 ` Giuliano Pochini
2003-05-09 9:08 ` Jan Dittmer
2003-05-09 15:23 ` Torrey Hoffman
2003-05-09 19:37 ` Jose Luis Domingo Lopez
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=3EBD8941.7070403@blue-labs.org \
--to=david+powerix@blue-labs.org \
--cc=andyp@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=norbert_wolff@t-online.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.