[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: jackd trouble



On Tue, Feb 15, 2005 at 05:36:20PM -0600, Henry Hollenberg wrote:
> Jan C. Nordholz wrote:
> >On Tue, Feb 15, 2005 at 05:09:24PM -0600, Henry Hollenberg wrote:
> >
> >>>crw-rw----  1 root audio 116, 1 2003-05-30 21:57 /dev/snd/seq
> >>
> >>hgh@opie:/dev/snd$ ls -l
> >>total 0
> >>crw-rw----  1 root audio 116,  0 Feb 15 16:04 controlC0
> >>crw-rw----  1 root audio 116, 24 Feb 15 16:04 pcmC0D0c
> >>crw-rw----  1 root audio 116, 16 Feb 15 16:04 pcmC0D0p
> >>crw-rw----  1 root audio 116, 25 Feb 15 16:04 pcmC0D1c
> >>crw-rw----  1 root audio 116, 26 Feb 15 16:04 pcmC0D2c
> >>crw-rw----  1 root audio 116, 27 Feb 15 16:04 pcmC0D3c
> >>crw-rw----  1 root audio 116, 20 Feb 15 16:04 pcmC0D4p
> >>crw-rw----  1 root audio 116, 33 Feb 15 16:04 timer
> >
> >Ok, devfs / udev seems to have created all device nodes whose appropriate
> >modules are loaded... so a module has to be missing...
> 
> should I pass one of these devices to jackd????  somehow???
Hmm no, the sequencer relies on /dev/snd/seq, which in turn is
automatically created by devfs/udev as soon as the kernel support
for it is enabled (at boot-time if compiled in, upon module loading
if compiled as module).

>>>devfsd  udev
>>Both?
> talk to the debian testing guys, I don't recall
> specifically setting up either one of those....at
> least not on purpose.  I guess if a kernel compile
> switch can trigger their existance then I may have
> hit y/m one time to many....
Both are separate debian packages that have to be installed
additionally (udev and devfsd are the package names) to
enabling the support in the kernel.
I hope both systems don't get in each other's way...
you could try to remove one of them (either deinstalling
the package, or simply moving the symlinks to the init script
out of the way, like 'update-rc.d -f devfsd remove').

> # Sound
> #
> CONFIG_SOUND=m
> 
> #
> # Advanced Linux Sound Architecture
> #
> CONFIG_SND=m
> CONFIG_SND_TIMER=m
> CONFIG_SND_PCM=m
> CONFIG_SND_RAWMIDI=m
> CONFIG_SND_SEQUENCER=m
> CONFIG_SND_SEQ_DUMMY=m
> CONFIG_SND_OSSEMUL=y
> CONFIG_SND_MIXER_OSS=m
> CONFIG_SND_PCM_OSS=m
> CONFIG_SND_SEQUENCER_OSS=y
> CONFIG_SND_RTCTIMER=m
> # CONFIG_SND_VERBOSE_PRINTK is not set
> # CONFIG_SND_DEBUG is not set
Hmm, looks perfectly fine...

> Sorry about so much stuff!
> hgh.
Was exactly what I requested. ;)

Hm, could you tell me if there is a "snd_seq" module in your
module tree? (find /lib/modules/2.6.8 -name "snd_seq*") If so,
try to manually load it (insmod or modprobe), and check if the
seq device node is created or the situation improves otherwise...

Jan

-- 
Jan C. Nordholz
<jckn At gmx net>

Attachment: signature.asc
Description: Digital signature


Reply to: