Re: [Alsa-user] linux 2.5 and alsa 0.9.0rc1, problem
Brought to you by:
perex
|
From: Takashi I. <ti...@su...> - 2002-04-29 16:26:58
|
At Sun, 28 Apr 2002 11:04:38 -0400 (EDT),
Allin Cottrell wrote:
>
> I'm running into some odd problems with alsa 0.9 and the Linux 2.5
> kernel. My setup right now is (a) alsa drivers as supplied with the
> 2.5.10 kernel, plus (b) the alsa library and utils version 0.9.0rc1 (I
> had the same problem with linux kernel 2.5.8).
>
> Most important problem: I'm used to having the alsa sound modules
> auto-load on demand, and this worked fine for me with alsa 0.5 and
> linux kernel 2.4.X. Now, however, if I launch an alsa app (aplay or
> alsaplayer for instance) without first manually loading the sound
> modules, very bad things happen. Gkrellm shows an ever-increasing
> number of processes being started; the system becomes unresponsive and
> the only way out that I have found is to reboot the machine (doing
> "killall" on the alsa app does not seem to stop the runaway process
> escalation).
hmm, weird.
> Secondary problem: If I do "modprobe snd-cs46xx" as root first, alsa
> apps are mostly well-behaved. The exception is alsaplayer (version
> 0.99.59, compiled against the new alsa lib). It says
>
> error on set_period_size (1024)
> <snip>
> failed to configure output device...trying OSS
>
> and hangs. In OSS mode ("alsaplayer -o oss") it starts fine.
try the different period size. iirc, alsaplayer requires the exact
period size (not inquiring via snd_pcm_hw_*_near function).
> I'm using devfs. Here are the relevant config bits, some of which I
> suppose must be wrong:
>
> /etc/devfsd.conf
>
> # ALSA
> LOOKUP snd MODLOAD ACTION snd
> REGISTER ^sound/.* PERMISSIONS root.www 660
> REGISTER ^snd/.* PERMISSIONS root.www 660
>
> /etc/modules.conf
>
> alias char-major-14 soundcore
> alias /dev/snd snd-cs46xx
> alias /dev/sound snd-pcm-oss
what are these two?
> alias char-major-116 snd
> options snd snd_major=116 snd_cards_limit=1
> above snd-cs46xx snd-pcm-oss
is this necessary?
Takashi
|