🚀 go-pugleaf

Hi,

It seems i am nearly in the same situation as you and everything works
fine in my case.
levels are not exactely the same.

> 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
> 

00:0b.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev
06)
	Subsystem: Ensoniq Creative Sound Blaster AudioPCI64V, AudioPCI128
	Flags: bus master, slow devsel, latency 32, IRQ 12
	I/O ports at e800
	Capabilities: [dc] Power Management version 1


> 2.  I added this line to /etc/conf.modules
> 
>         alias sound es1371
> 

not important as long as the module is loaded when needed.
( a help to tell the kernel which module to load )


> 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

es1371: version v0.22 time 18:32:55 Dec  1 2000
es1371: found chip, vendor id 0x1274 device id 0x1371 revision 0x06
es1371: found es1371 rev 6 at io 0xe800 irq 12
es1371: features: joystick 0x0
es1371: codec vendor   v (0x838476) revision 9 (0x09)
es1371: codec features 18bit DAC 18bit ADC
es1371: stereo enhancement: SigmaTel SS3D


> 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

strange...

> messages being written in /proc/kmsg.  I've seen some mail on this,
> but nothing conclusive.  BTW, my kernel version is 2.2.12-20.

Mine is 2.2.16-9.
 
> - 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.

My card is posterior to yours. So, you should maybe consider upgrading
your kernel to 2.2.16 or 17 ?
Beware: it is not so hard but it's very easy to do a mess.