| 1 |
Follow my device since I'm the developer ;) |
| 2 |
|
| 3 |
I'm not on gentoo-users, so please feel free to forward my response |
| 4 |
there as well. |
| 5 |
|
| 6 |
media-sound/alsa-driver-1.0.2c should work with your 2.6.x kernel. The |
| 7 |
results of emerging this package would give you the same configuration |
| 8 |
as configuging alsa to be built as modules in the kernel's 'make config' |
| 9 |
(aside from version differences). The ones in 2.6.x are KNOWN to work |
| 10 |
correct, and the alsa-driver ones SHOULD work correct (according to |
| 11 |
alsa, they DO work, but I don't take their word for it). |
| 12 |
|
| 13 |
So the prefered method for alsa usage if you want to help test things |
| 14 |
is: |
| 15 |
alsa-driver-1.0.2c |
| 16 |
alsa-lib-1.0.2 |
| 17 |
alsa-utils-1.0.2 |
| 18 |
alsa-oss-1.0.2 |
| 19 |
alsa-tools-1.0.2 |
| 20 |
|
| 21 |
If you want to play it safe with 2.6, then do modules in the kernel and |
| 22 |
use the 0.9.8 versions of alsa-{lib,utils,oss,tools}. If you experience |
| 23 |
ANY problems, PLEASE report on bugzilla. AFAIK, the only problem with |
| 24 |
alsa in 2.6 right now is that the init script tries to load all the |
| 25 |
sound modules (which is just really a problem for some people, and then |
| 26 |
it's just yucky boot-time text and extra modules loaded that you don't |
| 27 |
need...) |
| 28 |
|
| 29 |
Thanks, |
| 30 |
Jeremy |
| 31 |
|
| 32 |
On Tue, 2004-02-17 at 12:11, Kevin wrote: |
| 33 |
> Brad and Jeremy, thanks for your replies. Sorry if my post shouldn't have |
| 34 |
> gone to gentoo-dev. I did post to gentoo-users as well, but because of |
| 35 |
> the init script thing, thought that the developer's list was also |
| 36 |
> apropos. I didn't think to check bugzilla before posting, and for that I |
| 37 |
> offer my apologies. |
| 38 |
> |
| 39 |
> On Tuesday 17 February 2004 13:55, Jeremy Huddleston wrote: |
| 40 |
> > Actually, FWIW, alsa-driver-1.0.2c should work with the 2.6.x kernels. |
| 41 |
> > In order to do that, ALSA support in the kernel must be turned off or |
| 42 |
> > configured as a module (so it's overwritten by alsa-driver). |
| 43 |
> |
| 44 |
> Which one is preferred (using ALSA from kernel sources or using |
| 45 |
> alsa-driver-1.0.2.c)? |
| 46 |
> |
| 47 |
> > |
| 48 |
> > For the init script loading multiple cards trouble, go over to |
| 49 |
> > ghttp://bugs.gentoo.org/show_bug.cgi?id=41600 and add yourself to the |
| 50 |
> > CC of that bug so you can help me figure this problem out. |
| 51 |
> |
| 52 |
> Done, and will do. How can I help? (I'm a Gentoo newbie, but a long-time |
| 53 |
> (10 years) Linux user and sysadmin. I have some very limited programming |
| 54 |
> skills in C, C++, and shell scripts, but would be happy to help however I |
| 55 |
> can. |
| 56 |
> |
| 57 |
> > |
| 58 |
> > The alsasound init script will load your modules. It comes in the |
| 59 |
> |
| 60 |
> Yes, I see that, but the multiple module thing... I've just done a |
| 61 |
> rc-update del alsasound boot for now. Should I just rebuild the kernel |
| 62 |
> and not build sound modules for anything but my sound card to use that |
| 63 |
> init script? |
| 64 |
> |
| 65 |
> > alsa-utils package and should be added to the 'boot' runlevel: |
| 66 |
> > 'rc-update add alsasound boot'. Don't rely on hotplug to set you up |
| 67 |
> > properly. |
| 68 |
> |
| 69 |
> Ok... not sure whether to follow Brad's or Jeremy's advice here. If I |
| 70 |
> don't use hotplug as Jeremy suggests, what should I do instead? If the |
| 71 |
> answer's staring me in the face, then I'm sorry I don't see it. |
| 72 |
> |
Archives