At Tue, 7 Oct 2003 07:12:28 -0400 (EDT),
Adam K Kirchhoff wrote:
> 
> 
> It is a non-pnp chips...  Unfortunately, the alsaconf script was unable to
> find any legacy cards.  It asked what legacy ISA cards to probe and gave
> me the option of cs4236, cs4232, and cs4231.  I selected al three, and
> told it to try all possible DMA and IRQ combinations.
> 
> Should I take this to mean that this particular chipset isn't supported?

if you build the drivers with isapnp support, you have to pass
isapnp=0, too.  also, cport option is mandatory for cs4236.
try cport=0x538 for example.


Takashi

> 
> Adam
> 
> On Tue, 7 Oct 2003, Takashi Iwai wrote:
> 
> > At Tue, 7 Oct 2003 05:10:44 -0400 (EDT),
> > Adam K Kirchhoff wrote:
> > >
> > >
> > > Anyone? :-)
> >
> > is it an isa pnp chip, or without pnp?
> > anyway, try alsaconf script in alsa-drivers/utils directory.
> >
> >
> > Takashi
> >
> > >
> > > On Sat, 4 Oct 2003, Adam K Kirchhoff wrote:
> > >
> > > >
> > > > I have a Dell Latitude CPi with a CS4237B chipset.  I have my
> > > > modules.conf file set up with the following:
> > > >
> > > > alias char-major-116 snd
> > > > alias snd-card-0 snd-cs4236
> > > > alias char-major-14 soundcore
> > > > alias sound-slot-0 snd-card-0
> > > > alias sound-service-0-0 snd-mixer-oss
> > > > alias sound-service-0-1 snd-seq-oss
> > > > alias sound-service-0-3 snd-pcm-oss
> > > > alias sound-service-0-8 snd-seq-oss
> > > > alias sound-service-0-12 snd-pcm-oss
> > > >
> > > > options snd-cs4236 irq=5 port=0x530 dma1=1 dma2=0 mpu_port=0x330
> > > >
> > > > I know the port, irq, and dma values are correct since they work with the
> > > > cs4232 driver in the kernel source (2.4.22).  Unfortunately when I go to
> > > > start alsa, I get:
> > > >
> > > > [ [EMAIL PROTECTED] - /home/adamk ]: /etc/rc.d/rc.alsa
> > > > Loading ALSA kernel modules.
> > > > /lib/modules/2.4.22/kernel/sound/isa/cs423x/snd-cs4236.o: init_module: No such 
> > > > device
> > > > /lib/modules/2.4.22/kernel/sound/isa/cs423x/snd-cs4236.o: Hint: insmod
> > > >         errors can be caused by incorrect module parameters, including invalid 
> > > > IO
> > > >         or IRQ parameters. You may find more information in syslog or the
> > > >         output from dmesg
> > > >
> > > > Any ideas?
> > > >
> > > > Adam
> > > >
> > > >
> > > >
> > > >
> > > > -------------------------------------------------------
> > > > This sf.net email is sponsored by:ThinkGeek
> > > > Welcome to geek heaven.
> > > > http://thinkgeek.com/sf
> > > > _______________________________________________
> > > > Alsa-user mailing list
> > > > [EMAIL PROTECTED]
> > > > https://lists.sourceforge.net/lists/listinfo/alsa-user
> > > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > Alsa-user mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/alsa-user
> > >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Alsa-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/alsa-user
> >
> 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to