Hi, maybe resolved but ......:
On Thu, Mar 12, 2009 at 05:03:18AM +0100, Stefan Ott wrote: > On Thu, Feb 26, 2009 at 12:30, Labrador <labra...@edpnet.be> wrote: > > > No, I hadn't been forced to give anymore special commands in the past, > > not as user nor as root. > > Maybe your device file name changed (new kernel, new system, new udev > stuff, ...)? There are ways to tell udev to rename the device, maybe > you should look into that. The problem is now resolved: step 1: apt-get install libsox-fmt-all step 2: apt-get install oss-compat This last is VERY IMPORTANT; as long as there isn't oss-compat, aumix -q will give an error message. To resolve on long term the problem, the aumix package should see oss-compat as a dependence, since without it it couldn't longer work and nobody was able to check why aumix (but also saytime etc...) were not working. > > There is something broken or something that conflicts with amixer. > > If it works when you specify the device name then no, there's nothing > interfering. If it doesn't then yes, there might be some problem > there. oss-compat is the solution, maybe with libsox-fmt-all but I'm end-user and totally ignore what libs and so on exactly do, I just got aumix to work thanks to these two additional installations. > cheers Cheers! Labrad0r -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
