Hey, I cant seem to get any sound on my sys with mandrake 2.0. My motherboard (a7v266-e) has onboard sound, but i recently purchased a soundblaster audigy 2 which i obviously use instead. Manrake recognizes both soundcards in the config, but i think that its running primarily through the onboard. Does anyone know how i can change the default input/output over to the audigy? Any help would be greatly appreciated!

thanx

g

Dani AI

Generated

Brief context and what helped: ’s card was seen by the system but produced no sound — a very common situation where the kernel/ALSA knows the hardware but mixer channels are muted or routed wrong. correctly pointed to BIOS resource issues; ’s final fix (raising channels in KMix) is also a typical and immediate solution when a card is present but silent. (wiki.debian.org)

Quick diagnostics to run (in this order):

  • cat /proc/asound/cards and aplay -l — confirms which ALSA cards exist.
  • cat /proc/asound/modules or lsmod | grep snd — shows the module names actually loaded.
  • alsamixer (console) or KMix (KDE) — unmute and raise Master/PCM/Wave channels; use m in alsamixer to toggle mute.
  • speaker-test -c2 -t wav or aplay /usr/share/sounds/alsa/Front_Center.wav to exercise outputs.
    These /proc files and utilities are the primary way ALSA reports devices. (kernel.org)

If the Audigy is present but the onboard card becomes the default, fix the ordering in the modprobe config so Audigy is card 0. Find the exact module names from /proc/asound/modules and then add a small config file (replace <onboard_module> with the real name you found):

# /etc/modprobe.d/alsa.conf  (or /etc/modprobe.conf on older distros)
options snd cards_limit=2
options snd-emu10k1 index=0
options snd-<onboard_module> index=1
alias snd-card-0 snd-emu10k1
alias snd-card-1 snd-<onboard_module>

The index= / slots= mechanism is the supported way to fix card order. (docs.kernel.org)

BIOS note and a couple of cautions: the BIOS “PnP OS” setting controls whether the BIOS or the OS assigns resources — toggling it can change device enumeration and, in some cases, affect removable devices; change one setting at a time and verify behavior. Some Audigy/EMU devices also require ALSA firmware packages to function fully, and installing alsa-base / alsa-utils and ensuring your user is in the audio group will avoid permission/missing-firmware issues. (angelfire.com)

Recommended Answers

All 4 Replies

Hey, I cant seem to get any sound on my sys with mandrake 2.0. My motherboard (a7v266-e) has onboard sound, but i recently purchased a soundblaster audigy 2 which i obviously use instead. Manrake recognizes both soundcards in the config, but i think that its running primarily through the onboard. Does anyone know how i can change the default input/output over to the audigy? Any help would be greatly appreciated!

Make sure that you have disabled PnP-aware OS (that's how it's usually worded, it may say "Plug and Play" instead) in the BIOS Setup screen. It's usually ON by default.

well, my pnp was on, and i disabled it and booted... however, i still have no sound, and now linux won't recognise any of my removable media. The drives do not show up on the desktop. The dir are present in /mnt, but when opened, regardless of any media present in the physical drives, the dir are empty.

After a bit of meddling, i found that i can acces the removable media via kiwidisk. Had a bit of probs with hardrake, but it cleared up after a reboot. Still no sound though... I am an uber-noob at this, so, any help on this would be great, thanx!

Would this be the reason when I run make to install my divers it fails?

hey thanx, after a bit of fiddling (bringing up every possible volume in the kmix) i finally got sound! Thanx again for your help!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.