From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: "/proc/asound/dev" gone in 2.5.75
Date: Fri, 11 Jul 2003 14:59:10 +0200 [thread overview]
Message-ID: <yw1xof016wyp.fsf@users.sourceforge.net> (raw)
In-Reply-To: Pine.GSO.4.53.0307111450440.29900@pitsa.pld.ttu.ee
Siim Vahtre <siim@pld.ttu.ee> writes:
> I just went from 2.5.70 to 2.5.75 and discovered that sound no longer
> works. After short period of investigation, I found that "/dev/snd" is
> pointing to "/proc/asound/dev" that now, for some unknown reason, is gone.
>
> 'dmesg' shows
>> ALSA device list:
>> #0: Intel 82801BA-ICH2 at 0xe800, irq 9
>
> And '/proc/asound' seems to be there, aswell.
>> siim@void:/proc/asound$ ls
>> I82801BAICH2@ card0/ cards devices oss/ pcm timers version
>
> But no 'dev' there. I am also missing those control0* stuff. Strange...
>
> Can anyone please tell me what I'm doing wrong?
The /proc/asound/dev directory has been removed. Either switch to
devfs (IMHO a good thing), or run some script to create the proper
device files (it's in the ALSA distribution).
--
Måns Rullgård
mru@users.sf.net
prev parent reply other threads:[~2003-07-11 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 11:58 "/proc/asound/dev" gone in 2.5.75 Siim Vahtre
2003-07-11 12:59 ` Måns Rullgård [this message]
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=yw1xof016wyp.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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