Takashi Iwai wrote:
>>Quite embarassing, i discovered the permissions on the directory
>>/usr/share/alsa were 644 :-( Changed that to 755 and now it works.
> 
> oh, it's a good news. i totally forgot this possibility. should be added to FAQ :)

I added this to AlsaTips at the Wiki. Hopefully this is correct now ?
(I've always used devfs so I didn't realize the point about /proc perms)

 > Incorrect advice... should have been "chmod 666 /dev/snd/*". And to 
compliment
 > this insecure setting the directory itself needs to be "chmod 755 
/dev/snd".

This may not work because often, on a non-devfs enabled system, /dev/snd 
is symlinked to /proc/asound/dev where the permission cannot be manually 
modified. The most reliable way to change the owner/permission is to 
pass a proper module option to snd.o when ALSA starts up in 
/etc/modules.conf with a line similar to...

options snd snd_major=116 snd_cards_limit=4 snd_device_mode=0660 
snd_device_gid=29 snd_device_uid=0

--------------------------------------------

This below is included near the above entry, it's unclear (to me) what it
really refers to or if the (whatever) problem it solves is still valid ?
Any hints as to how to "refactor" these few lines below, anyone ?

if you use devfs interface for /dev, you cannot use the 2nd or later 
card with the original sound_core.c on 2.4 kernel. if you use proc 
interface for /dev/snd, it works anyway. also -

if you build the kernel without devfs support and use 2nd or later 
cards, then you'll get annoying error messages, even if you use proc 
interface.  (it's harmless, though.)

--markc



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to