159063 2006-12-25 01:31 0000 Default ALSA_CARDS on x86 includes unsupported driver (maestro3) 2006-12-26 07:11:01 0000 1 1 1 Unclassified Gentoo Linux Applications 2006.1 All Linux RESOLVED FIXED P2 normal --- 158678 1 ed@catmur.co.uk alsa-bugs@gentoo.org ticho@gentoo.org ed@catmur.co.uk 2006-12-25 01:31:35 0000 checking for parallel port support... yes checking for power management... yes checking for which soundcards to compile driver for... configure: error: Unsupported soundcard maestro3 !!! Please attach the following file when filing a report to bugs.gentoo.org: !!! /var/tmp/portage/media-sound/alsa-driver-1.0.14_rc1/work/alsa-driver-1.0.14rc1/config.log !!! ERROR: media-sound/alsa-driver-1.0.14_rc1 failed. Call stack: ebuild.sh, line 1580: Called dyn_compile ebuild.sh, line 945: Called src_compile alsa-driver-1.0.14_rc1.ebuild, line 114: Called econf '--with-oss' '--without-debug' '--with-kernel=/usr/src/linux' '--with-build=/usr/src/linux' '--with-isapnp=yes' '--with-sequencer=yes' '--with-cards= ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci' ebuild.sh, line 541: Called die !!! econf failed !!! If you need support, post the topmost build error, and the call stack if relevant. # grep -A3 ALSA_CARDS /usr/portage/profiles/default-linux/x86/make.defaults ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x \ ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 \ trident usb-audio via82xx via82xx-modem ymfpci" Please assign to ticho. ed@catmur.co.uk 2006-12-25 01:44:19 0000 Also ymfpci. ticho@gentoo.org 2006-12-25 03:16:53 0000 maestro3 and ymfpci removed from default ALSA_CARDS, although I still can't understand why does it report as unsupported. From alsa-driver's acinclude.m4, you need CONFIG_SOUND, CONFIG_PCI and CONFIG_FW_LOADER options enabled - the same as f.e. for emu10k1, which works nicely. Perhaps Diego can explain this mystery to me... Anyway, thanks for the report, and sorry. ticho@gentoo.org 2006-12-25 04:48:14 0000 After changing from in-kernel alsa drivers to those provided by alsa-driver package, I was able to install this package using default ALSA_CARDS (including maestro3 and ymfpci). I have CONFIG_FW_LOADER enabled. Perhaps alsa-driver should be checking for this kernel option for cards which need it? Diego? flameeyes@gentoo.org 2006-12-25 05:41:29 0000 It should indeed, the problem is that I couldn't know all of them offhand :) Feel free to leave them in the defaults, CONFIG_FW_LOADER is now widespread enough not to be an hassle (as ISA is). I'll fix it in a moment. flameeyes@gentoo.org 2006-12-25 05:50:38 0000 Fixed, now all the drivers that require CONFIG_FW_LOADER enabled will fail gracefully if it's disabled in-kernel. ed@catmur.co.uk 2006-12-26 07:11:01 0000 (In reply to comment #5) > Fixed, now all the drivers that require CONFIG_FW_LOADER enabled will fail > gracefully if it's disabled in-kernel. So the default setup for ALSA in Gentoo now requires CONFIG_FW_LOADER? I don't have a problem with that, but it should probably be documented in the upgrade notes for when the 1.0.14 ebuilds hit stable. http://www.gentoo.org/doc/en/alsa-guide.xml#alsa-driver doesn't currently mention the default ALSA_CARDS setting or which configs are required for such.