ESS1988 Chipset using RedHat 9 and Compaq PC(old one)

jatcan
jatcan used Ask the Experts™
on
Hey guys,

My boss is trying to setup his sound card on RedHat.

He has compiled the maestro3.o driver from src and make/make install blah...

When he does insmod he receives these errors:

/lib/modules/2.4.20-8/kernel/drivers/sound/maestro3.o: init_modules: No such device
/lib/modules/2.4.20-8/kernel/drivers/sound/maestro3.o insmod
/lib/modules/2.4.20-8/kernel/drivers/sound/maestro3.o:failed
/lib/modules/2.4.20-8/kernel/drivers/sound/maestro3.o: insmod sound-slot-0 failed



It looks to me like the module is not being inserted becaue the device itself is not being detected, however, I am by no means an exeprt on linux(YET that is...:-)

I DO beleive he has an on-board sound card; I will confirm this this morning and post it here.

SO, any ideas on how to proceed from here?

This may bhe a long question because he has to go home to do whatever you suggest and then email me the results or pass them along in the morning.
Patitence would be good for whomever is going to attempt to help us. But I will make it worth your while in points and grading.

Cheers,

Jatcan
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
If it's an old Compaq, chances are great it has some ess1688 or ess18xx gunk on it.
Try
modprobe sb io=0x220 irq=5 dma=1 dma16=0 mpu_io=0x330
... or whatever is appropriate for the chip. You can usually determine this from the BIOS or "setup partition".
modprobe opl3 io=0x388
will load the abominably bad esfm synth driver:).

If this returns without any errors, and you can "play <somesoundfile>", you should just edit /etc/modules.conf and add an appropriate
alias sound-slot-0 sb
options sb io=0x220 .... etc

-- Glenn

Author

Commented:
I have confirmed that the ess1988 sound card is NOT an onboard device. It is actually located in pci slot 3.

Does this change anything in the above suggestion?

Thanks for reponse.


Cheers,

jatcan

Author

Commented:
AND, I am afraid Gelnn, that I have never edited any sound config files manually...lacking in knowledge there..but I am a young jedi who is listening attentively to your instructions Yoda!

please elaborate on the alias entry and the comand

modprobe sb io=0x220 irq=5 dma=1 dma16=0 mpu_io=0x330

I can get the io from where again...not in BIOS I assume since this is not an onboard device...?
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

Author

Commented:
He cannot play any sounds whatsoever, not even the system bell is audible, but the system reports the sound card as being setup properly when /proc/pci is viewed.
Ok, so it's not an onboard thingy (I've got a bunch of ol' deskpros, all sporting some ess or other... Mostly onboard, but some with an es1869 or somesuch on an adding board). If you look at the card, does it say something about maestro3, allegro or ES1988? If it says AudioDrive or ES1[678]XX (you do the permutations:-), it should work with the kernel OSS soundblaser driver sb, as noted above, else ... it would be maestro3 (or maestro or (shudder) esssolo1).

There shouldn't be a need to build the maestro3 driver from source, it's part of the kernel shipping with RH9 (BTW, there is a kernel upgrade available -> 2.4.20-20.9 that you might consider applying).

The alias is just so that when a need for a sound device arises, it will be automatically loaded into the kernel. If one gets/installs ALSA (http://www.alsa-project.org) it contains an alternate driver that would entail a different modprobe/alias. Is this perhaps what your boss did? Then he shouldn't be modprobing maestro3, but rather modprobe snd-maestro3;modprobe snd-pcm-oss; etc as detailed in http://www.alsa-project.org/alsa-doc/doc-php/template.php3?company=ESS+Technology&card=ES1988&chip=ES1988&module=maestro3 ...

But primarily try determine exactly what chip this is first.

-- Glenn (who feels less than Yoda today:-)
.... reading _all_ of your comments...
That it shows in /proc/pci means that it is "detected" as a PCI card, not that the driver works properly. I'd imagine you could see there whether it's seen as a maestro, right?

Still, what I mention earlier should be fairly accurate.
If your boss indeed has installed ALSA, remember that alsa always starts with all channels muted, so you'd need unmute the master and PCM to hear any .wav output... Any mixer should do (aumix, amixer, alsamixer ...:-).

-- Glenn

Author

Commented:
SH!t! Pardon my french but I had the same freaking problem, took me 20 minutes to discover the stuff was muted....I gotta tell him now, he's on gaim. Thanks Glenn, won't be aorund for the weekend but I'll let you know how it all wnet on Tuesday(holiday monday in canada).

Cheers BUD!
Been there, done that... mostly:-).
Good Luck.

-- Glenn

Author

Commented:
just a quick note to let you know rthat my boss actually reads and has already checked the mute settings in kmix, everything is unmuted and full volume...see you Monday.Have a good weekend.

Author

Commented:
Thanks GNS,

I don't know if my boss ever got his sound working or not but I do appreciate all your information and help.

Appologies for the delay, completely forgot about this question.

Cheers!

J
> Appologies for the delay, completely forgot about this question.
Can happen to the best:-).

See ya'

-- Glenn

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial