I missed emerging the alsa-firmware, and alsa-headers, so maybe that's why I'm having only partial success.
However, I use 2.6 kernels, with alsa compiled in, so I don't need to emerge alsa-drivers, which is what emerge attempts to do when I do emerge alsa-headers. I definitely don't want to emerge alsa-drivers with 2.6, do I? (I'm on dialup, thus emerge -f, below)
-----------------------------------------------------------------------------
mymachine wrc # emerge -f =media-sound/alsa-headers-1.0.7
Calculating dependencies ...done!
>>> emerge (1 of 1) media-sound/alsa-headers-1.0.7 to /
>>> Downloading
http://gentoo.osuosl.org/distfiles/dist ... .7.tar.bz2
--05:54:25--
http://gentoo.osuosl.org/distfiles/dist ... .7.tar.bz2
=> `/usr/portage/distfiles/alsa-driver-1.0.7.tar.bz2'
SNIP
------------------------------------------------------------------------------------------------
But if I do: mymachine wrc # emerge -pv alsa-headers
I get:
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N ] media-sound/alsa-headers-1.0.7 0 kB
Total size of downloads: 0 kB
mymachine wrc #
-----------------------------------------------------
Are they really the same file, and as long as alsa is in a 2.6 kernel, I don't
need alsa-headers-1.0.7? What is the correct thinking on this? Or should I
put alsa-drivers in /etc/portage/profiles/package.provided, and do:
emerge alsa-headers?
My latest kernel is:
2.6.10-rc2-mm2-V0.7.30-4 (this is with the real time patch)
Seems to run fine, but I don't think I'm getting full alsa capability here,
with Rosegarden/qsynth/vkeybd. Should I use the CFQ scheduler instead of Anticipatory? I usually run ck kerenls with CFQ, but lately had some
problems.
Any advice is appreciated.
wrc1944