Johannes Held wrote: > Hi. > >> Here is a list of things to check: > let's go through it. > >> 1. In alsamixer, make sure that you have: > some things I found - some not >> 1.1. 3D control center in level 0 >> 1.2. 3D control depth in level 0 >> 1.3. 3D control switch muted > done >> 1.5. Surround muted >> 1.6. Surround down mix muted >> 1.7. Surround jack mode shared (don't know what this means :-) >> 1.8. Center muted >> 1.9. Center/LFE Down Mix muted > not found >> 1.10. Mic muted (if you want to hear what is received in mic, you >> can set this in a level that you desire) >> 1.11. Mic Boost muted (same comments as above) >> 1.12. Mic select as you choose > done >> 1.13. IEC958 muted >> 1.14. IEC958 playback AC97-SPSA doesn't matter > done >> 1.15. Analog to IEC958 Output muted > not found >> 1.16. Channel mode 2ch >> 1.17. Duplicate front muted >> 1.18. Exchange center/LFE muted >> 1.19. External amplifier muted >> 1.20. Swap surround slot muted > not found > >> 2. You don't need to load any modules in MODULES clause of rc.conf. >> Udev is able to guess the right ones. > Should I have it empty? > MODULES=(intel-agp uhci_hcd eepro100 ipw2100 ohci1394 yenta_socket > speedstep-centrino cpufreq_powersave cpufreq_userspace freq_table fuse) > >> 3. You need to put hal and alsa in the DAEMONS clause of rc.conf. Hal >> must be before alsa. > done > DAEMONS=(syslog-ng klogd @network @laptop_mode !fam @hal !acpid @cpudyn > @uptimed > @alsa) > > >> 4. /etc/modprobe.conf must not have any references to the snd-* >> modules. They are not needed anymore, because udev does its job. > # /etc/modprobe.conf (for v2.6 kernels) > # > # --- BEGIN: Generated by ALSACONF, do not edit. --- > # --- ALSACONF version 1.0.10 --- > #alias snd-card-0 snd-intel8x0 > #alias sound-slot-0 snd-intel8x0 > # --- END: Generated by ALSACONF, do not edit. --- > > #alias eth1 ipw2100 > I #ed lines 5,6 and 9. [don't know why I had line 9 in?] > >
Are you sure that your onboard sound card is an intel ac97? It may very well be a c-media processor, and if the wrong driver attaches to the device, this may very well be the result. Don't trust lspci, read the motherboard documentation or just take a peep at the motherboard itself and locate the sound chip. May I ask what motherboard you are using? Glenn _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
