>what is the kernel message? Ah ha.
ALSA ../../alsa-kernel/pci/ice1712/ice1712.c:2472: invalid EEPROM version 120 the driver wants version 1 and barfs on anything else. If I disable the error-out at that point in the code, here's what results: ALSA ../../alsa-kernel/pci/ice1712/ice1712.c:2472: invalid EEPROM version 120 ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1829: AC'97 0:0 does not respond - RESET [REC_GAIN = 0xffff] ice1712: cannot initialize pro ac97, skipped devfs_register(unknown): could not append to parent, err: -17 devfs_register(unknown): could not append to parent, err: -17 devfs_register(unknown): could not append to parent, err: -17 The module then deals with the card well enough for it to come up in amixer with read/write access, but not well enough to actually make sounds. Only S32_LE is accepted at all, the others producing "aplay: set_params:1346: Sample format non available". If S32_LE is used, aplay and record block for a few seconds, then product aplay: pcm_write:1623: write error: Input/output error or arecord: pcm_read:1710: read error: Input/output error Other glitches: douzzer@triceps douzzer $ /usr/sbin/alsactl -f /tmp/bla store 2 /usr/sbin/alsactl: get_controls:484: snd_ctl_open error: No such device Clearly more work is needed in the driver. I'm sure I'm missing some vital details on the card needed to do it, not to mention, some vital skills (I'm a hacker of neither the linux kernel nor the ALSA kernel). ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
