From: Andy Pfiffer <andyp@osdl.org>
To: walt <wa1ter@hotmail.com>
Cc: Torrey Hoffman <thoffman@arnor.net>,
Giuliano Pochini <pochini@shiny.it>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ALSA busted in 2.5.69
Date: 09 May 2003 12:12:10 -0700 [thread overview]
Message-ID: <1052507530.15922.37.camel@andyp.pdx.osdl.net> (raw)
In-Reply-To: <3EBBF00D.8040108@hotmail.com>
On Fri, 2003-05-09 at 11:14, walt wrote:
> Torrey Hoffman wrote:
> > On Fri, 2003-05-09 at 01:09, Giuliano Pochini wrote:
> >
> >>On 08-May-2003 Torrey Hoffman wrote:
> >>
> >>>ALSA isn't working for me in 2.5.69. It appears to be because
> >>>/proc/asound/dev is missing the control devices.
> > ...
> >>If you are not using devfs, you need to create the devices. There is a
> >>script in the ALSA-driver package to do that. Otherwise I can't help
> >>you because I never tried devfs and linux 2.5.x.
> >
> > No. /dev/snd is a symbolic link to /proc/asound/dev,
> > and that symbolic link was created by the script you mention.
> > (I am not using devfs.)
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?
Thanks,
Andy
next prev parent reply other threads:[~2003-05-09 19:02 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 [this message]
2003-05-09 19:41 ` David van Hoose
2003-05-10 6:04 ` Norbert Wolff
2003-05-10 23:20 ` David Ford
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=1052507530.15922.37.camel@andyp.pdx.osdl.net \
--to=andyp@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pochini@shiny.it \
--cc=thoffman@arnor.net \
--cc=wa1ter@hotmail.com \
/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;
as well as URLs for NNTP newsgroup(s).