Well I'd love to hear an answer to this one as well

After getting tired of waiting for linuxant to port their Riptide drivers to the 2.6 kernel I went to the sound card list on the Alsa website and ordered an Aureal 8810 chipset sound card from Ebay.

Of course now I'm in the same boat as everyone else here....modules load fine, I can adjust the volume (aumix, alsamixer you name it) but I get no sound at all! I've tried turning off PNP in the BIOS and the "setpci" trick mentioned above. Still no sound.

Anyone have a fix / workaround yet?

I took the easy way out, I bought another sound card (that used kernel's built-in drivers) . I tried to fix this card for 15-20 days but could not, I did not have time to try further.

People at OpenVortex ( https://savannah.nongnu.org/projects/openvortex/ ) responded very well, you could try posting your problem there.

--LC

FYI: The above reply was from me. --Linchip.

Bummer....I bought this Aureal card for that exact reason (to replace the Riptide that wasn't working)....oh well I'll keep an eye on this thread incase any one else chimes in.

From the research I've done, it almost seems as if this card used to work but a patch was added to the 2.6 tree and it broke it. I'm hoping one of the up and coming kernels will fix it (i.e. 2.6.6 or 2.6.7 etc).

is all audio not working? I discovered audio cd's would'nt play.. Because of windows I no longer install the audio cables from the cdroms to soundcards. I put one in and now I get sound from my cd's try it and see. Keith

Unfortunately I don't think my cheap card has a spot for the cdrom cables.....I thought those cables were only for listening to sound via the headphone out on the front of the cdroms. In other words, sound is sent from the cdrom to the sound card and then it goes to both 1. sound card output and 2. sound card cable back to the cdrom to the headphone jack.

In either case I don't think my card has a spot anyway....I can take a looksy but not tonight (gotta get up early for mountain biking :-)

p.s. I did find a patch for 2.6.4 (the openvortex link above) but I haven't applied / tested it yet.

Yes, I'm of course experiencing the same problems with my aureal 8810.

Could it be that all of you that has this problem (<3>bad adb fifo reset!) has some kind of nvidia graphics card?
I do have one, and in the readme for au88x0 sound drivers they have several notes on this (though none of them made it work unfortunately).

I don't think this will solve the problem, but it would be interesting.

I have an ATI card....although I think my mobo has a built in NVidia but it's not being used (even the "hwbrowser" doesn't show it nor does "/sbin/lspci -v").

Still haven't gotten around to trying the patch unfortunately (or looking at the card to see if it has a spot for the cdrom cables). I guess I've been without sound for so long that it doesn't bother me as much anymore *shrug*

Yeah, I am also using a nVidia card (TNT2) with the Aureal card.

I've got it!!!

If you still read this...

there's a patch which you have to use, availible here http://galadriel.mat.utfsm.cl/~mjand...-2.6.6.diff.gz

First i downloaded the 2.6.6 kernel, then i added the patch, after that: make menuconfig and so on!
Alsa is fantastic, this is the first time i hear sound in linux!

/j.

Hmm...I was REALLY excited when I read your response, but I tried the patch for 2.6.6 and it didn't work for me (received the same IRQ error in dmesg).

Maybe they'll have a 2.6.7 patch that will work for me when 2.6.7 is out :-)

I just finished installing Suse 9.1 and came across the same issue. Sound was not coming out of the card (monster sound mx300/au8830a2) initially until I found in kmix, that there's a little button labelled "advanced", after clicking on it, several radio buttons came up labelled 3d control, mix, external amplifier, eq enable, etc. Well, the button labelled "internal amplifier" which is initially set to "on" by default is the one that I needed to change for sound to come up, basically by setting it to "off". You can also use the ALSA mixer and if you scroll all the way to your right, you will see the entry for external amplifier. The setting should be "off" and oh, your speakers need to be connected to the "Out 1" for cd sound since the "Out 2" does nothing.
I also get the "vortex: irq fifo" error and in looking at my w2k device setup, there is an extra device labelled "Vortex Multifunction parent" which apparently uses the same irq as the sound card and maybe that is what causes the error in linux since the sound drivers probably do not address the extra device (or whatever it is)...of course that's my guess.
My problem now is that I can play .wavs .mp3s for a short while until something that uses the sound "throws it off" and therefore whatever I play after that sounds like it's on a 78 rpm turntable and therefore my only solution is to reboot. That is what I'm trying to figure out and fix since it annoying to be rebooting for sound. Any info would be helpful.

ErickC

Hi all!

Would just like to put this comment in here, in case anyone had the same, simple solution to this problem that I had.

Just went from Slackware 9.1 to 10.0 and had the experience of a soundless system immediately afterwards. Little did I notice that the faders in Kmix/Alsa had changed to include the EQ.......so when I adjusted the eq-faders, all sound was present.....erhrm....don't exactly feel like a bundle of braincells writing this, but I used quite some time reading other peoples posts, etc. before i figured this out...not that it will help you guys with irq and driver issues, but since noone else mentioned it, I can be the village idiot....

Fluxien

Upgraded from Fedora Core 1 to Core 2 on a Fujitsu notebook. The adventure is documented at http://www.constitution.org/comp/xeta-fc2.htm . The problem is that all sound settings, kmix, alsa, and aumix, are reset to zero and mute on bootup, despite using the control center option of saving the sound settings. Under Core 1 that was not a problem. Hitting the supposed "saved" settings works on aumix, but not for kmix or alsamixer. There is no 'alsactl store' option, because there is no alsactl file. I had to manually add a couple of lines in /etc/modprobe.conf to get the sound to work, but I wonder if something else is needed for that to allow storing settings. If one of you can read the above document and the linked files that provide more detail, and suggest a solution, I would appreciate it.

Well, the short answer to why alsactl store/restore does not work is, as you know, because you do not have the script that runs it on startup and shutdown, and the reason you don't have the files is because you have not installed the alsa-utils package which contains them.

The drivers in the 2.6 kernel are only the drivers, what were previously contained in the alsa-drivers package. The kernel facilities do not include what we know as alsa-libs and alsa-utils.

Install those (alsa-utils depends on alsa-libs, so you need both), and then try setting your alsamixer settings, and storing them. I don't know the methodology for adding a startup script to the FC2 boot process, but whatever it is, you should add the alsasound script to that process.

As for your other issues, the general consensus I see around the forums is that KDE 3.2 should be removed before upgrading to KDE 3.3, and your output seems to support that. If I was you, I would install a light WM such as XFCE or ICEWM, login to that, uninstall both KDE and QT from there, then install the newer versions of both KDE and QT.

Hope that's helpful (at least for the sound issues-- don't wanna hijack the thread).