🚀 go-pugleaf

On Sun, 03 Dec 2000 22:18:46 GMT, rlyacht@my-deja.com wrote:

>I've got a sound blaster PCI128 card that I can't seem to get working
>with my RH 6.1 system. I've tried a lot of things and made some
>progress, but I'm stuck.  I've read in numerous places how easy it is
>to get this card to work with linux, so I must be missing something.
>I would really appreciate some help!  Here are some details:
>
>1.  I've rebuilt my kernel a few times with ok results.  This time, I
>rebuilt it to compile the sound stuff as a module and to compile the
>es1371 module. lspci -v showed that I have an es1371
>
>00:0d.0 Multimedia audio controller: Ensoniq ES1371 (rev 07)
>        Subsystem: Unknown device 1274:8001
>        Flags: bus master, slow devsel, latency 32, IRQ 12
>        I/O ports at d000
>        Capabilities: [dc] Power Management version 1
>
>2.  I added this line to /etc/conf.modules
>
>        alias sound es1371
>
>3.  Recompilation went ok, and when I boot with the new kernel, I see
>this in dmesg
>
>es1371: version v0.13 time 00:26:37 Dec  3 2000
>es1371: found adapter at io 0xd000 irq 12
>es1371: features: joystick 0x0
>es1371: codec vendor ^@^@^@ revision 0
>es1371: codec features none
>es1371: stereo enhancement: no 3D stereo enhancement

I don't know what kernel your RH 6.1 distro uses, but Linux kernel 2.2.15 fixed
a number of es1371 module incompatabilities, making the Soundblaster 128PCI
(model CT4750) usable. Prior to that, the revision 7 1371 chips weren't
supported properly.

>4.  However, when I now note the following two problems
>
>- klogd is now taking 99% of my CPU.  However I don't see lots of
>messages being written in /proc/kmsg. 

I don't think that klogd is being impacted by your sound problem here. P'haps
there are other problems as well.

> I've seen some mail on this,
>but nothing conclusive.  BTW, my kernel version is 2.2.12-20.

You just answered the question. Upgrade to 2.2.15 or better (as always, be
careful with kernel upgrades, they can be tricky).

>- I can't play anything using mpg123.  It just sits there forever.
>After I control-C out, and look at /proc/kmsg, I see this
>
>        <7>es1371: dma timed out??

>I tried to run sndconfig, which correctly identified the es1371, but
>that also hung after it tried to play a test sound.
>
>5.  Also, I get this
>
>[root@bluemasq robt]# ls -l /dev/sndstat
>crw-rw-rw-   1 root     root      14,   6 May 16  2000 /dev/sndstat
>[root@bluemasq robt]# cat /dev/sndstat
>cat: /dev/sndstat: No such device
>[root@bluemasq robt]#

Yah, apparently the es1371 module doesn't support /dev/sndstat (at least that's
what happens on my Slackware kernel 2.2.13 system as well). The
Documentation/sound/es1371 document doesn't explain much, so it's
trial-and-error time (you might have guessed that I'm going through this as
well; it looks like I'm just further along than you). I believe that
/proc/sndstat (or something like that) substitutes for /dev/sndstat in this
case.



Lew Pitcher
IT Consultant, Development Services
Toronto Dominion Bank Financial Group

(Opinions expressed are my own, not my employers')