Summary: | alsa-utils 1.0.4: /etc/init.d/alsasound fails to discover snd-intel8x0 card on start | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dead Schorsch <spamlover> |
Component: | [OLD] Library | Assignee: | Jeremy Huddleston (RETIRED) <eradicator> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | egore, ferringb, sound |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dead Schorsch
2004-05-25 05:05:26 UTC
taking ownership, since I'm experiencing this currently :) Having the same problem here on 2 pc's: 1.) snd-intel8x0, alsa 1.0.3, gentoo-dev-sources-2.6.5-r1 2.) snd-via82xx, alsa 1.0.3, gentoo-dev-sources-2.6.5-r1 I read something in kernel (or alsa) changelog that they made changes to alsa's AC97 handling, so i think this is releated, since both use AC97. i tried using 2.6.4 and got the same result :( The modprobe installed by sys-apps/module-init-tools doesn't work anymore in the way the old modprobe used to. The solution of this problem is replacing "modprobe -c" with "cat /etc/modules.conf". I boot my computer with a usb-midi keyboard device attached. that module somehow is auto-loaded before the driver for my 1010lt delta card (ice1712). the script then detects my usb-midi device as a *sound card* and says "Alsa Detected" forgoing any loading of the driver i need for my real sound device. there needs to be better logic to detect if all the devices configured in the config files are actually with loaded drivers or not. Hi, have just discovered similar situation, but ... was wondering, why mixer state wasn't loaded at startup, so started to dig around. It is a newly installed system and sound worked (with no coniguration from me) and this was a trap, as 1. my soundcard was NOT configured, but detected by pci hotplug and the module was correctly loaded 2. after entering alias snd-card-0 snd-intel8x0 AND running update-modules "modprobe -c" worked as expected! Solution: either force proper configuration via alias OR depend on hotplug (what do do after alsasound restart?) Nikolaus Is alsasound in your boot runlevel? Did youu run modules-update after editing /etc/modules.d/alsa? the init script I just added to portage works with a larger range of configurations... please try it out. Working. |