| Summary: | alsasound should start before coldplug | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Akos Ladanyi <ladanyi> |
| Component: | [OLD] Unspecified | Assignee: | Gentoo Sound Team <sound> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Unless I am mistaken Jeremy Huddleston (eradicator@gentoo.org) wrote the problematic line in the alsasound init script. Dear Jeremy, could you comment on this? it needs to be started after coldplug, but older 'hotplug' init script provided the 'coldplug' functionality, so it's still in there for that reason. yes, coldplug will load alsa modules if you don't tell it not to... that's fine. good for it... nothing bad there... If youu have multiple sound cards, you can tell coldplug to not load those drivers. but it's more out-of-box friendly for USB audio devices if it starts after coldplug, so that's where it's going. Most people who have multiple sound cards probably know or can figure out how to hack their system to work with them nicely. |
The alsasound init script in alsa-utils-1.0.8 declares the following: need bootmisc localmount after modules isapnp coldplug hotplug My problem is with "after coldplug hotplug". The gentoo handbook suggests to add hotplug to the default runlevel, the hotpug ebuild suggests to add coldplug to the boot runlevel, and the gentoo alsa guide suggests to add alsasound to the boot runlevel. All this means that alsasound is started _after_ coldplug (and before hotplug). This means that coldplug loads the alsa modules and not alsasound. And in case you have multiple sound cards the order in they are recognized by the driver is _not_ determined by the contents of /etc/modules.d/alsa. So I think alsasound should be started _before_ coldplug. Is there a reason why this is not the case? Reproducible: Always Steps to Reproduce: