Thanks, Clemens. Right, initially /dev/snd/*, /dev/dsp*, and
/dev/audio* permissions were 600 root:root, and this is presumably set
by udev. In this state, mpd2 could not access the devices, but if when
I added mpd2 user to the root group it could, providing a somewhat
insecure kludgey solution to my problem. So I keep looking for another
solution...
Then I added the following lines to my
/etc/security/console.perms.d/50-default.perms:
<sound>=/dev/dsp* /dev/snd/* /dev/audio*
<…
[View More]console> 0666 <sound> 0600 root.audio
and now the permissions are 0666 root.audio by default. When I log in
as user tim, it appears that the permissions get changed to 0666
tim.audio. This should still be fine, bc my mpd2 user is in the audio
group, so *should* have read/write access. When I su mpd2, the
permissions listed are the same, but mpd2 can't access the devices. I
haven't tried actually logging in as mpd2 bc I didn't think it would
be any different. I will try that later, but this may all be a moot
point bc mpd2 is basically going to be a "server-only" user, with
SHELL=/sbin/nologin, so for all this, I've modified the user to use
bash just for testing purposes.
Interestingly, as mpd2, I get permission denied error when try to
access /dev/snd/pcmC0D0c, but as tim I get the expected error:
[mpd2@servy tim]$ ls -la /dev/snd
total 0
drwxr-xr-x 2 root root 460 2008-02-06 22:17 .
drwxr-xr-x 15 root root 4520 2008-02-06 22:17 ..
crw-rw-rw-+ 1 tim audio 116, 17 2008-02-06 22:17 controlC0
crw-rw-rw-+ 1 tim audio 116, 22 2008-02-06 22:17 controlC1
crw-rw-rw-+ 1 tim audio 116, 12 2008-02-06 22:17 controlC2
crw-rw-rw- 1 tim audio 116, 4 2008-02-06 22:17 controlC3
crw-rw-rw-+ 1 tim audio 116, 13 2008-02-06 22:17 midiC0D0
crw-rw-rw-+ 1 tim audio 116, 18 2008-02-06 22:17 midiC1D0
crw-rw-rw- 1 tim audio 116, 3 2008-02-06 22:17 midiC3D0
crw-rw-rw-+ 1 tim audio 116, 16 2008-02-06 22:17 pcmC0D0c
crw-rw-rw-+ 1 tim audio 116, 15 2008-02-06 22:17 pcmC0D0p
crw-rw-rw-+ 1 tim audio 116, 14 2008-02-06 22:17 pcmC0D1p
crw-rw-rw-+ 1 tim audio 116, 21 2008-02-06 22:17 pcmC1D0c
crw-rw-rw-+ 1 tim audio 116, 20 2008-02-06 22:17 pcmC1D0p
crw-rw-rw-+ 1 tim audio 116, 19 2008-02-06 22:17 pcmC1D1p
crw-rw-rw-+ 1 tim audio 116, 11 2008-02-06 22:17 pcmC2D0c
crw-rw-rw-+ 1 tim audio 116, 10 2008-02-06 22:17 pcmC2D0p
crw-rw-rw-+ 1 tim audio 116, 9 2008-02-06 22:17 pcmC2D1c
crw-rw-rw-+ 1 tim audio 116, 8 2008-02-06 22:17 pcmC2D2c
crw-rw-rw-+ 1 tim audio 116, 7 2008-02-06 22:17 pcmC2D3c
crw-rw-rw-+ 1 tim audio 116, 6 2008-02-06 22:17 pcmC2D4p
crw-rw-rw-+ 1 tim audio 116, 5 2008-02-06 22:17 seq
crw-rw-rw-+ 1 tim audio 116, 2 2008-02-06 22:17 timer
[mpd2@servy tim]$ cat /dev/snd/pcmC0D0c
cat: /dev/snd/pcmC0D0c: Permission denied [mpd2@servy tim]$ exit exit
[tim@servy ~]$ cat /dev/snd/pcmC0D0c
cat: /dev/snd/pcmC0D0c: File descriptor in bad state
An interesting observation is that when the sound devices were owned
by root:root, when I add mpd2 user to root group, mpd2 can access the
sound devices. But when I change the sound device to be owned by
root:audio, adding the mpd2 user to audio group doesn't allow mpd2 to
access the devices! This tells me that there's more to this than the
device permissions. Any ideas?
Tim
-----Original Message-----
From: linux-audio-user-bounces(a)lists.linuxaudio.org on behalf of Clemens Ladisch
Sent: Thu 2/7/2008 12:18 AM
Cc: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] ALSA device not found by some users... why?
Tim Black wrote:
> User mpd2 needs access to ALSA devices bc I'm running MPD (music
> player daemon) as this user. When this daemon tries to access ALSA
> device hw:0,0, it gets an "Error opening ALSA device: hw:0,0 No such
> device" error. (But if I run the daemon as 'tim' or root there are no
> such errors.)
When the device nodes in /dev/snd/ are created dynamically (with
udev), it's possible that their permissions are set by the udev rules
and do not come from the directory.
When you log in as mpd2, what are the permissions of the files in
/dev/snd/? Do you get the expected result when doing "cat
/dev/snd/pcmC0D0c"? (The expected result is "file descriptor in bad
state".)
Regards,
Clemens
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
[View Less]
Some users on my Fedora Core 8 system cannot seem to access any ALSA devices, while some can:
[tim@servy ~]$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: AudioPCI [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: AudioPCI_1 [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
Subdevices: 1/1
…
[View More]Subdevice #0: subdevice #0
card 1: AudioPCI_1 [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: I6300ESB [Intel 6300ESB], device 0: Intel ICH [Intel 6300ESB]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: I6300ESB [Intel 6300ESB], device 4: Intel ICH - IEC958 [Intel 6300ESB - IEC958]
Subdevices: 1/1
Subdevice #0: subdevice #0
while:
[tim@servy ~]$ su mpd2
Password:
[mpd2@servy tim]$ aplay -l
**** List of PLAYBACK Hardware Devices ****
<empty list>
User mpd2 needs access to ALSA devices bc I'm running MPD (music player daemon) as this user. When this daemon tries to access ALSA device hw:0,0, it gets an "Error opening ALSA device: hw:0,0 No such device" error. (But if I run the daemon as 'tim' or root there are no such errors.)
I created a new "audio" group, made all sound devices (/dev/snd/, /dev/dsp*, /dev/audio*) accessible to the "audio" group members, and added the mpd2 user to this group, but I still get the same errors. In fact, the only way I've been able to get past the permission problem is to put the new users into the root group, which is not an acceptable solution to me.
So this seems very much like a case of bad ALSA device permissions, but I don't know what else I can do to fix it. Do you? What am I missing?
The /proc/asound filesystem seems to be fully populated and accessible by both tim and mpd2. My ALSA Driver Version is 1.0.15 (Tue Nov 20 19:16:42 2007 UTC).
Since I'm using FC8, I was beginning to think that PulseAudio was behind this. I've followed the threads on FC8 audio problems, but none of the suggested solutions have worked for me. (I have ConsoleKit and avahi daemons running and have removed alsa-plugins-pulseaudio and am still getting the same errors.)
I would appreciate any suggestions or clues anyone might have.
Thanks,
Tim
BIAMP SYSTEMS EMAIL NOTICE
The information contained in this email and any attachments is confidential and
may be subject to copyright or other intellectual property protection. If you
are not the intended recipient, you are not authorized to use or disclose this
information, and we request that you notify us by reply mail or telephone and
delete the original message from your mail system.
[View Less]
linux-audio-user-request(a)lists.linuxaudio.org wrote:
> 2. Re: OT What newer CDR/RW drives should I consider? opps I
> forgot a few things... (Matthias Sch?nborn)
> 3. Re: Fwd: Re: OT What newer CDR/RW drives should I consider?
> opps I forgot a few things... (Allan Wind)
> Message: 3
> Date: Tue, 5 Feb 2008 17:43:23 -0500
> From: Allan Wind
>
> On 2008-02-05T17:16:25-0500, ka1iic(a)prexar.com wrote:
>> I'm replacing an old Matshita CW-7585 …
[View More]ATAPI IDE internal drive and wish a
>> newer drive to be a 'plugin' replacement... It's a junk parts system with an
>> old INTEL 1.7GHZ mother board and I use it for single copies of original
>> music... and little more...
>
> The last (DVD RW) drive that I got was from Lite-On based on reviews,
> and end-user feedback. It has worked just fine.
I got a LiteOn DVD-RW last week. 20x write on DVD's, 48x write on CD's,
SATA2 interface. BIOS found it, FC5 found it, works just fine so far
though I haven't tried writing anything yet.
--
David http://iwr.ru.ac.za/~iwdf/
If you receive email saying "Send this to everyone you know",
PLEASE pretend you don't know me.
[View Less]
Hi
I recently switched to ubuntu (from debian) and for the most parts I'm
doing ok. However when running the realtime kernel (that's part of
ubuntu, I think I simply imstalled it by "apt-get install linux-image-rt
linux-restricted-modules-rt") the computer completely freezes (not even
accepting incomming ssh) when copying larger files with scp.
Very small files are ok, just now it died on my with a 8M file.
I'm running the ath_pci module from restricted modules for my wlan card,
and the …
[View More]problem is not there when booting into the unpatched, regular
ubuntu kernel.
Anyone heard of something like this? Any solutions? Where to file a
bugreport?
--
peace, love & harmony
Atte
http://atte.dk | http://myspace.com/attejensenhttp://anagrammer.dk | http://modlys.dk
[View Less]
One colleague is specially interested in making [1]Independence Free
running via fst...
1. http://www.yellowtools.com/
Unfortunatelly...
JACK tmpdir identified as [/dev/shm]
err:ole:CoInitializeEx Attempt to change threading model of this
apartment from multi-threaded to apartment threaded
gui_thread_id = 16
The program 'fst.exe.so' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial …
[View More]52387 error_code 179 request_code 156 minor_code 7)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Running the program with the --sync command line option makes no
difference in debugging output.
Anybody running Independence Free successfully through any of the
available VST solutions?
My colleague is interested in bass sounds, meaning acoustic (rock,
pop, jazz) bass sounds. What are the best acoustic bass sounds
available for Linux users around? Thanks in advance!
Cordially, Ismael
--
Ismael Valladolid Torres GnuPG key: DE721AF4
SHS Polar (3.4.3) Google Talk/Jabber/MSN Messenger: ivalladt(a)gmail.com
C/ Emilio Vargas 1 Jaiku/Twitter/Skype/Yahoo!: ivalladt
Edif. Fiteni II AIM/ICQ: 264472328
28043 Madrid (Spain)
The opinions expressed here represent my own and not those of my employer.
Las opiniones expresadas representan las mías propias y no las de mi empresa.
[View Less]
Hello all,
I've been racking my brains over this for some time now. I have an
older (2003 or so, but still pretty decent) dual processor AMD machine
with an Echo Layla 3G audio interface, and connected to the Layla via
ADAT, an Alesis AI3 A/D converter. So after some hunting, I
discovered that the Echo driver is written so that the analog and
digital parts of the I/O appear on hw:0,0 and hw:0,1, respectively.
So I learned how to make an .asoundrc file using the "multi" plugin to
combine all …
[View More]32 channels (16 analog, total ins and outs, and 16 ADAT)
into a single interface. So far, so good... Jack sees all 16 ins and
16 outs, and i can get audio to pass at various sample rates through
all the channels (so I'm assuming it's not a sync problem). However,
running UbuntuStudio's realtime kernel, I get about 3-4 xruns per
second. I have so far tried:
-editing /etc/security/limits.conf with appropriate values for the audio group
-tweaking the realtime priority of jack, various timer threads, and
the IRQ thread for Layla, using chrt (jack is set to RT via qjackctl)
-setting the frames/period as high as 2048 seems to have little, if
any, effect, though setting it way down (32-64 frames) gives hundreds
of xruns per second.
The problem does not seem to be present when i use either hw:0,0 or
hw:0,1 directly as the device (with no other settings changed)... in
fact, i can run Jack reliably at 32 frames when i do so, leading me to
think it's either a) something with the multi plugin or asoundrc? or,
b) perhaps a slight ADAT clock jitter? (the AI3 syncs to whatever
clock it finds on its inputs, plus Layla's clock is set to internal,
so this seems unlikely.)
Anyone have any suggestions as to what to try next?
Thanks in advance for any help whatsoever...
----
here are some more details:
running alsa version 1.0.14, jack version 0.103.0
contents of my .asoundrc:
# create a virtual sixteen-channel device with layla's
# analog and digital i/o:
pcm.layla16 {
type multi;
slaves.a.pcm "hw:0,0";
slaves.a.channels 8;
slaves.b.pcm "hw:0,1";
slaves.b.channels 8;
bindings.0.slave a;
bindings.0.channel 0;
bindings.1.slave a;
bindings.1.channel 1;
bindings.2.slave a;
bindings.2.channel 2;
bindings.3.slave a;
bindings.3.channel 3;
bindings.4.slave a;
bindings.4.channel 4;
bindings.5.slave a;
bindings.5.channel 5;
bindings.6.slave a;
bindings.6.channel 6;
bindings.7.slave a;
bindings.7.channel 7;
bindings.8.slave b;
bindings.8.channel 0;
bindings.9.slave b;
bindings.9.channel 1;
bindings.10.slave b;
bindings.10.channel 2;
bindings.11.slave b;
bindings.11.channel 3;
bindings.12.slave b;
bindings.12.channel 4;
bindings.13.slave b;
bindings.13.channel 5;
bindings.14.slave b;
bindings.14.channel 6;
bindings.15.slave b;
bindings.15.channel 7;
}
# Create a fake mixer for Jack to talk to
ctl.layla16 {
type hw;
card 0;
}
Some JACK output:
20:49:28.832 JACK is starting...
20:49:28.832 jackd -R -P60 -t2000 -dalsa -dlayla16 -r48000 -p1024 -n2
20:49:28.836 JACK was started with PID=6352 (0x18d0).
jackd 0.103.0
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 ..
apparent rate = 48000
creating alsa driver ...
layla16|layla16|1024|2|48000|16|16|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
ALSA: final selected sample format for capture: 32bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 2 periods for playback
20:49:30.863 Server configuration saved to "/home/sean/.jackdrc".
20:49:30.864 Statistics reset.
20:49:30.866 Client activated.
20:49:30.869 Audio connection change.
20:49:30.882 Audio connection graph change.
JACK tmpdir identified as [/dev/shm]
20:49:30.984 XRUN callback (1).
20:49:32.285 XRUN callback (2).
20:49:32.883 XRUN callback (4 skipped).
20:49:35.740 XRUN callback (6).
20:49:37.259 Client deactivated.
20:49:37.261 JACK is stopping...
jack main caught signal 15
no message buffer overruns
20:49:37.283 JACK was stopped successfully.
[View Less]
Now that LAM is back up, I've been catching up on what's posted.
I've really enjoyed the music that Benoit Rouits has posted. Very interesting, meditative, ambient kind of stuff. Some of the sounds and patches are just gorgeous too (i.e. on "Organum").
Nice stuff, very impressive.
-ken
OK folks...
I know I did it again I forgot some of the more important things in my
specs...
I'm replacing an old Matshita CW-7585 ATAPI IDE internal drive and wish a
newer drive to be a 'plugin' replacement... It's a junk parts system with an
old INTEL 1.7GHZ mother board and I use it for single copies of original
music... and little more...
I am using X-CD-Roast and wish to stay with that program....
Excuse the lack of info...
vince
On Monday 04 February 2008 22:05, Vince Werber wrote:…
[View More]
> Hi Folks...
>
> It's about time for me to get a few more CD-R/RW drives for a Slackware 11
> box...
>
> Only CD read and write are required, speed isn't an issue either... Price
> is but these things seems to be low enough in price these days so even that
> doesn't seem to be an issue...
>
> Writing is the important part... I don't rip CD's anyway...
>
> So... what new units do you all recommend these days???
>
> Thanks in advanced
>
> vince aka Wesa
>
> http://vincewerber.org
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
-------------------------------------------------------
[View Less]
So if I understand correctly, my AES32 has the same matrix
functionality as the HDSP cards, but the hdspmixer (and similar
hdsptools) do not recognize the AES32. (Apparently hdspmixer hasn't
been kept up to date for quite a while)
Does hdspmixer just need the card definitions of the AES32 added or is
the differences between it and the HDSP series more complex than that?
Are there any patches floating around for this?
-Reuben