Re: alsa0.9rc5 with linux-2.4.19 on debian unstable <-- sometime
You are the victim of yet another abrupt, incompatible change in the
ALSA driver interface. This one occurred between 0.9rc3 and 0.9rc5.
Basically, they removed the "snd_" prefix from *all* ALSA module
option names.
The rationale given was a desire to become compatible with de facto
kernel standards for module option names. Apparently, the kernel
developers had requested, but not demanded, this change when ALSA was
first incorporated into the 2.5 kernel source tree.
stallus@t-online.de (reiner) writes:
> Here is the modified config (removed snd_ prefix in options snd):
> # --- BEGIN: Generated by ALSACONF, do not edit. ---
> # --- ALSACONF verion 0.4.3b ---
> alias char-major-116 snd
> alias snd-card-0 snd-card-emu10k1
> alias char-major-14 soundcore
> alias sound-slot-0 snd-card-0
> alias sound-service-0-0 snd-mixer-oss
> alias sound-service-0-1 snd-seq-oss
> alias sound-service-0-3 snd-pcm-oss
> alias sound-service-0-8 snd-seq-oss
> alias sound-service-0-12 snd-pcm-oss
> options snd major=116 cards_limit=1 device_mode=0660 device_gid=29
> device_uid=0
>
> options snd-card-emu10k1 snd_index=0 snd_id=CARD_0
> snd_dac_frame_size=128 snd_ad
>
> c_frame_size=64
> # --- END: Generated by ALSACONF, do not edit. ---
You figured most of it out on your own. Good job! :-)
You also need to remove the "snd_" prefix from all your
snd-card-emu10k1 options.
> What is going on here? What is wrong
What's wrong is the difficulty of tracking a highly unstable component
like ALSA. Perhaps the Debian package developers could paper over
some of this mess using clever install scripts to automatically edit
existing module options. That might be a good idea, but it's tricky
to get exactly right. I have a lot of sympathy with the difficulty of
their task.
We can all hope that ALSA will become much more stable with the final
0.9 release version. This much change between "release candidates" is
discouraging.
Regards,
--
Jack O'Quin
Austin, Texas, USA
Reply to: