[Alsa-user] alsa isn't compiling with kernel 2.4.20-20.8

hello, I recently updated redhat 8 with kernel 2.4.20-19.8 to kernel 2.4.20-20.8 and tried to install alsa 0.9.4 and got the following error: [EMAIL PROTECTED] alsa-driver-0.9.4]# /sbin/modprobe snd-emu10k1 /lib/modules/2.4.20-20.8/kernel/sound/acore/snd.o: unresolved symbol schedule_work /lib/mo

Re: [Alsa-user] MIDI hell with 0.9.6

On 08/20/03 04:07:13, Clemens Ladisch wrote: Austin wrote: > 1. MIDI is dead. > I have three MIDI interfaces: an ens1371, and Evolution USB keyboard, and an > M-Audio Quattro. The Evolution and ens1371 both worked with 0.9.2 and still > do. The Quattro worked with 0.9.5. None work with 0.9.6.

Re: [Alsa-user] Sound Blaster 128 Problems

Colin Armstrong <[EMAIL PROTECTED]>: > I currently have in my box a sound blaster 128 card, which I am having > very weird problems with. Hey, I got a Sound Blaster 128 too and also couldn't make it work correctly. Is it a PCI board? What does 'lspci' shows? -- Julio Biason <[EMAIL PROTECTED]> De

Re: [Alsa-user] Saving alsamixer state

Colin Armstrong wrote: > How do I get alsamixer to save its state? "alsactl store" saves the mixer state to the file /etc/asound.state. "alsactl restore" restores it. > Every time I reboot it comes up as having the sound completely > muted. In theory, the two command above should be run by the s

[Alsa-user] Help with testing DTS A52 output?

Hi, I am having trouble with my ALSA drivers. I have an Audigy, and am trying to setup the Digital Coaxial output. I have a Klipsch Promedia 5.1 set of speakers, with the digital decoder-- so it shows me what mode the audio is in. I get sound, like from XMMS, sounds GREAT. But I cant seem to g