The various alsa 0.9.8 packages got marked stable recerntly so I decided to upgrade from alsa 0.9.2 After upgrading and rebooting, loading the kernel module for my SB Live fails claiming it cannot find the card. is doing: # modprobe snd-emu10k1 fails saying it cannot initilise the module I've now downgraded to alsa 0.9.2 and everything works again. Here's some stuff from the logs: Nov 27 19:33:42 localhost kernel: EMU10K1/Audigy soundcard not found or device busy Nov 27 19:33:42 localhost insmod: /lib/modules/2.4.20-gentoo-r5/kernel/sound/pci/emu10k1/snd-emu10k1.o: init_module: No such device Nov 27 19:33:42 localhost insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Nov 27 19:33:42 localhost insmod: /lib/modules/2.4.20-gentoo-r5/kernel/sound/pci/emu10k1/snd-emu10k1.o: insmod snd-card-0 failed Reproducible: Always Steps to Reproduce: 1. emerge alsa-driver (version 0.9.8) 2. reboot 3. modprobe snd-emu10k1 Actual Results: The module fails to initialise Expected Results: The module should find the card and initialise properly $ /sbin/lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] 00:0b.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07) 00:0b.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07) 00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1b) 00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1b) 00:11.4 USB Controller: VIA Technologies, Inc. USB (rev 1b) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 30) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200] (rev 01) $ emerge --info Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gentoo-r5) ================================================================= System uname: 2.4.20-gentoo-r5 i686 AMD Athlon(tm) Gentoo Base System version 1.4.3.10p1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://212.219.56.162/sites/www.ibiblio.org/gentoo/ http://194.83.57.2/sites/www.ibiblio.org/gentoo/ http://194.83.57.3/sites/www.ibiblio.org/gentoo/ http://194.83.57.7/sites/www.ibiblio.org/gentoo/ http://194.83.57.11/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline arts tetex aalib bonobo svga java ruby postgres X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk motif opengl mozilla ldap cdr alsa -kde -qt gtk2 apache2"
*** Bug 34828 has been marked as a duplicate of this bug. ***
This also applies to the 2.4.20-r8 kernel.
there's a bug upstream http://sourceforge.net/tracker/index.php?func=detail&aid=848718&group_id=27464&atid=390601
Got the same bug ... Maybe it should be rolled back to version 0.9.2 for stable ...
The alsa homepage says that they don't check the sourceforge tracker. The following message on the mailing list suggest that the person "upgrade to CVS." http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg10101.html For the record, ACCEPT_KEYWORD='~x86' to give me version 1.0.0_rc1 seems to also work. (I have a SB Live! Value.) Note that the "stable" version on the website is now 1.0.0rc2. So I guess you have an option of going forward or backward.
*** Bug 35585 has been marked as a duplicate of this bug. ***
Does someone have a reference to a patch agains 0.9.8 that fixes this so we can include it in 0.9.8 rather than making people upgrade to 1.0.x?
won't fix... alsa-1.0.x fixes it, and chances are alsa-1.0.x will be a stable ebuild in a few weeks now that all the 1.0 incompatibilities mentioned in bugzilla have been fixed.
