[PlanetCCRMA] Alsa-Jack config on Fedora 4
Bob Bailey
bob at digisonus.com
Fri Sep 30 22:48:00 PDT 2005
Thanks Fernando. I think I determined that I didn't need to run
alsaconf, but only after I'd run it. Can I then delete the alsaconf
generated section and replace with your suggestion from below?
by the way, here is /proc/asound/cards and /proc/devices:
[root at daw bbailey]# cat /proc/asound/cards
0 [M410 ]: ICE1712 - M Audio Delta 410
M Audio Delta 410 at 0xd000, irq 10
[root at daw bbailey]# cat /proc/devices
Character devices:
1 mem
4 /dev/vc/0
4 tty
4 ttyS
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
14 sound
29 fb
116 alsa
128 ptm
136 pts
180 usb
226 drm
Block devices:
1 ramdisk
2 fd
3 ide0
9 md
22 ide1
253 device-mapper
254 mdp
looks like ALSA is there.
When I start envy24control, it starts to initiate, but quickly closes.
hmmm. here is the output:
[root at daw bbailey]# envy24control
using --- input_channels: 2
--- output_channels: 8
--- pcm_output_channels: 8
--- spdif in/out channels: 2
Segmentation fault
started jackd and got this.... looks like it is up. Is there a reason
it wouldn't start with qjackctl?
[root at daw bbailey]# jackd -R -d alsa -d hw
jackd 0.100.1
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 ..
creating alsa driver ... hw|hw|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
Bob
Fernando Lopez-Lezcano wrote:
>On Fri, 2005-09-30 at 10:32 -0700, Bob Bailey wrote:
>
>
>>I may have over estimated my abilities in venturing to Fedora4 without
>>more documentation available. I have had success with Fedora2, but it
>>seems that there may have been some changes in the version 4 that are
>>keeping me from a successful install. I've not installed ardour or any
>>of the other apps I will use, but am just trying to get the audio
>>working well with xmms and perhaps realaudio streams.
>>
>>when I try to open an ogg/mp3/wav file, I get an xmms error:
>>Couldn't open audio. Please check that your soundcard is configured
>>properly, you have the correct output plugin selected, and that no other
>>program is blocking the soundcard.
>>
>>I have the alsa 1.2.10 output plugin selected (libALSA.so) and
>>modprobe.conf:
>>
>>alias eth0 e100
>>alias snd-card-0 snd-ice1712
>>alias usb-controller uhci-hcd
>># --- BEGIN: Generated by ALSACONF, do not edit. ---
>># --- ALSACONF version 1.0.9 ---
>># --- END: Generated by ALSACONF, do not edit. ---
>>
>>
>
>You should not have neede to run alsaconf on fc4, it should have found
>your card automatically...
>
>
>
>># -- Keep modules from being autocleaned
>>#add options -k snd-card-0
>>alias net-pf-10 off
>>alias ipv6 off
>>
>>by the way, I get errors when I uncomment these 'autoclean' options
>>
>>
>
>Try with this for the soundcard options:
>
>alias snd-card-0 snd-ice1712
>options snd-card-0 index=0
>options snd-ice1712 index=0
>
>That should be all you need.
>
>
>
>>In previous installs, I had to start up jack first. When I attemt to do
>>this now, I get this error from qjackctl:
>>
>>creating alsa driver ... /dev/dsp|-|1024|2|44100|0|2|nomon|swmeter|-|32bit
>>ALSA lib control.c:817:(snd_ctl_open_noupdate) Invalid CTL /dev/dsp
>>control open "/dev/dsp" (No such file or directory)
>>cannot load driver module alsa
>>09:27:01.025 JACK was stopped successfully.
>>09:27:02.818 Could not connect to JACK server as client.
>>
>>
>
>This is all very strange.
>What do you have in:
> cat /proc/asound/cards
> cat /proc/asound/devices
>If you don't have anything there then alsa is not started.
>
>If you appear to have things there try starting "envy24control" to make
>sure it can see your card.
>
>Then start (from the command line first) jack:
>
> jackd -R -d alsa -d hw
>
>-- Fernando
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/planetccrma/attachments/20050930/5aa0e00d/attachment.html>
More information about the PlanetCCRMA
mailing list