Re: [Alsa-user] Problem solved! - invalid operand when loading snd-ens1371

[David C. <da...@da...>]

Thanks to all who responded.

> 
> David Cornette wrote:
> > I hope someone can help me.  I have a Red Hat 8.0 system with a
> > SoundBlaster PCI 128.  I haven't been able to get sound to work at all.
> > Since the oss drivers didn't work (sox would hang trying to open the
> > device), I decided to try ALSA.  When I tried to load the module, modprobe
> > segfaulted.  I am using kernel-2.4.18-26.8.0 from Red Hat, and alsa
> > 0.9.1-fr1 from freshrpms.net.  If anyone has any ideas on what I can do to
> > get sound to work, please let me know.
> 
> I had the same problem. Solved it by downloading 0.9.0rc6 (note: RC6!), 
> compiling and installing. That version works great. I've not tried newer 
> versions, but the latest and greatest might, or might work. But, 
> 0.9.0rc6 does work.

I downloaded the source rpms for 0.9.1 from freshrpms.net and rebuilt
them. I installed the new ones, and they worked.  I don't know what was
different about my newly built version from the ones built with the same
source rpm.  I will inform Matthias Saou at freshrpms that there is a
problem with the rpm.

Now everything works fine, with two exceptions.  First, alsamixer doesn't
display properly on a virtual terminal, although it does work fine in an
xterm.  I don't know if it is related to Red Hat's utf8 problem.  Other
curses programs have problems with that.

The other problem is that after a reboot, the modules aren't loaded until
X is started.  I guess when esd starts they are loaded, but when I use cdp
or aplay they don't get loaded.  I'm not sure what the right way to do
this is.  I guess Red Hat would probably say "Start X.", but that doesn't
seem right.  I created a file /etc/rc.modules, which the RH init scripts
run.  I see references to an "alsasound" init script, but it seems to no
longer be distributed.