17:24 <@Chainsaw> jkt|: It is now recommended to use in-kernel ALSA. If alsa-drivers are able to drive a card that does not work with in-kernel drivers, we want to hear about it.
Created attachment 123209 [details, diff] alsa-driver-is-going-to-get-nuked.patch
(In reply to comment #0) > 17:24 <@Chainsaw> jkt|: It is now recommended to use in-kernel ALSA. If > alsa-drivers are able to drive a card that does not work with in-kernel > drivers, we want to hear about it. Is there any explanation for that? Or is this discussed elsewhere? Regards Stefan
> Is there any explanation for that? Or is this discussed elsewhere? The new ALSA maintainers feel that the alsa-drivers ebuild is an unnecessary maintenance burden that has no clear advantages. If you want to discuss this, you can do so on the gentoo-dev mailing list. Bugzilla is for technical discussion, and this bug is for a documentation change.
From a technical viewpoint this sucks.
Small note regarding the patch: There's an error with the date mentioned being June 2006 - I suspect that should be June 2007. For anyone who's wondering what the stupidly name patch actually is, it's a modification for the alsa guide.
(In reply to comment #5) > For anyone who's wondering what the stupidly name patch actually is, it's a > modification for the alsa guide. ...as the clever reader could imagine, given the "Product", "Component" and "URL" fields of this bug.
kernel driver doesn't work with cmipci. All i see is intel (i don't want to use that). alsacfg just shows intel (or nothing if i remove intel driver). lsmod shows snd_cmipci. However, if i use alsa-driver with ALSA_CARDS="cmipci" it works. 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High 01:0b.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
(In reply to comment #7) This is not the place to report bugs against ALSA. Open a separate bug for that issue and assign it to the appropriate Bugzilla Product. jkt: I really will have a cleaned up patch for this guide, I really will. :) Gimme another couple of days for my eyesight to improve (you've no idea how hard it is to try to do this stuff without being able to see), and once I'm off devaway I'll attach the thing.
in-kernel drivers are not working for maestro-3i. Here is the card info: 02:03.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i PCI Audio Accelerator (rev 10) I've confirmed this on both a Gateway Solo 5300 and a Dell Inspiron 8100. Older versions of the alsa-driver worked for this card. Now, 1.0.14-r1 fails to compile with errors, so I'm unable to test it. How do you want this bug reported? Want a separate bug? I see several outstanding and nothing happening...no comments on how to fix or resolve either.
Yes, please file separate bugs: - one for not being able to use in-kernel audio drivers (if that is the case -- your comment doesn't make it clear if you actually tried that or whatever) - one for alsa-driver compile error (if there is not one already) As for bugs not being attended to, well, there is only one open bug against kernel audio drivers. Or if you meant bugs about alsa-driver, yes, there isn't really much attention going into that package (one of the reasons why we advise people to change).
I will file bugs after some more testing. I think the actual issue may be with alsa-lib package. Sorry for the chatter here. On a side note, it is particularly difficult to search the bug tracker for in-kernel driver issues.
Fixed in CVS. Hi Jan! Don't mind me.... ;) I mostly didn't use your patch, but I did pull the TODO from it at least. commit log sez: "removed alsa-driver steps from the guide, per bug 183418, bug 207427 and other showstopper/regression bugs, and requests from the alsa & kernel teams. no one maintains or wants to maintain alsa-driver. it is the weakest link."