[linux-audio-user] jackd fails to start: cannot create shm segment /jack-shm-registry (No such file or directory)
17 Apr
2003
17 Apr
'03
9:53 p.m.
Hi all, any ideas on this one?
I have 2 soundcards configured:
sblive
rme 9652
my modules.conf looks like this:
#install rme9652 Hammerfall buffer first before memory gets fragmented
pre-install snd-hammerfall-mem
alias eth0 3c59x
probeall usb-interface usb-uhci
alias /dev/nvidia* nvidia
# ALSA native device support
alias char-major-116 snd
options snd major=116 cards_limit=3
alias snd-card-0 snd-emu10k1
alias snd-card-1 snd-rme9652
alias snd-card-2 snd-usb-audio
# OSS/Free compatibility
# SBLIVE (Card 0)
alias char-major-14 soundcore
alias sound-slot-0 snd-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
#We'll use Hammerfall (Card 1) only as an ALSA device
# USB-MIDI (Card 2)
alias sound-slot-2 snd-2
alias sound-service-2-1 snd-seq-oss
alias sound-service-2-8 snd-seq-oss
lsmod reflects that everything is loaded ok:
Module Size Used by Tainted: P
isofs 28244 1 (autoclean)
zlib_inflate 21156 0 (autoclean) [isofs]
nls_iso8859-1 3516 1 (autoclean)
snd-pcm-oss 42468 0 (autoclean)
snd-mixer-oss 14296 0 (autoclean) [snd-pcm-oss]
snd-seq-oss 30016 0 (autoclean) (unused)
snd-seq-midi 4576 0 (autoclean) (unused)
udf 92128 0 (autoclean)
sr_mod 16952 2 (autoclean)
floppy 56028 0 (autoclean)
snd-emu10k1-synth 5116 0 (unused)
snd-emux-synth 32092 0 [snd-emu10k1-synth]
snd-seq-midi-emul 6652 0 [snd-emux-synth]
snd-seq-virmidi 4556 0 [snd-emux-synth]
snd-seq-midi-event 5800 0 [snd-seq-oss snd-seq-midi
snd-seq-virmidi]
snd-seq 44560 2 [snd-seq-oss snd-seq-midi
snd-emux-synth
snd-seq-midi-emul snd-seq-virmidi snd-seq-midi-event]
snd-usb-audio 47744 0 (unused)
snd-rme9652 21164 0
snd-hammerfall-mem 2848 0 [snd-rme9652]
snd-emu10k1 71348 0 [snd-emu10k1-synth]
snd-pcm 79680 0 [snd-pcm-oss snd-usb-audio snd-rme9652
snd-emu10k1]
snd-timer 19272 0 [snd-seq snd-pcm]
snd-rawmidi 18304 0 [snd-seq-midi snd-seq-virmidi
snd-usb-audio
snd-emu10k1]
snd-page-alloc 7960 0 [snd-emu10k1 snd-pcm]
snd-util-mem 2984 0 [snd-emux-synth snd-emu10k1]
snd-ac97-codec 40416 0 [snd-emu10k1]
snd-seq-device 5740 0 [snd-seq-oss snd-seq-midi
snd-emu10k1-synth
snd-emux-synth snd-seq snd-emu10k1 snd-rawmidi]
snd-hwdep 6272 0 [snd-emu10k1]
snd 41476 0 [snd-pcm-oss snd-mixer-oss snd-seq-oss
snd-seq-midi snd-emux-synth snd-seq-virmidi snd-seq-midi-event snd-seq
snd-usb-audio snd-rme9652 snd-emu10k1 snd-pcm snd-timer snd-rawmidi
snd-util-mem snd-ac97-codec snd-seq-device snd-hwdep]
parport_pc 25320 1 (autoclean)
lp 8224 0 (autoclean)
parport 35232 1 (autoclean) [parport_pc lp]
agpgart 41248 3 (autoclean)
nvidia 1593216 10 (autoclean)
nfsd 74992 8 (autoclean)
af_packet 16872 1 (autoclean)
3c59x 29936 1 (autoclean)
supermount 74908 2 (autoclean)
ide-scsi 11440 1
scsi_mod 105556 2 [sr_mod ide-scsi]
ide-cd 33952 0
cdrom 31712 0 [sr_mod ide-cd]
usb-midi 19256 0 (unused)
soundcore 6500 0 [snd usb-midi]
usbmouse 2936 0 (unused)
keybdev 2720 0 (unused)
mousedev 5332 1
hid 21028 0 (unused)
input 5760 0 [usbmouse keybdev mousedev hid]
usb-uhci 25932 0 (unused)
usbcore 75616 1 [snd-usb-audio usb-midi usbmouse hid
usb-uhci]
rtc 8892 0 (autoclean)
ext3 62252 3
jbd 41500 3 [ext3]
my /etc/asound.conf looks like this:
pcm.sblive {
type hw
card 0
}
ctl.sblive {
type hw
card 0
}
pcm.rme9652 {
type hw
card 1
}
ctl.rme9652 {
type hw
card 1
}
When I do:
aplay -D sblive <filename>
it works just fine.
Yet, when I do
jackd -d alsa -d hw:0
or
jackd -d alsa -d sblive
or simply
jackd -d alsa
I get the following _every time_:
jackd 0.68.0
Copyright 2001-2003 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
key for /tmp/jack/shm/jack-shm-registry is 0x6a06252b
cannot create shm segment /jack-shm-registry (No such file or directory)
cannot create engine
jack main caught signal 15
I am using MDK 9.1 with low-lat kernel (otherwise vanilla), and the CVS
jack
(4/17/03). The rpm for MDK (0.66) also has the same issue.
Any help on this one is greatly appreciated! Thank you! Sincerely,
Ivica Ico Bukvic, composer & multimedia sculptor
http://meowing.ccm.uc.edu/~ico
17 Apr
17 Apr
10:12 p.m.
hi
On Thursday 17 April 2003 23:44, Ivica Bukvic wrote:
key for /tmp/jack/shm/jack-shm-registry is 0x6a06252b
cannot create shm segment /jack-shm-registry (No such file or directory)
You need to mount shmfs for jack to work. My /etc/fstab entry is like that:
shmfs /dev/shm shm defaults 0 0
To do that you need a kernel compiled with shm support.
--regards
anton
18 Apr
18 Apr
12:37 p.m.
Well, the odd thing is that I have the exactly same setup on another
machine with the same kernel rpm installed and that one has shm just
fine.
At any rate, according to Mdk there needs to be this kind of line added:
none /tmp tmpfs defaults 0 0
(supposedly tmpfs has replaced shmfs in the newer kernels)
Yet, I am not sure whether this thing has to be mounted explicitly or
what. On the other machine everything is automatic, but this one is
giving me all kinds of headaches. Should I maybe recompile the jack, now
that I've added this thingy to my fstab? What about a reboot?
Ico
-----Original Message-----
From: Antonis Galanopoulos [mailto:addon@blueyonder.co.uk]
Sent: Thursday, April 17, 2003 9:10 PM
To: linux-audio-user(a)music.columbia.edu
Cc: ico(a)fuse.net
Subject: Re: [linux-audio-user] jackd fails to start: cannot create
shm
segment /jack-shm-registry (No such file or
directory)
hi
On Thursday 17 April 2003 23:44, Ivica Bukvic wrote:
> key for /tmp/jack/shm/jack-shm-registry is 0x6a06252b
> cannot create shm segment /jack-shm-registry (No such file or
directory)
You need to mount shmfs for jack to work. My /etc/fstab entry is like
that:
shmfs /dev/shm shm defaults
0
0
To do that you need a kernel compiled with shm support.
--regards
anton
2:20 p.m.
"Ivica Bukvic" <ico(a)fuse.net> writes:
Well, the odd thing is that I have the exactly same
setup on another
machine with the same kernel rpm installed and that one has shm just
fine.
At any rate, according to Mdk there needs to be this kind of line added:
none /tmp tmpfs defaults 0 0
I think your problem is that, for JACK, the mount point should be
/dev/shm. You can use tmpfs for the /tmp file system if you want, but
that does not satisfy JACK's requirement for POSIX openshm support.
(supposedly tmpfs has replaced shmfs in the newer
kernels)
Yes.
Yet, I am not sure whether this thing has to be
mounted explicitly or
what. On the other machine everything is automatic, but this one is
giving me all kinds of headaches. Should I maybe recompile the jack, now
that I've added this thingy to my fstab? What about a reboot?
It does have to be mounted explicitly the first time. If you set up
/etc/fstab correctly, it will be remounted whenever you reboot.
--
Jack O'Quin
Austin, Texas, USA
2:53 p.m.
Well, the odd thing is that I have the exactly
same setup on another
machine with the same kernel rpm installed and that one has shm just
fine.
At any rate, according to Mdk there needs to be this kind of line added:
none /tmp tmpfs defaults 0 0
I think your problem is that, for JACK, the mount point should be
/dev/shm. You can use tmpfs for the /tmp file system if you want, but
that does not satisfy JACK's requirement for POSIX openshm support.
4:44 p.m.
"Mark Knecht" <mknecht(a)controlnet.com> writes:
Jack,
I found (in my Redhat case) that there is support for something that
'replaces' the shm file system in the kernel I built this morning, but when
I went to mount it I found that /dev/shm doesn't exist. I know from my 1394
work that these things have to be created correctly, but I do not know how
to do it. Do you know of any documentation on the right way to get this
created? I admit I have not searched the Jack archives yet.
Mount points are ordinary directories. To create it (as root)...
# mkdir /dev/shm
Most things in /dev are device special files, created with mknod (or
MAKEDEV). But, this is just a mount point. It's odd that the POSIX
shm implementors put it in that directory, but there it is.
What value does this provide, by the way? Jack
seemed to be working just
fine for me up to now.
Paul changed from System V shared memory to the POSIX shm interface.
System V had a bad habit of leaving garbage segments around after
applications terminate. POSIX shm is cleaner, and is also available
on Apple OS X.
I don't think Paul initially realized that most Linux systems are not
configured out of the box for this to work. Who would have thunk it?
This problem only arises with CVS versions of JACK. At one point,
Paul said he was considering changing JACK to support both, with
automatic configuration at build time. I don't know what the status
of that is, or even whether I think it's a good idea.
At this point, it seems like mostly a big documentation problem.
Regards,
--
Jack O'Quin
Austin, Texas, USA
5:09 p.m.
Hmm., I guess I was rejoicing prematurely...
I added /dev/shm into fstab:
none /dev/shm tmpfs defaults 0 0
recompiled CVS jack (configure finds shm stuff ok)
started jack and the same thingy happens:
jackd -d alsa -d hw:0
jackd 0.68.0
Copyright 2001-2003 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
key for /tmp/jack/shm/jack-shm-registry is 0x6a0bdb99
cannot create shm segment /jack-shm-registry (No such file or directory)
cannot create engine
I guess I am back to square one.
In addition, I forgot to mention one important issue with my other
machine (where Jack works), and that is that it was updated from mdk9.0,
while this one was a clean install. After two clean installs on two
different machines, I noticed that neither had the shm entry in fstab,
which obviously nullifies the possibility that it was a faulty install
in the first place.
Again, any help is greatly appreciated! Sincerely,
Ico
5:51 p.m.
"Ivica Bukvic" <ico(a)fuse.net> writes:
Hmm., I guess I was rejoicing prematurely...
I added /dev/shm into fstab:
none /dev/shm tmpfs defaults 0 0
recompiled CVS jack (configure finds shm stuff ok)
started jack and the same thingy happens:
jackd -d alsa -d hw:0
jackd 0.68.0
Copyright 2001-2003 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
key for /tmp/jack/shm/jack-shm-registry is 0x6a0bdb99
cannot create shm segment /jack-shm-registry (No such file or directory)
cannot create engine
I guess I am back to square one.
In addition, I forgot to mention one important issue with my other
machine (where Jack works), and that is that it was updated from mdk9.0,
while this one was a clean install. After two clean installs on two
different machines, I noticed that neither had the shm entry in fstab,
which obviously nullifies the possibility that it was a faulty install
in the first place.
Apparently, the POSIX shared memory implementation is not a standard
part of most Linux distributions. That's a shame.
Again, any help is greatly appreciated! Sincerely,
Does the directory /dev/shm exist? If not, "mkdir /dev/shm" (as root).
Then mount /dev/shm, and try starting jackd again.
What does "grep shm /etc/fstab" say?
Sorry this is such a hassle.
--
Jack O'Quin
Austin, Texas, USA
6:20 p.m.
/dev/shm exists right after install, but there is no entry in the
/etc/fstab.
The funny thing about the /dev/shm dir is that you cannot remove or
modify even as root. It's default creation date is Dec.31 1969 until it
gets mounted, at which point it converts itself to the appropriate date.
I had to manually add the below included line to fstab:
none /dev/shm tmpfs defaults 0 0
and had to mount it manually in order for the jack's ./configure to
report that it has successfully found POSIX memory sharing. Yet, the
error persists when the newly compiled jackd is started:
key for /tmp/jack/shm/jack-shm-registry is 0x6a0bdb99
cannot create shm segment /jack-shm-registry (No such file or directory)
cannot create engine
Should I simply revert to the older version of Jack until this stuff is
sorted out?
BTW, configure does revert to the other style of shared memory stuff
(System V shm) if it does not find POSIX one, but even if I compile that
one, I still end up with the same error/results.
Thanks for your help!
Ico
root).
-----Original Message-----
From: linux-audio-user-admin(a)music.columbia.edu
[mailto:linux-audio-user-
admin(a)music.columbia.edu] On Behalf Of Jack
O'Quin
Sent: Friday, April 18, 2003 3:42 PM
To: linux-audio-user(a)music.columbia.edu
Subject: Re: [linux-audio-user] jackd fails to start: cannot create
shm
segment /jack-shm-registry (No such file or
directory)
"Ivica Bukvic" <ico(a)fuse.net> writes:
> Hmm., I guess I was rejoicing prematurely...
>
> I added /dev/shm into fstab:
>
> none /dev/shm tmpfs defaults 0 0
>
> recompiled CVS jack (configure finds shm stuff ok)
>
> started jack and the same thingy happens:
>
> jackd -d alsa -d hw:0
> jackd 0.68.0
> Copyright 2001-2003 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
>
> key for /tmp/jack/shm/jack-shm-registry is 0x6a0bdb99
> cannot create shm segment /jack-shm-registry (No such file or
directory)
> cannot create engine
>
> I guess I am back to square one.
>
> In addition, I forgot to mention one important issue with my other
> machine (where Jack works), and that is that it was updated from
mdk9.0,
> while this one was a clean install. After two
clean installs on two
> different machines, I noticed that neither had the shm entry in
fstab,
> which obviously nullifies the possibility that it
was a faulty
install
in the first
place.
Apparently, the POSIX shared memory implementation is not a standard
part of most Linux distributions. That's a shame.
Again, any help is greatly appreciated!
Sincerely,
Does the directory /dev/shm exist? If not, "mkdir /dev/shm" (as Then mount /dev/shm, and try starting jackd again.
What does "grep shm /etc/fstab" say?
Sorry this is such a hassle.
--
Jack O'Quin
Austin, Texas, USA
9:25 p.m.
This is beyond me. Are you running devfs by any chance?
I'm copying this message to the jackit-devel list. Maybe someone
there knows what this problem is.
"Ivica Bukvic" <ico(a)fuse.net> writes:
/dev/shm exists right after install, but there is no
entry in the
/etc/fstab.
The funny thing about the /dev/shm dir is that you cannot remove or
modify even as root. It's default creation date is Dec.31 1969 until it
gets mounted, at which point it converts itself to the appropriate date.
I had to manually add the below included line to fstab:
none /dev/shm tmpfs defaults 0 0
and had to mount it manually in order for the jack's ./configure to
report that it has successfully found POSIX memory sharing. Yet, the
error persists when the newly compiled jackd is started:
key for /tmp/jack/shm/jack-shm-registry is 0x6a0bdb99
cannot create shm segment /jack-shm-registry (No such file or directory)
cannot create engine
Should I simply revert to the older version of Jack until this stuff is
sorted out?
BTW, configure does revert to the other style of shared memory stuff
(System V shm) if it does not find POSIX one, but even if I compile that
one, I still end up with the same error/results.
Thanks for your help!
Ico
root).
> Then mount /dev/shm, and try starting jackd again.
>
> What does "grep shm /etc/fstab" say?
>
> Sorry this is such a hassle.
--
Jack O'Quin
Austin, Texas, USA
-----Original Message-----
From: linux-audio-user-admin(a)music.columbia.edu
[mailto:linux-audio-user-
admin(a)music.columbia.edu] On Behalf Of Jack
O'Quin
Sent: Friday, April 18, 2003 3:42 PM
To: linux-audio-user(a)music.columbia.edu
Subject: Re: [linux-audio-user] jackd fails to start: cannot create
shm
segment /jack-shm-registry (No such file or
directory)
"Ivica Bukvic" <ico(a)fuse.net> writes:
> Hmm., I guess I was rejoicing prematurely...
>
> I added /dev/shm into fstab:
>
> none /dev/shm tmpfs defaults 0 0
>
> recompiled CVS jack (configure finds shm stuff ok)
>
> started jack and the same thingy happens:
>
> jackd -d alsa -d hw:0
> jackd 0.68.0
> Copyright 2001-2003 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
>
> key for /tmp/jack/shm/jack-shm-registry is 0x6a0bdb99
> cannot create shm segment /jack-shm-registry (No such file or
directory)
> cannot create engine
>
> I guess I am back to square one.
>
> In addition, I forgot to mention one important issue with my other
> machine (where Jack works), and that is that it was updated from
mdk9.0,
> while this one was a clean install. After
two clean installs on two
> different machines, I noticed that neither had the shm entry in
fstab,
> which obviously nullifies the possibility
that it was a faulty
install
in the
first place.
Apparently, the POSIX shared memory implementation is not a standard
part of most Linux distributions. That's a shame.
Again, any help is greatly appreciated!
Sincerely,
Does the directory /dev/shm exist? If not, "mkdir /dev/shm" (as
19 Apr
19 Apr
12:04 a.m.
Actually, Thac just released a new rpm of jackit (0.67.2) on his rpm
repository that magically fixes this issue. Yet, the CVS version simply
fails to work. Perhaps there is some bug in my CVS checkout, since it is
looking for /jack-shm-registry (which may imply it is looking for it in
the root dir? -- this would obviously be a bug).
Thanks for all your help!
Ico
--
Jack O'Quin
Austin, Texas, USA
-----Original Message-----
From: linux-audio-user-admin(a)music.columbia.edu
[mailto:linux-audio-user-
admin(a)music.columbia.edu] On Behalf Of Jack
O'Quin
Sent: Friday, April 18, 2003 7:16 PM
To: linux-audio-user(a)music.columbia.edu
Cc: jackit-devel(a)lists.sourceforge.net
Subject: Re: [linux-audio-user] jackd fails to start: cannot create
shm
segment /jack-shm-registry (No such file or
directory)
This is beyond me. Are you running devfs by any chance?
I'm copying this message to the jackit-devel list. Maybe someone
there knows what this problem is.
"Ivica Bukvic" <ico(a)fuse.net> writes:
> /dev/shm exists right after install, but there is no entry in the
> /etc/fstab.
>
> The funny thing about the /dev/shm dir is that you cannot remove or
> modify even as root. It's default creation date is Dec.31 1969 until
it
> gets mounted, at which point it converts itself
to the appropriate
date.
>
> I had to manually add the below included line to fstab:
>
> none /dev/shm tmpfs defaults 0 0
>
> and had to mount it manually in order for the jack's ./configure to
> report that it has successfully found POSIX memory sharing. Yet, the
> error persists when the newly compiled jackd is started:
>
> key for /tmp/jack/shm/jack-shm-registry is 0x6a0bdb99
> cannot create shm segment /jack-shm-registry (No such file or
directory)
> cannot create engine
>
> Should I simply revert to the older version of Jack until this stuff
is
> sorted out?
>
> BTW, configure does revert to the other style of shared memory stuff
> (System V shm) if it does not find POSIX one, but even if I compile
that
> one, I still end up with the same error/results.
>
> Thanks for your help!
>
> Ico
>
>
> > -----Original Message-----
> > From: linux-audio-user-admin(a)music.columbia.edu
> [mailto:linux-audio-user-
> > admin(a)music.columbia.edu] On Behalf Of Jack O'Quin
> > Sent: Friday, April 18, 2003 3:42 PM
> > To: linux-audio-user(a)music.columbia.edu
> > Subject: Re: [linux-audio-user] jackd fails to start: cannot
create
> shm
> > segment /jack-shm-registry (No such file or directory)
> >
> > "Ivica Bukvic" <ico(a)fuse.net> writes:
> >
> > > Hmm., I guess I was rejoicing prematurely...
> > >
> > > I added /dev/shm into fstab:
> > >
> > > none /dev/shm tmpfs defaults 0 0
> > >
> > > recompiled CVS jack (configure finds shm stuff ok)
> > >
> > > started jack and the same thingy happens:
> > >
> > > jackd -d alsa -d hw:0
> > > jackd 0.68.0
> > > Copyright 2001-2003 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
> > >
> > > key for /tmp/jack/shm/jack-shm-registry is 0x6a0bdb99
> > > cannot create shm segment /jack-shm-registry (No such file or
> directory)
> > > cannot create engine
> > >
> > > I guess I am back to square one.
> > >
> > > In addition, I forgot to mention one important issue with my
other
> > > machine (where Jack works), and that is
that it was updated from
> mdk9.0,
> > > while this one was a clean install. After two clean installs on
two
> > > different machines, I noticed that
neither had the shm entry in
> fstab,
> > > which obviously nullifies the possibility that it was a faulty
> install
> > > in the first place.
> >
> > Apparently, the POSIX shared memory implementation is not a
standard
part of most Linux distributions. That's a
shame.
root).
> Then mount /dev/shm, and try starting jackd again.
>
> What does "grep shm /etc/fstab" say?
>
> Sorry this is such a hassle. Again, any help is greatly appreciated!
Sincerely,
Does the directory /dev/shm exist? If not, "mkdir /dev/shm" (as
7731
days inactive
7732
days old
linux-audio-user@lists.linuxaudio.org
11 comments
4 participants
participants (4)
-
Antonis Galanopoulos -
Ivica Bukvic -
Jack O'Quin -
Mark Knecht