1 |
Benny Pedersen posted |
2 |
<36728.80.166.75.19.1120793029.squirrel@×××××××××.org>, excerpted below, |
3 |
on Fri, 08 Jul 2005 05:23:49 +0200: |
4 |
|
5 |
> Sound server informational message: |
6 |
> Error while initializing the sound driver: device /dev/dsp can't be opened |
7 |
> (Permission denied) The sound server will continue, using the null output |
8 |
> device. |
9 |
> |
10 |
> i get a requester when starting x11 now and i don't know how to solve this |
11 |
> one :( |
12 |
> |
13 |
> using udev 0.58 |
14 |
|
15 |
There was just a problem with that, with the new udev-061, now masked |
16 |
pending a fix. However, if you're running 058, that shouldn't be the one |
17 |
you are having. |
18 |
|
19 |
Expanding on what Zac said, ensure your user is in the audio group, and |
20 |
that udev is set up to use that group for audio devices and that the mode |
21 |
is 660. |
22 |
|
23 |
Also, check your PAM settings, console.perms IIRC. Gentoo is moving away |
24 |
from using the PAM console-perms module by default, because it causes |
25 |
issues, but I've no idea if that's now on stable or if stable is still |
26 |
running console-perms by default. Basically, the idea of console-perms is |
27 |
to have the sound hardware and certain other devices belong to the first |
28 |
logged in console user. After they log off, perms switch to the second, |
29 |
etc. If nobody is logged in at the console, perms would switch to root |
30 |
only. Note that it is *NOT* necessary to be logged in at the console |
31 |
while you have an X session running, and this is in fact one of the big |
32 |
problems with pam-console-perms, and the reason Gentoo has decided to |
33 |
switch off of it. For those who don't understand how it works, it ends up |
34 |
looking like sometimes the perms work as expected, sometimes they don't, |
35 |
randomly, which of course causes serious support headaches. |
36 |
|
37 |
Anyway, if you aren't on a network and it's basically a single user at a |
38 |
time machine, you could probably get away with setting both PAM (if |
39 |
necessary) and UDEV permissions to 666, allowing all users to read/write |
40 |
the audio hardware, regardless of whether they are in the audio group. |
41 |
That's not necessarily a good thing on a decent sized office network, of |
42 |
course, because it's all too easy for someone else to login remotely, and |
43 |
set it playing embarrassing noises at the wrong time <g>, not to mention |
44 |
potential buffer overflows and the like, but for a single computer or |
45 |
home/SOHO network where all users are trusted and behind a suitable |
46 |
firewall, that'd generally be the least complicated thing to do. |
47 |
|
48 |
-- |
49 |
Duncan - List replies preferred. No HTML msgs. |
50 |
"Every nonfree program has a lord, a master -- |
51 |
and if you use the program, he is your master." Richard Stallman in |
52 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
53 |
|
54 |
|
55 |
-- |
56 |
gentoo-amd64@g.o mailing list |