Summary says everything, log attached. emerge info: Portage 2.0.48 (default-x86-1.4, gcc-3.2.2, glibc-2.3.2-r1) ================================================================= System uname: 2.4.20-pfeifer-r1_pre10 i686 AMD Athlon(tm) XP 1600+ GENTOO_MIRRORS="http://gentoo.linux.no" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/cvs/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/portage.local" USE="x86 oss apm gif jpeg kde libg++ mikmod mmx ncurses pdflib png quicktime spell xml2 xmms xv zlib alsa gdbm berkdb slang readline tcltk guile X sdl gpm tcpd pam libwww ssl perl python imlib gtk qt motif opengl mozilla aavm nls ipv6 oggvorbis -gnome crypt mysql cdr apache2 -java -svga -directfb -esd -ldap -cups -arts encode truetype dvd mpeg avi 3dnow sse" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-mcpu=athlon-xp -O2 -pipe" CXXFLAGS="-mcpu=athlon-xp -O2 -pipe" ACCEPT_KEYWORDS="x86 ~x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache userpriv usersandbox" Reproducible: Always Steps to Reproduce: 1. emerge alsa-driver 2. 3.
Created attachment 12243 [details] alsa-driver-0.9c sandbox violation log small detail from the console output: ... install -m 755 -g root -o root utils/alsasound /var/tmp/portage/alsa-driver-0.9.3c/image//etc/init.d/alsasound; \ fi The ALSA devices were removed from /proc/asound/dev directory. Creating static device entries in /dev/snd. ACCESS DENIED unlink: /dev/mixer rm: cannot remove `/dev/mixer': Permission denied ACCESS DENIED unlink: /dev/mixer0 rm: cannot remove `/dev/mixer0': Permission denied ...
try again without USERPRIV
Removed userpriv and usersandbox from FEATURES, but the problem remains exactly the same. Maybe the alsa Makefile ignores DESTDIR when install invoked?
Strange, I cannot replicate it. However, this may be related to this: http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg08006.html I'll attach the patch, mentioned in the message. Won't be able to get to it until a few days later, though.
Created attachment 12338 [details, diff] The patch Tom Burkart's patch.
Created attachment 12339 [details, diff] The patch
Comment on attachment 12339 [details, diff] The patch Duplicate
On a second look, the patch is about installing the init script, but the access violations are caused by trying to create device entries in /dev, so the patch is not likely to be relevant to this issue.
Should be fixed in 0.9.3c-r1.
Ok, -r1 installed, but root:~# alsactl restore alsactl: set_controls:982: snd_ctl_open error: No such file or directory root:~# alsamixer alsamixer: function snd_ctl_open failed for default: No such file or directory strace alsamixer shows: ... open("/dev/snd/controlC0", O_RDWR) = -1 ENOENT (No such file or directory) open("/dev/snd/controlC0", O_RDONLY) = -1 ENOENT (No such file or directory) I can fix it with untar alsa-driver archive, and run the snddevices script in it. That make the neccessary devices and symlinks.
Are you using devfs?
No, i don't. Always have problems with devfs.
Aha, that explains it. Previously you had a symlink /dev/snd -> /proc/asound/dev. With 0.9.3c they have removed /proc/asound/dev, so you, indeed, need to create the entries in /dev with the snddevices script. Perhaps the ebuild should be installing it somewhere for those not using devfs. Will get to this later.
Thank you for the explanation.
The revised 0.9.3c-r1 now installs /usr/sbin/snddevices and prints a message, telling the people who are not using devfs to run the script. Thanks for your feedback.
