[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: udev and sound the right way? kernel 2.6.10



According to Ron Johnson,
> On Fri, 2005-03-25 at 12:48 -0800, Tony Godshall wrote:
> > Hi, folks.
> > 
> > I've got 2.6.10 running with udev.  Debian source, custom
> > compile for Pentium M plus nvidia.
> > 
> > Works great, till a couple days later when I want to play a
> > track in xmms (don't use sound much :-) )
> > 
> > It can't find /dev/dsp*.  Neither can madplay.  aumix can't
> > find /dev/mixer*.  Strange.
> > 
> > So I poke around and lsmod shows sound stuff loaded.
> 
> Umm, which "sound stuff"?

mo:/etc/udev/rules.d# lsmod |grep snd
snd_pcm_oss            49060  0 
snd_mixer_oss          17792  1 snd_pcm_oss
snd_intel8x0m          15236  0 
snd_intel8x0           28576  0 
snd_ac97_codec         73824  2 snd_intel8x0m,snd_intel8x0
snd_pcm                85384  4
snd_pcm_oss,snd_intel8x0m,snd_intel8x0,snd_ac97_codec
snd_timer              21380  1 snd_pcm
snd                    47460  7
snd_pcm_oss,snd_mixer_oss,snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore               7584  2 i810_audio,snd
snd_page_alloc          7620  3
snd_intel8x0m,snd_intel8x0,snd_pcm

I suppose I should also mention the machine type: 
Dell Inspiron 8600.

> Have you installed the alsa packages?

Yes.
 
> $ grep CONFIG_SND /usr/src/linux/.config

Wait.  Am I on the right list?  Isn't this debian-user?  ;-)
You must mean one of these...

  grep CONFIG_SND /usr/src/kernel-source-$(uname -r)/.config
  grep CONFIG_SND /boot/config-$(uname -r)

But regardless... too much output to post, and the fact that
the lsmod shows the modules loaded make it moot.


> Also, have you installed the alsa packages?

Ah, neglected to mention that alsa-mixer works, and worked
before the symlink.  Ergo, alsa installed.

 
> > I do a find in /dev/ and it turns out there's a .static
> > subdir and the old static devices are down there.  This
> > makes a little sense, since Alban Browaeys recently wrote...
> > 
> > > ...  if a device file is not created it is because either 
> > > because the driver does not support sysfs yet (as driver 
> > > which did not supported devfs failed too) ...
> > >
> > > /dev/.static or old /.dev are really usefull as not all
> > > kernel drivers are yet ported to sysfs/hotplug (and some 
> > > won't be before 2.7 as the risk for mass bugs is too 
> > > heavy : console driver ...). Well they may be if 2.7
> > > takes too long to appear.
> > 
> > OK. So perhaps that's the problem...
> > 
> > Here's what I did to fix it for now...
> > 
> >   ln -s /dev/.static/dev/mixer0 /dev/mixer0
> >   ln -s /dev/.static/dev/mixer0 /dev/mixer
> >   ln -s /dev/.static/dev/dsp0 /dev/dsp
> >   ln -s /dev/.static/dev/dsp0 /dev/dsp0
> >   chmod ugo+rx /dev/.static
> > 
> > This won't persist past a reboot, so I'm wondering what I
> > should do.  Tried to look for a way to make a custom udev
> > rule for it, but ...
> > 
> >   # udevinfo -a -p $(udevinfo -q path -n /dev/./.static/dev/dsp0)
> >   couldn't get the class device
> > 
> >   # udevinfo -a -p $(udevinfo -q path -n /dev/./.static/dev/mixer0)
> >   couldn't get the class device

Thanks for the quick response, Ron.



Reply to: