When upgrading, emerge -uUD world, portage should check the file /usr/src/linux/include/sound/version.h for ALSA version in the kernel and NOT try to upgrade alsa-* (utils,libs,tools,etc) past that version. contents of file look like: /* include/version.h. Generated by configure. */ #define CONFIG_SND_VERSION "1.0.2c" #define CONFIG_SND_DATE "" The only current fix would be to continue to mask packages above that number manually in /etc/portage/package.mask.
*shrug* i used the 1.0.x series in userland while kernel was still 0.9.x and i never had any problems ;)
The version of alsa provided by the kernel has no baring on what version will actually work with the kernel.
That is not always true. You are too quick to jump a resolved. In fact, many things break when kernel driver and alsa-lib are not the same. You may not notice them if you don't use advanced things such a surround sound or AC3 passthrough but they DO BREAK. I've done development work with ALSA and can tell you that the kernel driver and libs should match. Furthermore, some tools such as amixer, alsamixer(gui) will also have issues if you run unmatched versions. Again, just because simple functions work DOES NOT mean everything is fine.
a) I do use AC3 passthrough on 2 separate systems. b) We are recommending that users use media-sound/alsa-driver over the in-kernel drivers unless the external packages do not compile (still an issue for some people). This way, the versions stay in-sync. c) If they use media-sound/alsa-driver, then checking /usr/src/linux/include/version.h is not a valid solution.
