Re: [proaudio] pam rlimits aware setup

[ Thread Index | Date Index | More lists.tuxfamily.org/proaudio Archives ]


Dominique Michel wrote:
Check at you are in the audio group:
# cat /etc/group

If not, add yourself:
# useradd -G audio username

Check the permission of the audio device:
# ls -l /dev/dsp* /dev/mixer*
lrwxrwxrwx  1 root root  9 mai 17 15:55 /dev/dsp -> sound/dsp
lrwxrwxrwx  1 root root 10 mai 17 15:55 /dev/dsp1 -> sound/dsp1
lrwxrwxrwx  1 root root 10 mai 17 15:55 /dev/dsp3 -> sound/dsp3
lrwxrwxrwx  1 root root 11 mai 17 15:55 /dev/mixer -> sound/mixer
lrwxrwxrwx  1 root root 12 mai 17 15:55 /dev/mixer1 -> sound/mixer1
lrwxrwxrwx  1 root root 12 mai 17 15:55 /dev/mixer2 -> sound/mixer2
lrwxrwxrwx  1 root root 12 mai 17 15:55 /dev/mixer3 -> sound/mixer3

If you don't have something like this:
# chgrp audio /dev/dsp* /dev/mixer*
(You may need to check udev rules if using udev, otherwise it will not work after a reboot)

this is what I get, but these are just symlinks so no real permissions
see below my real-permissions

***root@crazyfury (39 /etc/pam.d) $ ls -l /dev/dsp* /dev/mixer*
lrwxrwxrwx 1 root root  9 18. Mai 14:34 /dev/dsp -> sound/dsp
lrwxrwxrwx 1 root root 10 18. Mai 14:34 /dev/dsp1 -> sound/dsp1
lrwxrwxrwx 1 root root 10 18. Mai 14:34 /dev/dsp2 -> sound/dsp2
lrwxrwxrwx 1 root root 10 18. Mai 14:34 /dev/dsp3 -> sound/dsp3
lrwxrwxrwx 1 root root 11 18. Mai 14:34 /dev/mixer -> sound/mixer
lrwxrwxrwx 1 root root 12 18. Mai 14:34 /dev/mixer1 -> sound/mixer1
lrwxrwxrwx 1 root root 12 18. Mai 14:34 /dev/mixer2 -> sound/mixer2
lrwxrwxrwx 1 root root 12 18. Mai 14:34 /dev/mixer3 -> sound/mixer3
lrwxrwxrwx 1 root root 12 18. Mai 14:34 /dev/mixer4 -> sound/mixer4

real permissions
***root@crazyfury (39 /etc/pam.d) $ ls -l /dev/sound/dsp* /dev/sound/mixer*
crw-rw---- 1 root audio 14,  3 18. Mai 14:34 /dev/sound/dsp
crw-rw---- 1 root audio 14, 19 18. Mai 14:34 /dev/sound/dsp1
crw-rw---- 1 root audio 14, 35 18. Mai 14:34 /dev/sound/dsp2
crw-rw---- 1 root audio 14, 51 18. Mai 14:34 /dev/sound/dsp3
crw-rw---- 1 root audio 14,  0 18. Mai 14:34 /dev/sound/mixer
crw-rw---- 1 root audio 14, 16 18. Mai 14:34 /dev/sound/mixer1
crw-rw---- 1 root audio 14, 32 18. Mai 14:34 /dev/sound/mixer2
crw-rw---- 1 root audio 14, 48 18. Mai 14:34 /dev/sound/mixer3
crw-rw---- 1 root audio 14, 64 18. Mai 14:34 /dev/sound/mixer4

   Frieder


Which sound card are you using?
Dominique

Le Wed, 17 May 2006 22:47:33 -0500,
"Colin Shapiro" <cmshapiro@xxxxxxxxx> a écrit :

up to now I was forced to use a non-rt kernel because using reiser4 as
filesystem, but now I've added successfully reiser4 to rt-sources.
pam setup fails anyway
this is what jackd gives me

$ jackd -R -d alsa

jackd 0.100.7
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details

JACK compiled with System V SHM support.
loading driver ..
Enhanced3DNow! detected
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
[snip]
cannot use real-time scheduling (FIFO at priority 20) [for thread
-1228706896, from thread -1228706896] (1: Operation not permitted)
cannot use real-time scheduling (FIFO at priority 10) [for thread
-1237099600, from thread -1237099600] (1: Operation not permitted)


Well, that's definitely a permissions issue.

If it helps at all, I can say that the default rlimits values that I posted
earlier work for me.  I don't have realtime-lsm installed, and I can run
jackd in realtime mode without any issues.

I just recently recompiled all my audio tools from source (to get the latest
CVS updates), so all my packages are up-to-date.  That might not mean
anything, but it's worth mentioning.

- Colin





Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/