From: Lee Revell <rlrevell@joe-job.com>
To: abrahams@acm.org
Cc: alsa-devel@alsa-project.org, Peter Zubaj <pzubaj@gaya.sk>
Subject: Re: PROBLEM: Probable kernel bug in VT8233 drivers
Date: Thu, 04 Jan 2007 19:13:39 -0500 [thread overview]
Message-ID: <1167956020.11404.31.camel@mindpipe> (raw)
In-Reply-To: <200701041823.48794.abrahams@acm.org>
On Thu, 2007-01-04 at 18:23 -0500, Paul Abrahams wrote:
> On Thursday 04 January 2007 4:06 pm, Peter Zubaj wrote:
> > If card is in /proc/asound/cards then driver is loaded and working.
> > Probably Yast will fail to load driver again, because it is already
> > loaded.
> >
> > You have probably problem with dev files. Check if there are dev files
> > in /dev/snd subdir (I think this is default).
> >
> > Something like this:
> > crw------- 1 peter root 116, 13 Jan 4 17:03 controlC0
> > crw------- 1 peter root 116, 20 Jan 4 17:03 controlC1
>
> This is getting interesting. I do not have a /dev/snd directory. I tried
> reinstalling the devs rpm package, and that recreated /dev/snd, but after a
> reboot /dev/snd was gone again.
This is a bug in your distro. udev is supposed to create those files.
Lee
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-01-05 0:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 18:32 PROBLEM: Probable kernel bug in VT8233 drivers Paul Abrahams
2007-01-04 18:52 ` Peter Zubaj
2007-01-04 19:21 ` Paul Abrahams
2007-01-04 20:16 ` Peter Zubaj
2007-01-04 20:51 ` Paul Abrahams
2007-01-04 21:06 ` Peter Zubaj
2007-01-04 23:23 ` Paul Abrahams
2007-01-05 0:13 ` Lee Revell [this message]
2007-01-05 0:42 ` Paul Abrahams
2007-01-07 3:24 ` Paul Abrahams
2007-01-08 11:25 ` 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=1167956020.11404.31.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=abrahams@acm.org \
--cc=alsa-devel@alsa-project.org \
--cc=pzubaj@gaya.sk \
/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