Linux Sound subsystem development
 help / color / mirror / Atom feed
From: William Law Kar Wai <willaw79@yahoo.com>
To: linux-sound@vger.kernel.org
Subject: Re: help needed for cs423x chips
Date: Thu, 10 Dec 1998 05:28:00 +0000	[thread overview]
Message-ID: <marc-linux-sound-91334971309315@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91325015828495@msgid-missing>

Hi,
  I once successfully configured the sound for the cs4236 sound chip.
Unfortunately I forgot how to configure it, but here is something that
I might recall. I was using Redhat 5.0. I downloaded OSSfree version
3.8. I first compiled the kernel without the sound support. Then I use
the isapnp tools to configure the pnp card, of course you have to edit
the files and enable certain configurations. After that, I decompress
the ossfree sound driver in the /usr/src/linux directory. Then I
recompile the kernel using the configuration I set in the isapnp.conf.
It once worked, even the MIDI and other stuff worked. But when I
reformatted the hard disk and reinstall everything, is doesn't work at
all. You can also try to download the ALSA sound driver. I heard that
it works. It supports your sound chips. I haven't try it yet, but soon.

Trying my best to help...

William,
Running Redhat 5.1
www.redhat.com




---moc liamtoh <mackilla@hotmail.com> wrote:
>
> alright, i cant get my sound to work. i have an aopen MB with built
on 
> sound and video. sound chip says cs4235 on the chip but isapnp
detects 
> as 4236. i have tried different settings with isapnp and different 
> modules for sound support....i have also tried without modules and
just 
> ocmpiling into kernel...i have tried configuration manager alone and 
> with isapnp and modules...basically i was trying about everything i 
> could think...only problem being that i dont know that much yet and 
> therefore am running out off ideas...plus it is taking time to learn 
> stuff to try different things....not that i mind the knowledge but i 
> would like to get sound working quickly =)
> 
> so if anyone could spare the time to help i would appreciate it. i am 
> fairly knowledgeable with linux, i just mainly need to know what to 
> do...(i guess basically a brief howto sort of answer would be cool, 
> detailing the steps enough that i can understand. eg: say 
> 
> tar xvf blahblahbalh
> 
> not just "decompress with gzip and then use tar on it."
> 
> thanks again.
> 
> Joshua Kukovec
> 
> 
> 
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
> 

_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

  parent reply	other threads:[~1998-12-10  5:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-08 23:49 help needed for cs423x chips moc liamtoh
1998-12-09  0:12 ` moc liamtoh
1998-12-10  0:35 ` Matthew B. Marlowe
1998-12-10  5:28 ` William Law Kar Wai [this message]
1998-12-10  7:02 ` Etienne Grossmann
1998-12-11 16:32 ` Tony Nugent
1998-12-12 15:24 ` D Sen
1998-12-13  5:32 ` Keith Duthie
1998-12-14  4:38 ` Michael Haller
1998-12-15  8:10 ` Keith Duthie
1998-12-16  6:26 ` Keith Duthie
1998-12-16  6:26 ` Keith Duthie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-sound-91334971309315@msgid-missing \
    --to=willaw79@yahoo.com \
    --cc=linux-sound@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox