Am Montag, 22. Januar 2007 17:36 schrieb Elimar Riesebieter: > On Mon, 22 Jan 2007 the mental interface of > > Mikael Magnusson told: > > Steve Langasek wrote: > > >On Mon, Jan 22, 2007 at 07:39:03AM +0100, Markus Schulz wrote: > > >>>doesn't sound 'grave' to me; if anything, it sounds like a bug > > >>> in 2.6.19 for changing interfaces in ways that break userspace. > > >> > > >>yes, exactly this. Should this be reported anywhere? > > > > > >Preferably, upstream to the kernel maintainers responsible for the > > > breakage. > > > > According to alsa-devel the problem has been "Fixed and committed > > to HG tree". > > > > http://article.gmane.org/gmane.linux.alsa.devel/43900 > > Markus, could you please test the according patch:
[..patch..] i've patched alsa-lib 1.0.13-1 debian source package. rebuild alsa-lib and alsa-tools (the latter with the new generated libasound2-dev) package in clean pbuilder environment. Then i've installed the new ld10k1/lo10k* and libasound2 package into my running system. Now i can start ld10k1 on 2.6.19.2 kernel, but my old patchset (working on 2.6.18-1-k7) dont produce any sound output?!? All mixer controls looks like at 2.6.18-1-k7 kernel, but no sound anymore. With the new version of alsa-lib and ld10k1 i _can't_ start ld10k1 on 2.6.18-1-k7 and the patch don't look for me like to fix this. Have i misunderstand something? Markus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
