Hi All, I bought a Sound card with VIA chip set. This sound card does not work after boot, the kernel just says: ... ICE1724: probe of 0000:01:06.0 failed with error -12 ... However, running 'alsaconf' (I uses 1.0.13) with root account can configure that card successfully without any trouble, it says the sound card "ice1724 VIA Technologies Inc. VT1720/24 [Envy24PT/HT] PCI Multi-Channel" is found. Following is the detail output from 'alsaconf': moncave:~# alsaconf Unloading ALSA sound driver modules: snd-ice1724 snd-ice17xx-ak4xxx snd-ak4114 snd-ak4xxx-adda snd-mpu401-uart snd-seq-dummy snd-seq-oss snd-seq-midi snd-seq-midi-event snd-seq snd-intel8x0 snd-ac97-codec snd-ac97-bus snd-pcm-oss snd-mixer-oss snd-rawmidi snd-seq-device snd-pcm snd-timer snd-page-alloc. Building card database... Running update-modules... Loading driver... Setting default volumes... =============================================================================== Now ALSA is ready to use. For adjustment of volumes, use your favorite mixer. Have a lot of fun! After running alsaconf, I can run 'mplayer' successfully. I searched on the web for a while and got some impression that this issue has something to do with the PCI vendor ID, etc, following is the detail output from lspci: # lspci -vvv -nn -xxx .... .... 01:06.0 Multimedia audio controller [0401]: VIA Technologies Inc. VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio Controller [1412:1724] (rev 01) Subsystem: VIA Technologies Inc. Unknown device [1412:2403] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 Interrupt: pin A routed to IRQ 3 Region 0: I/O ports at df80 [size=32] Region 1: I/O ports at dc00 [size=128] Capabilities: [80] Power Management version 1 Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 12 14 24 17 05 00 10 02 01 00 01 04 00 40 00 00 10: 81 df 00 00 01 dc 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 12 14 03 24 30: 00 00 00 00 80 00 00 00 00 00 00 00 03 01 00 00 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 01 00 01 04 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... ... I have no idea how to use this piece of information to make the process of boot-sound-card-detection work, do I need to modify the source code and recompile the kernel? Or just editing some configuration files? PS, I use debian 4.0 and my alsa packages are: moncave:~# dpkg --list | grep alsa ii alsa-base 1.0.13-5etch1 ALSA driver configuration files ii alsa-tools 1.0.13-1 Console based ALSA utilities for specific ha ii alsa-utils 1.0.13-2 ALSA utilities ii gstreamer0.10-alsa 0.10.10-4 GStreamer plugin for ALSA ii libpt-plugins-alsa 1.10.2-2+etch1 Portable Windows Library Audio Plugin for th ii libsdl1.2debian-alsa 1.2.11-8 Simple DirectMedia Layer (with X11 and ALSA Thank you very much for your help in advance. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user