🚀 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

Sorry peter, I don't agree.
If you want good performance you have to compile your own kernel!!!!!
Matthias

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

Matthias Rhinow wrote:
> 
> Sorry peter, I don't agree.
> If you want good performance you have to compile your own kernel!!!!!
> Matthias


My SB 128 PCI uses the es1370 module. They must have changed chipsets
somewhere along the way.

-- 
Confucius say: He who play in root, eventually kill tree.
Registered with the Linux Counter.  http://counter.li.org
ID # 123538
Completed more work units than 98.870% of seti users. +/- 0.01%

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.

On Thu, 07 Dec 2000, David wrote:
>Matthias Rhinow wrote:
>> 
>> Sorry peter, I don't agree.
>> If you want good performance you have to compile your own kernel!!!!!
>> Matthias
>
>
>My SB 128 PCI uses the es1370 module. They must have changed chipsets
>somewhere along the way.
>
>-- 
>Confucius say: He who play in root, eventually kill tree.
>Registered with the Linux Counter.  http://counter.li.org
>ID # 123538
>Completed more work units than 98.870% of seti users. +/- 0.01%

There are about 4 different versions of this card, using at least 2 different
chipsets.  I had an early one with the es1370 chip, it worked perfectly (its in
my 11 year-olds comp now, and again works perfectly for him, in Linux and
winblows)
--
moonie ;)

Registered Linux User #175104
   (Registered at: http://counter.li.org)

KDE2
Kernel 2.4.0-test5
XFree86 4.0 Nvidia .94 drivers
RAID 0 Striped
Test-Pilots-R-Us ;)
ICQ #83003404
AIM mooniesdl3
MSN mooniesdl@hotmail.com