> I've been battling this problem for a month now. The only alternative I > found to go into /usr/portage/media-sound/alsa-driver and try installing > ebuilds from the newest one to the oldest until you find one that works. > I'm sorry, but I don't know how to find what version of alsa-driver I'm > using. When I installed GNOME it didn't seem to care which alsa-driver > I had installed, as long as there was one. Now the only problem comes > up when I try to do an emerge -uD world. I have to do it manually so > that it doesn't trip over alsa-driver... > > On Tue, 2005-01-11 at 15:44 +0000, James "Morpheous" Harrison wrote: > > Hi, [problem with alsa-driver build failure snipped]
Guys, I don't understand why you're having these issues with alsa-driver. It's built into the kernel and I can't for any reason see why you're emerging it directly... The built-in alsa is working fine for my soundcard, so maybe that's you're original issue, but I don't know... I just did an emerge --search of alsa-driver and it is showing as not installed. Did an emerge --pretend gnome and it does not come up as a dependency to be installed. I've got alsa in my USE flags, so it knows that I'm using it. It's always been a pain to use alsa drivers of a different release than the one included with the kernel. They have to be defined as modules, they have to be rebuilt after a successful kernel upgrade (or the different alsa modules will not be available to the new kernel), etc. It has always been recommended by all distributions (and alsa project, I believe) to stick with the built in alsa driver version unless you absolutely need a newer driver. That plus the fact that the built-in version tends to be well tested before it is accepted into the kernel source tree... Dave -- gentoo-user@gentoo.org mailing list
