This is only an issue on systems with monolithic kernels, where /usr/src/linux/config.modular does not exist. In that case, the alsa-driwer package errors out of compilation. Invoking "touch" or "mknod" on the missing file before running the compile fixes the problem. (Obviously, things break if the support wasn't actually compiled into the kernel.) I'm not sure whether this should be considered a problem with the ebuild or with the ALSA code. I saw this on media-sound/alsa-driver-0.5.12a, so it may not be an issue with other versions.
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.