Summary: | ALSA driver package assumes config.modular | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Leif Brown <leifbrown> |
Component: | Current packages | Assignee: | Arcady Genkin (RETIRED) <agenkin> |
Status: | RESOLVED REMIND | ||
Severity: | trivial | CC: | leifbrown |
Priority: | Low | ||
Version: | 1.1a | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Leif Brown
2002-04-24 11:27:10 UTC
I'd definitely report this to the ALSA people, but I'll keep this bug here too. Assigning to agenkin. Submitted upstream, but I don't expect a fix. The 0.5 series is officially deprecated. Hi! Two questions: - Does the same problem happen with alsa-0.9.10 ebuilds? You can test compiling it w/o installing the package with the command: ebuild alsa-driver-0.9.0_beta10.ebuild compile - Is this just a matter of checking for existence of the config.modular file under /usr/src/linux/? I don't seem to have that file on neither of my two Linux machines, and I have module support enabled in both kernels. I have never built `monolithic' kernels; hat am I missing? Thanks. For the record, the original reporter emailed me that he, at the moment, was not able to reproduce the bug himself. He will try again in a week when he'll have a new system to install. Marking this bug as REMIND. This is repeatable with ALSA 0.5.12a, but isn't a problem with ALSA 0.9x. Since 0.9x is unmasked (and default for new installs), this should never bother anybody again. I suggest changing resolution to WONTFIX, or LATER, FIXED when the 0.5 series driver has been masked. |