Screwed up alsaconf, can't detect card now
My system's sound was only partially configured before, and now I've gone and created more problems for myself.
Before, in order to get sound I had to manually modprobe snd_via82xx (for my VIA8237 integrated card) after boot. This enabled hardware device '0,0', which is apparently just for stereo output. I discovered that device '0,1' could handle 5.1 surround sound, but to configure it I needed to execute alsaconf in addition to or in place of modprobe. Besides setting up this extra device, the alsaconf script also got rid of a strange repeated clicking sound that I would hear in the game Nexuiz while playing music.
At this point, I was wondering: 1) Why alsa gives me separate devices for a single card - is it a property of the hardware or the configuration; and, 2) Why is it that I needed to re-run the script every time I restarted the system? The only thing I can think of is that something like PAM would reset alsaconf's changes.
Anyway, yesterday I screwed up the system even more by initiating alsaconf while already running alsamixer. I soon realized my mistake and tried to kill both of them, but from that point on alsaconf refused to detect my sound card, with the message:
( - to which I answer No.)
No supported PnP or PCI card found.
Would you like to probe legacy ISA sound cards/chips?
Oddly enough, device '0,1' is now working regardless. I still have the clicking problem in Nexuiz.
So I guess my biggest problem is, how do I restore alsaconf to its original state? Do I need to weed through a configuration file somewhere or can I just reinstall it?