On Sunday 30 September 2007Gabriel Ambuehl wrote:
> Well, if certain versions of alsa-driver work and others don't, then,
> everything else equal, alsa-driver would likely be at fault ;)
I don`t think the fault is only at alsa-driver:
In Feisty (Kernel 2.6.20-16) with alsa-driver 1.0.13-3ubuntu1 my soundcard worked out of the box. Only mic wasn't recognized.
With self compiled alsa-driver (+ alsa-lib, alsa-utils) 1.0.15rc2 all worked fine in Feisty.
Gutsy (Kernel 2.6.22-12) with alsa-driver 1.0.14 absolutely nothing worked. It also doesn`t worked with 1.0.15rc2,
only the whole 1.0.15rc3 alsa package made it.
Also I think there is no chance to get the latest alsa-driver in the final Gutsy release.
But a good workaround would be to backport the alsa-driver, alsa-lib and alsa-utils, so that we could provide a fast solution for the users, who will run into this and are afraid compiling things by themself.
On Sunday 30 September 2007Gabriel Ambuehl wrote:
> Well, if certain versions of alsa-driver work and others don't, then,
> everything else equal, alsa-driver would likely be at fault ;)
I don`t think the fault is only at alsa-driver:
In Feisty (Kernel 2.6.20-16) with alsa-driver 1.0.13-3ubuntu1 my soundcard worked out of the box. Only mic wasn't recognized.
With self compiled alsa-driver (+ alsa-lib, alsa-utils) 1.0.15rc2 all worked fine in Feisty.
Gutsy (Kernel 2.6.22-12) with alsa-driver 1.0.14 absolutely nothing worked. It also doesn`t worked with 1.0.15rc2,
only the whole 1.0.15rc3 alsa package made it.
Also I think there is no chance to get the latest alsa-driver in the final Gutsy release.
But a good workaround would be to backport the alsa-driver, alsa-lib and alsa-utils, so that we could provide a fast solution for the users, who will run into this and are afraid compiling things by themself.