On Saturday 11 September 2010 14:39:05 luxInteg wrote: > Greetings > > /etc/udev/rules.d/40-alsa.rules in:- > from (http://lfs.aliensoft.org/blfs/view/svn/multimedia/alsa-utils.html ) > > # When a sound device is detected, restore the volume settings > KERNEL=="controlC[0-9]*", ACTION=="add", RUN+="/usr/sbin/alsactl restore > %n" > > With the latter, on a cblfs setup with kde-4.4.5 sound devices are detected > correctly as per > (http://pulseaudio.org/wiki/KDE > for example) and shows that phonon and > pulse are correctly talking. BUT this is available only to the group > root. > > > If the /etc/udev/rules.d/40-alsa.rules is amended so that sound devices > are accessible to users in the group audio (for example) like so:- > -------------------------------------------------------------------- > # ALSA Devices > SUBSYSTEM=="snd", GROUP="audio" > # When a sound device is detected, restore the volume settings > KERNEL=="controlC[0-9]*", NAME="snd/%k", GROUP="audio", ACTION=="add", > RUN+="/usr/sbin/alsactl restore %n" > KERNEL=="hw[CD0-9]*", NAME="snd/%k", GROUP="audio" > KERNEL=="pcm[CD0-9cp]*", NAME="snd/%k", GROUP="audio" > KERNEL=="midiC[D0-9]*", NAME="snd/%k", GROUP="audio" > KERNEL=="timer", NAME="snd/%k", GROUP="audio" > KERNEL=="seq", NAME="snd/%k", GROUP="audio" > ------------------------------------------------------------------------ >
excerpt from ( http://www.pulseaudio.org/wiki/PerfectSetup) { There are three kind of distributions: 1) those who control access to the sound card by adding users to the "audio" group, 2) those who use HAL and ConsoleKit to dynamically give access to the currently "active" user, but allow overriding that using the "audio" group and 3) those who don't use the "audio" group at all, but rely solely on HAL+ConsoleKit to grant access to the sound card. To find out which group your distribution belongs to, run ls -l /dev/snd. If the permission field of many of the listed files contains a plus character in the end, like this: crw-rw----+ 1 root audio 116, 7 Aug 2 08:57 pcmC0D0p then your distribution most likely belongs to group 2 or 3 If there was no plus character in the permission fields, like in this example: crw-rw---- 1 root audio 116, 7 Aug 2 08:57 pcmC0D0p } --------- for a blfs setup the output is below linteg [ ~ ]$ ls -l /dev/snd total 0 drwxr-xr-x 2 root root 60 Sep 12 2010 by-path crw-rw---- 1 root audio 116, 10 Sep 12 2010 controlC0 crw-rw---- 1 root audio 116, 9 Sep 12 2010 hwC0D0 crw-rw---- 1 root audio 116, 8 Sep 12 2010 pcmC0D0c crw-rw---- 1 root audio 116, 7 Sep 12 2010 pcmC0D0p crw-rw---- 1 root audio 116, 6 Sep 12 2010 pcmC0D1c crw-rw---- 1 root audio 116, 5 Sep 12 2010 pcmC0D1p crw-rw---- 1 root audio 116, 4 Sep 12 2010 pcmC0D2c crw-rw---- 1 root audio 116, 3 Sep 12 2010 seq crw-rw---- 1 root audio 116, 2 Sep 12 2010 timer linteg [ ~ ]$ (I checked a fedora machine and they have the + sign) The BLFS appears to be category 1 so it begs the question if the latter udev rule above is not more adequate. HOWEVER the BLFS setup seems to be a hybrid of some sort. i)-------all we get is a dummy IF A) the file /usr/lib/dbus-1.0/dbus-daemon-launch-helper is owned by messagebus with permissions 4750 AND B ) if all users and pulse are in the "audio" group. ii)------- warning of absent ck-cookie shown in kdm.logs as ########################:- arguments to ck_connector_get_cookie() were incorrect, assertion "connector != NULL" failed in file ck-connector.c line 583. ######################## C) if the file /usr/lib/dbus-1.0/dbus-daemon-launch-helper is in the group root D) all sound devices enables to all users we should have D) with A) and and B) -not D) with C) -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
