On Wed, 5 Jan 2005 11:01:51 -0500, michael higgins <[EMAIL PROTECTED]> wrote: > On Wed, 5 Jan 2005 03:37:28 +0000 > "Jans H. Xie" <[EMAIL PROTECTED]> wrote: > > > I guess you haven't read this: > > http://www.gentoo.org/doc/en/alsa-guide.xml [1] > > > > Before you emerge the alsa-drivers, you should add a line in your make.conf: > > ALSA_CARDS="here is your sound card type" > > > > After you emerge the alsa-drivers you should edit the > > /etc/modules.d/alsa to make alsa modules work. Find howto in the > > guide[1]. :)) > > > [snip] > > Thanks. I've now already read that doco, yes, but not thoroughly before I did > the kernel the first time. That first time, following the x86 quick install > guide, when prompted about alsa, of course I included and 'modularized' all > the alsa stuff I thought I'd need. > > I don't know about relative efficiency of performance, alsa in kernel or not, > but that's more research for me I guess. > > The problem with alsa in the kernel was, when attempting to emerge and update > the world, it consistently failed at the newer alsa driver library release. > This must be an unintended result, I think. Unless there is never a good > reason to compile asla into the kernel, but I've not heard an argument from > this list for or against yet... >
uh... Have you tried emerge -C alsa-drivers when you failed? It seems the alsa-dirvers is in your world file. In kernel vs. Modules depends on you, and I don't think there is obvious different between them. Kernel 2.6.x with ALSA buildin existed on my box a long time and I recently changed to alsa-drivers just for fun. BTW, the only convincible reason to use alsa-drivers I've seen is that it maybe update more frequently than kernel :) > When I finally recompiled the kernel without the alsa drivers, consistently, > when the new kernel boots, it can't find the alsa drivers for my cards. So, I > have to unmerge and remerge the package. This also can't be an intended > result, I'd think. > > . . . > > Also, I'm wondering, on a slightly different topic, why, when I recompile a > kernel, it overwrites with the new files, which may or may not, work and may > or may not force me to recover from the live cd. > > Is there a good way to add a copy of these current, functional, boot files to > the bootloaders (grub, lilo), so this will always appear as an alternate > option, one not to be replaced when I recompile this same kernel version yet > another time? > Yes of course. For grub just edit /boot/grub/menu.lst. Be careful that genkernel will overwrite the same version old one by new kernel, so you'd better type 'make' yourself and copy bzImage to your /boot with a new name. > -- mike higgins > > -- > gentoo-user@gentoo.org mailing list > > -- Jans -- gentoo-user@gentoo.org mailing list
