Re: [Alsa-user] Ongoing ALSA troubles

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

I've had a bit more success, I downloaded alsaconf having seen its now >0.9=
=20
(did it not lag at v0.5 for ages, or is that just Debian's packaging?) and=
=20
ran alsaconf which did the trick; I always thought that was optional, it=20
certainly wasn't a package that was depended on by the other packages (I ha=
d=20
installed alsa-lib btw :-)=20

So now after a couple of reboots it seems fine, in that apps I've bothered =
to=20
configure can make sound now.

As always, solving one problem leads to more problems, and my new problems=
=20
aren't strictly regards ALSA:

(i) KDE says :

Sound server warning message:
Can't set real-time scheduling priority.
You need to run artswrapper as root or
setuid root. This means that you will
likely not be able to produce acceptable
sound (i.e. without clicks and breaks).

(ii) Can't get Rosegarden or any sequencer's that are in Demudi as they wan=
t=20
KDE2 and I have 3.1 :-(

Anyway thx all 4 help,=20
not sure if your extigy's problem's as easy to solve as using alsa-conf Chr=
is?

On Monday 28 Apr 2003 1:32 pm, christopher cuse wrote:
> hi oli,
>
> could you try;
>
> #amixer contents
>
> and see what you get -- i have extigy and less or more the same problem
> that you are having.
>
> the output from this command results in a page of info, and contains:
>
> numid=3D23,iface=3DMIXER,name=3D'Digital In Playback Source',index=3D1
>   ; type=3DENUMERATED,access=3Drw---,values=3D1,items=3D2
>   ; Item #0 'Mixer'
>   ; Item #1 'PCM'
> amixer: Control default element read error: Invalid argument
>
> although i have no idea what it means ....
>
> cheers
>
> christopher cuse
>
> On Mon, 2003-04-28 at 14:03, linux power wrote:
> > You must run ./snddevices while in drriver dir.
> > Also you must install the alsa-lib package
> >  OliWilson <ma...@ol...> wrote:Please help!
> >
> > I have been going round in circles trying to sort out ALSA on a machine
> > I'm rebuilding ground up. The distro is a mix of Debian testing and
> > Demudi.
> >
> > I have installed the following packages:
> >
> > alsa-base-0.9.0rc3-0.2
> > alsa-modules-2.4.18-586-demudi
> > alsa-utils-0.9.0rc3-0.2
> >
> > from http://http.demudi.org/debian/
> >
> > ------
> >
> > Here is cat /proc/modules:
> >
> > *snip*
> > snd-emu10k1-synth 3648 0 (unused)
> > snd-emux-synth 23324 0 [snd-emu10k1-synth]
> > snd-seq-midi-emul 4448 0 [snd-emux-synth]
> > snd-seq-virmidi 2600 0 [snd-emux-synth]
> > snd-seq-midi-event 3000 0 [snd-seq-virmidi]
> > snd-seq 33548 0 [snd-emux-synth snd-seq-midi-emul
> > snd-seq-virmidi snd-seq-midi-event]
> > snd-emu10k1 56548 0 [snd-emu10k1-synth]
> > snd-pcm 53216 0 [snd-emu10k1]
> > snd-timer 9280 0 [snd-seq snd-pcm]
> > snd-rawmidi 11520 0 [snd-seq-virmidi snd-emu10k1]
> > snd-util-mem 1168 0 [snd-emux-synth snd-emu10k1]
> > snd-hwdep 3392 0 [snd-emu10k1]
> > snd-ac97-codec 24784 0 [snd-emu10k1]
> > snd-seq-device 3648 0 [snd-emu10k1-synth snd-emux-synth snd-seq
> > snd-emu10k1 snd-rawmidi]
> > snd 23144 0 [snd-mixer-oss snd-emux-synth snd-seq-virmidi
> > snd-seq-midi-event snd-seq snd-emu10k1 snd-pcm snd-timer snd-rawmidi
> > snd-util-mem snd-hwdep snd-ac97-codec snd-seq-device]
> > soundcore 3460 5 [snd]
> > *snip*
> >
> > ------
> >
> > Here is cat /proc/asound/cards:
> >
> > 0 [card0 ]: Audigy - Sound Blaster Audigy
> > Sound Blaster Audigy at 0xe000, irq 5
> >
> > ------
> >
> > Now if I try to run any program using alsa, I get:
> >
> > oliwilson@angelcake:~$ amixer
> > amixer: Mixer attach default error: No such file or directory
> >
> > oliwilson@angelcake:~$ alsamixer
> > alsamixer: function snd_ctl_open failed for default: No such file or
> > directory
> >
> > ------
> >
> > If I run:
> > angelcake:/home/oliwilson#
> > /usr/share/doc/alsa-modules-2.4.18-586-demudi/examples/snddevices
> >
> > Creating /dev/mixer?... done
> > Creating /dev/sequencer... done
> > *etc*
> > ALSA dynamic sound device filesystem
> > create symbolic link `/dev/snd' to `/proc/asound/dev'
> > ALSA loader devices
> > Creating /dev/aload?... done
> > Creating /dev/aloadSEQ... done
> >
> > Then, programs such as alsamixer work.
> >
> > However, the next time I reboot, whatever snddevices script did is eras=
ed
> > and I must run it again to put stuff in /dev ! Why can't I make any
> > permanent changes to the contents of /dev? I can if I say something like
> > "ln -s /dev/sr0 /dev/cdrom", what's different here?
> >
> > KDE 3.1.1a does not recognise the alsa drivers at all for it's arts
> > server, nor the emulated OSS drivers.
> >
> > I am yet to hear a sound and obviously missed something crucial, what is
> > the 'missing step' in installing the drivers?
> >
> > Yes, I do unmute the channels when I can get the mixer up, oh and I did
> > add root + user to the audio group.
> >
> > I've scoured FAQs etc but I'm totally stumped,
> >
> > Please help!
> >
> > OliWilson
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Alsa-user mailing list
> > Als...@li...
> > https://lists.sourceforge.net/lists/listinfo/alsa-user
> >
> > http://home.no.net/~knutove/knut_ove_hauge_kuren.htm
> > Ny versjon av Yahoo! Messenger
> > Nye ikoner og bakgrunner, webkamera med superkvalitet og dobbelt s=E5
> > morsom
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Alsa-user mailing list
> Als...@li...
> https://lists.sourceforge.net/lists/listinfo/alsa-user