Re: [Alsa-user] Cyrrus Logic Crystal CS4237B to configure

[Rene H. <ren...@ke...>]

Hulin Thibaud wrote:

> I followed your councils. About the post in text, I believe... that's
> work !

It does. It is also very much preferred if you keep the list you posted 
on in CC (using "reply to all" would've done that). That way, others can 
look in on the conversation, correct given advice, give more advice, 
learn from advice as well, and so on.

> (/lib/modules/2.6.12-10-386/kernel/sound/isa/cs423x/snd-cs4236.ko): No 
> such device

Okay...

> I suppose that I have the IsaPNP support (how can I be sure ?), because 
> I have the folder /sys/devices/pnp and pnp1.
> But I don't have the file card_id (searched with 'locate').

"locate" is not useful here. It uses a database, but /sys is a  virtual 
filesystem (meaning the files don't really "exist" on disk -- it's just 
an illusion made up by the kernel, same as /proc). Anyways, you can just 
browse around in /sys to see what's there. From the console for example 
with "mc /sys", or using whatever graphical file manager you use.

> I have only links bus and driver, and the directory power, and the files 
> id, options and resources.

Okay, that means you do have a device there it seems, as the bus and 
driver links only exist in device directories. That is, in a directory 
such as:

$ tree /sys/devices/pnp1/01:01/01:01.00
/sys/devices/pnp1/01:01/01:01.00
|-- bus -> ../../../../bus/pnp
|-- driver -> ../../../../bus/pnp/drivers/cs4236_isapnp
|-- id
|-- options
|-- power
|-- resources
`-- uevent

Please show me the output of that same "tree" command (for the directory 
where your "bus" and "driver" and id file was). Also, what does that 
"id" file say in that directory? For me:

$ cat /sys/devices/pnp1/01:01/01:01.00/id
CSCa800

The card_id file I said should be one directory up. Is that CS4237 card 
by the way the only ISA-PnP card you have in the machine?

> So, the command pnpdump conclue "No boards found"...

pnpdump is another tool which you should not be using anymore on 2.6. It 
should still work though, and it bypasses the kernel. If it isn't 
finding anything, that's very strange seeing as how apparently the 
kernel code _did_ find something. Please also just make sure the 
board(s) is/are inserted properly.

Rene.