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

Re: jackd trouble



Jan C. Nordholz wrote:
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


Looks better:

opie:/lib/modules/2.6.8_2.15.2005# modprobe snd-seq
opie:/lib/modules/2.6.8_2.15.2005# lsmod
Module                  Size  Used by
snd_seq_midi            6560  0
snd_seq_oss            30080  0
snd_seq_midi_event      6016  2 snd_seq_midi,snd_seq_oss
snd_seq                45968  5 snd_seq_midi,snd_seq_oss,snd_seq_midi_event
radeon                123684  2
pcmcia_core            51908  0
af_packet              12552  2
ide_scsi               13700  0
sg                     32672  0
scsi_mod               74560  2 ide_scsi,sg
snd_intel8x0           29320  1
snd_ac97_codec         64388  1 snd_intel8x0
snd_pcm_oss            47656  0
snd_mixer_oss          17152  2 snd_pcm_oss
snd_pcm                79880  2 snd_intel8x0,snd_pcm_oss
snd_timer              19716  2 snd_seq,snd_pcm
snd_page_alloc          8968  2 snd_intel8x0,snd_pcm
snd_mpu401_uart         5888  1 snd_intel8x0
snd_rawmidi            19236  2 snd_seq_midi,snd_mpu401_uart
snd_seq_device          6536  3 snd_seq_midi,snd_seq_oss,snd_rawmidi
snd 44772 13 snd_seq_midi,snd_seq_oss,snd_seq_midi_event,snd_seq,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore               7008  2 snd
hw_random               4500  0
ehci_hcd               38020  0
uhci_hcd               29068  0
usbcore               109540  4 ehci_hcd,uhci_hcd
intel_agp              19232  1
joydev                  8000  0
evdev                   7424  0
nls_iso8859_1           3968  1
nls_cp437               5632  1
vfat                   11264  1
fat                    38336  1 vfat
unix                   21428  454

opie:/lib/modules/2.6.8_2.15.2005# cd /dev/snd
opie:/dev/snd# ls
controlC0  pcmC0D0c  pcmC0D0p  pcmC0D1c  pcmC0D2c  pcmC0D3c  pcmC0D4p  seq  timer

$ jackd -d alsa

still gives me alot of
**** alsa_pcm: xrun of at least 2.398 msecs
**** alsa_pcm: xrun of at least 9.354 msecs
**** alsa_pcm: xrun of at least 64.750 msecs
**** alsa_pcm: xrun of at least 59.304 msecs
**** alsa_pcm: xrun of at least 4.890 msecs


$ rosegarden4

seemed to start up OK though....since I've never used it I don't know how to test
it for sound output!

and I can't seem to get my cdrom to play any music anymore to test sound that way.
The gnome-cd app just says "Drive Error".

It works fine when I boot with my 2.4.26 kernel...ide-scsi and such...

hgh.
--
Henry Hollenberg
hgh@rcwm.com



Reply to: