28 Sep
2005
28 Sep
'05
3:22 p.m.
Hi to the list,
I've a problem starting jackd from a a normal user. I'm on debian
testing and even using non-realtime mode I got this message:
$ jackd -dalsa
jackd 0.100.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.
cannot create /dev/shm/jack-1000 directory (Permission denied)
cannot create server sockets
cannot create engine
$ _
As you see I've jackd 0.100 (in testing there is 0.80) because after
seeng this problem I've upgraded to the unstable version, but I have the
same problem. I've tried both with my own kernel and with the debian
binary kernel (both are 2.6.12). From root jackd works perfectly.
This evening I'm going to try to compile 2.6.13, I will report any news.
Thanks for any answer.
Best Regards,
~ Antonio
28 Sep
28 Sep
4:06 p.m.
On 9/28/05, Antonio <debian(a)fastwebnet.it> wrote:
JACK compiled with System V SHM support.
cannot create /dev/shm/jack-1000 directory (Permission denied)
Hi,
It seems pretty clear to me that this is a permissions problem, not a
kernel issue. I would suggest looking at how shm is mounted in your
distro and whether users are given access. On my Gentoo machine I have
this in fstab:
shm /dev/shm tmpfs
nodev,nosuid,noexec 0 0
For me, using udev, it gets the job done.
NOTE: This also might be a groups issue. If your distro has an 'audio'
group, for instance, and if your securities setup enforces a user
being part of that group to use /dev/shm then this might stop you from
being able to creat /dev/shm/jack-1000 when you try to run Jack as a
normal user.
HTH,
Mark
29 Sep
29 Sep
5:19 a.m.
On Wed, 28 Sep 2005, Mark Knecht wrote:
On 9/28/05, Antonio <debian(a)fastwebnet.it>
wrote:
Make sure you have support for shm and tmpfs in the kernel.
(I think SHM is default but you have select
"Virtual memory filesystem support" under Filesystems/Pseudo fs)
If you have that you shouldn't have to have any entry in fstab;
the kernel automounts /dev/shm with 1777 permissions.
I've read that having fstab mount /dev/shm after the kernel has mounted
it might cause xruns.
The fstab entry, I think, is only for 2.4 kernels.
- Peder
JACK compiled with System V SHM support.
cannot create /dev/shm/jack-1000 directory (Permission denied)
Hi,
It seems pretty clear to me that this is a permissions problem, not a
kernel issue. I would suggest looking at how shm is mounted in your
distro and whether users are given access. On my Gentoo machine I have
this in fstab:
shm /dev/shm tmpfs
nodev,nosuid,noexec 0 0
7:33 a.m.
Hi Burkhard, Mark, Peder,
On Thu, 2005-09-29 at 09:19 +0200, Peder Hedlund wrote:
Sorry for not noting it was a permission issue with shm. I had compiled
"Virtual memory filesystem support" in the kernel. I have this situation
for /dev/shm:
drwxr-xr-x 3 root root 60 2005-09-29 11:05 shm
Now, manually changing the permissions to /dev/shm with chmod works (in
the sense that I can start jack from normal user). Manually mounting shm
in this way:
# mount -t tmpfs shm /dev/shm
works too, giving
drwxrwxrwt 2 root root 40 2005-09-29 11:25 shm
unmounting shm I return to have the bad permission. If I put the stanza
in the fstab I get (well, obviously) the right permission on boot.
How can I obtain that shm is mounted on boot with the right permission
without the fstab entry? It really matters that fstab entry?
Thanks for the help.
Best Regards,
~ Antonio
On Wed, 28 Sep 2005, Mark Knecht wrote:
[cut]
I would suggest looking at how shm is mounted in your
distro and
whether users are given access. On my Gentoo machine I have
this in fstab:
shm /dev/shm tmpfs
nodev,nosuid,noexec 0 0
Make sure you have support for shm and tmpfs in the kernel.
(I think SHM is default but you have select
"Virtual memory filesystem support" under Filesystems/Pseudo fs)
If you have that you shouldn't have to have any entry in fstab;
the kernel automounts /dev/shm with 1777 permissions.
I've read that having fstab mount /dev/shm after the kernel has mounted
it might cause xruns.
The fstab entry, I think, is only for 2.4 kernels.
8:58 a.m.
On Thu, 29 Sep 2005, Antonio wrote:
Hi Burkhard, Mark, Peder,
On Thu, 2005-09-29 at 09:19 +0200, Peder Hedlund wrote:
> If you have that you shouldn't have to have any entry in fstab;
> the kernel automounts /dev/shm with 1777 permissions.
> I've read that having fstab mount /dev/shm after the kernel has mounted
> it might cause xruns.
How can I obtain that shm is mounted on boot with the right permission
without the fstab entry? It really matters that fstab entry?
Hmm, guess I was a bit wrong about the kernele automounting.
In Mandrake /dev/shm is mounted by /etc/rc.sysinit :
mount -n -t tmpfs none /dev/shm
after it has mounted devpts.
I guess you could have it mounted either way (but not both).
Do you have a fstab entry and if so, what does it look like?
- Peder
9:36 a.m.
On Thu, 2005-09-29 at 12:58 +0200, Peder Hedlund wrote:
[cut]
In Mandrake /dev/shm is mounted by /etc/rc.sysinit :
mount -n -t tmpfs none /dev/shm
after it has mounted devpts.
I guess you could have it mounted either way (but not both).
Do you have a fstab entry and if so, what does it look like?
I had no fstab entry for shm in my debian etch (testing) system.
So /dev/shm had wrong permission. I don't now if this is a bug in the
jackd pachage. However, if I do one of these three things I get the
right permission so jack can start from normal user:
1) Add to fstab:
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
2) manually mont shm with:
# mount -t tmpfs shm /dev/shm
3) change the permissions:
# chomd a+rwx /dev/shm
So use 1) for now (as suggested by Mark previously). Is this the best
solution on debian? (Not that I don't trust Mark, but only to ask if
debian has a specific behaviour here).
[OT]
I don't have a devpts entry in fstab, should debian must have one?
(infact I currently have to manually mount devpts to open a subshell,
for example CRTL+O in mc).
[/OT]
Thanks again.
Best Regards,
~ Antonio
10:01 a.m.
I had no fstab entry for shm in my debian etch
(testing) system.
So /dev/shm had wrong permission. I don't now if this is a bug in the
jackd pachage. However, if I do one of these three things I get the
right permission so jack can start from normal user:
1) Add to fstab:
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
So use 1) for now (as suggested by Mark previously).
Is this the best
solution on debian? (Not that I don't trust Mark, but only to ask if
debian has a specific behaviour here).
That explains the faulty permissions; since no filesystem was mounted
on the (empty) directory /dev/shm it had the default 755 root.root.
The fstab entry is perfectly fine.
[OT]
I don't have a devpts entry in fstab, should debian must have one?
(infact I currently have to manually mount devpts to open a subshell,
for example CRTL+O in mc).
[/OT]
You (or the debian testing release) seem to have screwed up some
/etc files somewhat. As said, Mandrake has the mounting of devpts
in rc.sysinit, but I guess you could add that to fstab as well.
- Peder
30 Sep
30 Sep
9:49 a.m.
On Thu, Sep 29, 2005 at 02:01:08PM +0200, Peder Hedlund wrote:
On debian /etc/init.d/mountvirtfs handles /dev/pts as well as /dev/shm
--
Eric Dantan Rzewnicki | Systems Administrator
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
network(a)rfa.org.
I had no fstab
entry for shm in my debian etch (testing) system.
So /dev/shm had wrong permission. I don't now if this is a bug in the
jackd pachage. However, if I do one of these three things I get the
right permission so jack can start from normal user:
1) Add to fstab:
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
So use 1) for now (as suggested by Mark previously). Is this the best
solution on debian? (Not that I don't trust Mark, but only to ask if
debian has a specific behaviour here).
That explains the faulty permissions;
since no filesystem was mounted
on the (empty) directory /dev/shm it had the default 755 root.root.
The fstab entry is perfectly fine.
[OT]
I don't have a devpts entry in fstab, should debian must have one?
(infact I currently have to manually mount devpts to open a subshell,
for example CRTL+O in mc).
[/OT]
You (or the debian testing release) seem to have screwed up some
/etc files somewhat. As said, Mandrake has the mounting of devpts
in rc.sysinit, but I guess you could add that to fstab as well.
29 Sep
29 Sep
11:56 a.m.
On 9/29/05, Antonio <debian(a)fastwebnet.it> wrote:
However, if I do one of these three things I get the
right permission so jack can start from normal user:
1) Add to fstab:
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
Will survive a reboot.
2) manually mont shm with:
# mount -t tmpfs shm /dev/shm
Probably requires you to be root. Why bother. Could be done by user
with the proper entry in fstab.Why not use #1?
3) change the permissions:
# chomd a+rwx /dev/shm
Again, probably requires you to be root.
So use 1) for now (as suggested by Mark previously). Is this the best
solution on debian? (Not that I don't trust Mark, but only to ask if
debian has a specific behaviour here).
Sure. I don't trust Mark either! ;-)
Glad you have things working.
- Mark
12:10 p.m.
On Thursday 29 Sep 2005 12:37 pm, Antonio wrote:
On Thu, 2005-09-29 at 12:58 +0200, Peder Hedlund
wrote:
[cut]
Hi. I have 3 Debian installs that started off as Woody 3.0r2, then upgraded to
Sarge (which was then testing) One of these is now getting updates from
testing which is now Etch. I looked in my /etc/fstab and don't have that
entry either and yet jack starts ok as user. The only extras in /etc/fstab
are for the 2.6 kernel.
none /sys sysfs defaults 0 0
none /proc/bus/usb usbdevfs defaults 0 0
I admit I had some problems getting Debian's sound working, having only
previously worked on sounds on FC1 & FC2 from planetccrma, and Slackware 10.0
with Audioslacks mmkernel and packages. Some folks on lists helped me with
the Debian sounds. I had to add myself to the audio group, and as I don't
have realtime, had to uncheck the realtime box in qjackctl before jack would
start. This worked fine as user for kernel 2.4.27, apart from having to
comment out in /etc/hotplug/blacklist the entry for awe_wave which I also
added to /etc/modules. This is to enable the loading of soundfonts on my
Audigy2 soundblaster card. For the 2.6 kernels I had to add more modules to
/etc/modules to get my usb midi keyboard working, as below.
snd-usb-audio
uhci-hcd
snd-emu10k1-synth (needed for loading soundfonts onto Audigy2 soundblaster
card for 2.6 kernel)
Also nothing to do with sounds, but X wouldn't start with 2.6 kernel, and had
to add mousedev & psmouse to /etc/modules which fixed this.
You are no doubt a member of the audio group. If not, the synax as root, is.
#usermod -G audio your_user_name. All the best. Nigel.
Debian Sarge/Etch
Kernels: 2.4.27, 2.6.8, 2.6.11
Alsa version: 2.4.27 kernel. Alsa 1.0.9. 2.6.11 kernel, Alsa 1.0.8
In Mandrake /dev/shm is mounted by
/etc/rc.sysinit :
mount -n -t tmpfs none /dev/shm
after it has mounted devpts.
I guess you could have it mounted either way (but not both).
Do you have a fstab entry and if so, what does it look like?
I had no fstab entry for shm in my debian etch (testing) system.
So /dev/shm had wrong permission. I don't now if this is a bug in the
jackd pachage. However, if I do one of these three things I get the
right permission so jack can start from normal user:
1) Add to fstab:
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
2) manually mont shm with:
# mount -t tmpfs shm /dev/shm
3) change the permissions:
# chomd a+rwx /dev/shm
So use 1) for now (as suggested by Mark previously). Is this the best
solution on debian? (Not that I don't trust Mark, but only to ask if
debian has a specific behaviour here).
[OT]
I don't have a devpts entry in fstab, should debian must have one?
(infact I currently have to manually mount devpts to open a subshell,
for example CRTL+O in mc).
[/OT]
Thanks again.
Best Regards,
~ Antonio 
10:27 p.m.
On Thu, 29 Sep 2005 13:37:26 +0200
Antonio <debian(a)fastwebnet.it> wrote:
[OT]
I don't have a devpts entry in fstab, should debian must have one?
(infact I currently have to manually mount devpts to open a subshell,
for example CRTL+O in mc).
[/OT]
On my Debian testing, /dev/pts and /dev/shm are both mounted
by /etc/init.d/mountvirtfs, that is called during the single user part
of the boot sequence. No need for an fstab entry.
I don't know why it isn't so on your system.
--
David
10:41 p.m.
On 9/29/05, David <dplist(a)free.fr> wrote:
On Thu, 29 Sep 2005 13:37:26 +0200
Antonio <debian(a)fastwebnet.it> wrote:
I don't know anything about Debian, but the fact that it's being
mounted by mountvirtfs means that it's not 'automaticly done',
correct? File systems can be mounted even if they aren't in fstab, but
shm isn't done automatically as someone suggested earlier.
Since my Gentoo systems don't have this mountvirtfs script it doesn't
happen on my box.
Or so I think... ;-)
- Mark
[OT]
I don't have a devpts entry in fstab, should debian must have one?
(infact I currently have to manually mount devpts to open a subshell,
for example CRTL+O in mc).
[/OT]
On my Debian testing, /dev/pts and /dev/shm are both mounted
by /etc/init.d/mountvirtfs, that is called during the single user part
of the boot sequence. No need for an fstab entry.
I don't know why it isn't so on your system.
30 Sep
30 Sep
9:54 a.m.
On Thu, Sep 29, 2005 at 05:41:20PM -0700, Mark Knecht wrote:
On 9/29/05, David <dplist(a)free.fr> wrote:
Correct, they're not automatically mounted by the kernel.
On Thu, 29 Sep 2005 13:37:26 +0200
Antonio <debian(a)fastwebnet.it> wrote:
I don't know anything
about Debian, but the fact that it's being
mounted by mountvirtfs means that it's not 'automaticly done',
correct? File systems can be mounted even if they aren't in fstab, but
shm isn't done automatically as someone suggested earlier. [OT]
I don't have a devpts entry in fstab, should debian must have one?
(infact I currently have to manually mount devpts to open a subshell,
for example CRTL+O in mc).
[/OT]
On my Debian testing, /dev/pts and /dev/shm are both mounted
by /etc/init.d/mountvirtfs, that is called during the single user part
of the boot sequence. No need for an fstab entry.
I don't know why it isn't so on your system. Since my Gentoo systems don't have this
mountvirtfs script it doesn't
happen on my box.
grep -ri shm /etc/init.d/ ??
--
Eric Dantan Rzewnicki | Systems Administrator
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
network(a)rfa.org.
10:24 a.m.
On 9/30/05, Eric Dantan Rzewnicki <rzewnickie(a)rfa.org> wrote:
Right. It's not there AFAICT. If you want shm mounted you put it in
fstab to get it mounted, just like all your other file systems..
I like Gentoo. Very little magic. (Except for recent udev changes...) ;-)
Cheers,
Mark
Since my Gentoo systems don't have this
mountvirtfs script it doesn't
happen on my box.
grep -ri shm /etc/init.d/ ??
9:47 a.m.
On Thu, Sep 29, 2005 at 01:37:26PM +0200, Antonio wrote:
On Thu, 2005-09-29 at 12:58 +0200, Peder Hedlund
wrote:
[cut]
On debian sarge /dev/shm is mounted by /etc/init.d/mountvirtfs
ls -la /etc/rcS.d/S02mountvirtfs
lrwxr-xr-x 1 root root 21 Jun 19 2004 /etc/rcS.d/S02mountvirtfs ->
../init.d/mountvirtfs
I have no /dev/shm entry in /etc/fstab and /dev/shm looks like this:
eric@audiobox:~$ ls -la /dev/shm/
total 24
drwxrwxrwt 4 root root 80 Aug 28 17:56 .
drwxr-xr-x 14 root root 24576 Aug 28 17:52 ..
drwx------ 3 eric eric 60 Aug 28 17:56 jack-1000
drwxr-xr-x 2 root root 60 Aug 28 17:50 network
I don't have an etch system handy to check, but would expect it to be
the same there.
--
Eric Dantan Rzewnicki | Systems Administrator
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
network(a)rfa.org.
In Mandrake /dev/shm is mounted by
/etc/rc.sysinit :
mount -n -t tmpfs none /dev/shm
after it has mounted devpts.
I guess you could have it mounted either way (but not both).
Do you have a fstab entry and if so, what does it look like?
I had no fstab entry
for shm in my debian etch (testing) system.
So /dev/shm had wrong permission. I don't now if this is a bug in the
jackd pachage. However, if I do one of these three things I get the
right permission so jack can start from normal user:
1) Add to fstab:
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
2) manually mont shm with:
# mount -t tmpfs shm /dev/shm
3) change the permissions:
# chomd a+rwx /dev/shm
So use 1) for now (as suggested by Mark previously). Is this the best
solution on debian? (Not that I don't trust Mark, but only to ask if
debian has a specific behaviour here).
11:27 a.m.
Hi,
On Fri, 2005-09-30 at 07:47 -0400, Eric Dantan Rzewnicki wrote:
On debian sarge /dev/shm is mounted by
/etc/init.d/mountvirtfs
ls -la /etc/rcS.d/S02mountvirtfs
lrwxr-xr-x 1 root root 21 Jun 19 2004 /etc/rcS.d/S02mountvirtfs ->
../init.d/mountvirtfs
I have no /dev/shm entry in /etc/fstab and /dev/shm looks like this:
eric@audiobox:~$ ls -la /dev/shm/
total 24
drwxrwxrwt 4 root root 80 Aug 28 17:56 .
drwxr-xr-x 14 root root 24576 Aug 28 17:52 ..
drwx------ 3 eric eric 60 Aug 28 17:56 jack-1000
drwxr-xr-x 2 root root 60 Aug 28 17:50 network
I don't have an etch system handy to check, but would expect it to be
the same there.
Yes, this is the right behaviour in etch and sid too. Now I have
understanded that my problem is related to the fact that mountvirtfs
doesn't mount shm and devpts when it is called on boot. I don't know
why, I'm investigating this. However if I manually stop the service
mountvirtfs and start it again shm and devpts are mounted and with the
right permissions.
I'll report any news on this.
Thanks to all have answered, you were all very helpful ;-).
Best Regards,
~ Antonio
1:17 p.m.
On Fri, 2005-09-30 at 15:28 +0200, Antonio wrote:
[cut]
Now I have
understanded that my problem is related to the fact
that mountvirtfs
doesn't mount shm and devpts when it is called on boot. I don't know
why, I'm investigating this. However if I manually stop the service
mountvirtfs and start it again shm and devpts are mounted and with the
right permissions.
I'll report any news on this.
Well, I've solved the problem!
I've learn a lot of new thinks too! The dir /dev/shm is one of the few
in /dev non managed by udev. The mountvirtfs init script have to be
called before udev because udev needs procfs, that is mounted by
mountvirtfs. I've noted that disabling udev at boot the /dev/shm
permissions were right, so mountvirtfs was doing his job. It was udev
called after that broke the things. Reinstalling udev (and to be sure
sys-rc and initscript) solved the problem.
A sincere thanks to all the guys have helped me :-).
Best Regards,
~ Antonio
1:37 p.m.
On Fri, 2005-09-30 at 17:17 +0200, Antonio wrote:
Reinstalling udev (and to be sure
sys-rc and initscript) solved the problem.
I think I've found the exact cause of the problem. There are two calls
to mountvirtfs in the S runlevel. I think that some time ago I deleted
the second one, thinking that wasn't necessary, lol! Sorry, my error.
Best Regards,
~ Antonio
29 Sep
29 Sep
11:53 a.m.
On 9/29/05, Peder Hedlund <peder(a)musikhuset.org> wrote:
If you have that you shouldn't have to have any entry in fstab;
the kernel automounts /dev/shm with 1777 permissions.
I've read that having fstab mount /dev/shm after the kernel has mounted
it might cause xruns.
The fstab entry, I think, is only for 2.4 kernels.
- Peder
This information doesn't reflect how things appear to work here. It
may be distro dependent.
- Mark
1:43 p.m.
On Thursday 29 Sep 2005 2:53 pm, Mark Knecht wrote:
On 9/29/05, Peder Hedlund <peder(a)musikhuset.org>
wrote:
Hi. Just having read the post, I booted up Debian Sarge/Etch with the
2.4.27-2-386 kernel and that /etc/fstab entry still isn't there, and yet
everything works ok, apart from realtime. Interesting also, is that in
qjackctl jacks starts with the 2.4 kernel with the jackd command, and yet in
FC1 which uses the 2.4 kernel it's necessary to change this to jackstart. I
sympathise with anyone having permissions problems, having suffered them
myself. Sometimes even convincing myself that it's a permissions problem
,then finding out that permissions have nothing to do with the problem.
Probably some sort of paranoia that the machine won't let you do want you
want it to do. Don't give up. Nigel.
If you have that you shouldn't have to have
any entry in fstab;
the kernel automounts /dev/shm with 1777 permissions.
I've read that having fstab mount /dev/shm after the kernel has mounted
it might cause xruns.
The fstab entry, I think, is only for 2.4 kernels.
- Peder
This information doesn't reflect how things appear to work here. It
may be distro dependent.
- Mark
7022
days inactive
7024
days old
linux-audio-user@lists.linuxaudio.org
19 comments
6 participants
participants (6)
-
Antonio -
David -
Eric Dantan Rzewnicki -
Mark Knecht -
nigel henry -
Peder Hedlund