Re: config mixer device for aumix
On Sat, Sep 09, 2006 at 12:43:31 +0000, 46kmz5j02@sneakemail.com wrote:
> On 2006-09-08, Florian Kulzer wrote:
> > On Fri, Sep 08, 2006 at 21:42:06 +0300, Simo Kauppi wrote:
> >> On Fri, Sep 08, 2006 at 08:30:29PM +0200, Florian Kulzer wrote:
> >> > On Wed, Sep 06, 2006 at 00:06:53 +0000, 46kmz5j02@sneakemail.com wrote:
> >> > > I upgraded from sarge to etch, and now console sound apps like
> >> > > aumix and mp3blaster won't work (sound apps work fine in X).
> >> > > During boot, the following message is displayed:
> >> > >
> >> > > "Restoring mixer settings: failed"
> >> > >
> >> > > If I run 'aumix', it says "aumix: error opening mixer". The
> >> > > default mixer it is looking for, /dev/mixer, does not exist. I
> >> > > looked around in /dev/ and found the following:
> >> > >
> >> > > "crw-rw---- 1 root audio 14, 0 2005-02-26 01:39 /dev/.static/dev/mixer"
> >> > >
> >> > > If I run 'aumix -d /dev/.static/dev/mixer', then it works as it
> >> > > should, even if I kill it and then just run 'aumix' without the
> >> > > '-d' option. If I then shutdown or reboot, I see a message about
> >> > > the mixer and muting being saved. However, on the next boot,
> >> > > it once again says: "Restoring mixer settings: failed".
> >> >
> >> > [...]
> >> >
> >> > > I am using kernel 2.6.15-1-k7.
> >> >
> >> > That looks like a problem with udev. Did you purge the hotplug package
> >> > after you upgraded to Etch?
> >
> > [...]
> >
> >> I think that aumix uses some kind of OSS compatibility mode of ALSA. In
> >> my case I need to `modprobe snd-mixer-oss` to get the /dev/mixer
> >> device for aumix.
> >
> > Good point, I had not thought of that. The module is loaded
> > automatically for me during boot (Sid, udev 0.100-1), but that might not
> > be the case for the OP. However, the fact that he has the mixer in
> > /dev/.static/dev/ might mean that the module is loaded in his case as
> > well and that there is a problem with udev.
[...]
> I just now purged hotplug by doing 'aptitude purge hotplug',
> then rebooting. It didn't fix aumix.
>
> Here is the output of 'lsmod':
[...]
> snd_emu10k1 97252 0
> snd_rawmidi 22688 1 snd_emu10k1
> snd_seq_device 8012 2 snd_emu10k1,snd_rawmidi
> snd_ac97_codec 82528 1 snd_emu10k1
> snd_pcm 77704 2 snd_emu10k1,snd_ac97_codec
> snd_timer 21444 2 snd_emu10k1,snd_pcm
> snd_ac97_bus 2112 1 snd_ac97_codec
> snd_page_alloc 9992 2 snd_emu10k1,snd_pcm
> snd_util_mem 4352 1 snd_emu10k1
> snd_hwdep 8480 1 snd_emu10k1
> snd 48740 7 snd_emu10k1,snd_rawmidi,snd_seq_device,
> snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep
> emu10k1_gp 3520 0
> soundcore 8992 1 snd
[...]
> And here is the output of lspci:
[...]
> 00:11.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
[...]
> I know next to nothing about udev; I first heard of it when I
> upgraded to etch, and I got a message about how it wouldn't
> work with the kernel I was using at the time, 2.6.8-3-k7. I
> thought that was the latest kernel available, until I found
> that they had changed package names from "kernel-image" to
> "linux-image".
udev generates device nodes in /dev/. Sometimes it has to be prodded a
little by modprobing the right modules for missing devices. Try to
"modprobe snd_mixer_oss" as Simo has suggested, and maybe also "modprobe
snd_pcm_oss". Is /dev/mixer created or are there any error messages?
--
Regards,
Florian
Reply to: