🚀 go-pugleaf

In comp.os.linux.help 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

> 1.  I've rebuilt my kernel a few times with ok results.  This time, I

Don't do this. There is no need, and you are very likely to make a mess.

> rebuilt it to compile the sound stuff as a module and to compile the

It was already a module, and the es1371 module (and the es1370) was
already there.

> es1371 module. lspci -v showed that I have an es1371

> 00:0d.0 Multimedia audio controller: Ensoniq ES1371 (rev 07)

Well, probably.

>         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

Fine in some senses, but not what you want to do to test. Just load the
driver and see what it says. And doesn't the es1371 take some options?

> 3.  Recompilation went ok, and when I boot with the new kernel, I see

Please do NOT recompile.

> 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

well, the joystick is a mess. Never mind.

> es1371: codec vendor ^@^@^@ revision 0

Uh huh. You seem to have messed up the compile, or the card is messed
up, or the source is. This is a mess. It should be revision 7, surely?

> es1371: codec features none
> es1371: stereo enhancement: no 3D stereo enhancement

A straight zero from trying to talk to the card. Code wrong, card
wrong, compile wrong, or computer wrong.

> 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've seen some mail on this,

kmsg? You mean syslog?

> but nothing conclusive.  BTW, my kernel version is 2.2.12-20.

> - I can't play anything using mpg123.  It just sits there forever.

Not a test. 

> After I control-C out, and look at /proc/kmsg, I see this

Why? Just use dmesg.

>         <7>es1371: dma timed out??

Very probably. Your card is not talking over dma, apparently.

Try the alsa drivers. I never had the sensation that the kernel drivers
for the es137x did too much. OTOH I know that the alsa drivers work
fine.

And do not recompile the kernel. There are several indications here
that you are doing it wrong, possibly using the wrong compiler.

Peter