I posted this to the amd64 list, but am not getting any results yet, so I'll repost is here. Hopefully the problem is not specific to amd64, but some know behavior in which alsaconfig modifies some config file/permissions I can't seem to be able to trace. I had my SB Audigy 2 ZS almost completely working (a couple of games were giving me trouble), but I decided (quite regretfully) to manually run alsaconf. As a result I get no sound output now. Even running yast2 sound again, and rebooting. All cable connections were rechecked, and volumes in kmix and alsamixer and in my speakers are up. yast finds the card and everything. But everytime I try to test the volume nothing happens. No audio apps seem to be working. This is stock SuSE 9.2 64bit, completely patched. The card's IRQ is 185. I'd really appreciate some help. TIA. My /etc/modprobe.d/sound: options snd-emu10k1 enable=1 extin=0x3fff extout=0x7fff index=0 \ max_buffer_size=128 max_synth_voices=64 seq_ports=4 # qnJ_.9jPiZAnlR97:SB Audigy 2 ZS (SB0350) alias snd-card-0 snd-emu10k1 The module options are from /usr/src/linux/Documentation/sound/alsa/ALSA-Configuration.txt, and they were working before I decided to run alsaconf. These are some log messages I found that could be related: From dmesg: drivers/usb/input/hid-input.c: event field not found drivers/usb/input/hid-input.c: event field not found Creative EMU10K1 PCI Audio Driver, version 0.20a, 15:26:57 Dec 22 2004 ALSA sound/core/seq/oss/seq_oss.c:234: can't register device seq ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 18 (level, low) -> IRQ 185 From /var/log/messages: Dec 28 13:27:07 severian kernel: ALSA sound/core/seq/oss/seq_oss.c:234: can't register device seq Dec 28 13:27:07 severian modprobe: FATAL: Error inserting snd_seq_oss (/lib/modules/2.6.8-24.10-default/kernel/sound/core/seq/oss/snd-seq-oss.ko): Device or resource busy Dec 28 13:27:08 severian kernel: ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 18 (level, low) -> IRQ 185