Bug#288005: acknowledged by developer (Re: [Pkg-alsa-devel] Bug#288005: alsa-base: Unable to use cs4237b sound card with alsa)

[Alexander Toresson]

On Sun, 02 Jan 2005 16:14:01 +0100, Thomas Hood <jdthood@aglu.demon.nl> wrote:
> On Sun, 2005-01-02 at 01:51 +0100, Alexander Toresson wrote:
> > I may have identified the problem. At:
> > http://cvs.sourceforge.net/viewcvs.py/alsa/alsa-kernel/isa/cs423x/cs4236.c?rev=1.47&view=markup
> >
> > I can see these lines:
> >
> >       /* Crystal Semiconductors CS4237B */
> >       { .id = "CSC4637", .devs = { { "CSC0000" }, { "CSC0010" }, { "CSC0003" } } },
> >
> > They correspond to my sound card. Well, this or the Crystal 3D.
> > The thing is, the CSC0000 and CSC0010 pnp 'entries' (don't know what
> > they are called), do exist in my lspnp listing. CSC0003 do[es]n't.
> 
> The table you referred to does contain other entries whose devs do match
> yours, such as this one:
> 
>         /* Dell P410 motherboard - CS4236B */
>         { .id = "CSC6835", .devs = { { "CSC0000" }, { "CSC0010" } } },
> 
> 
> > As I understand it (I haven't found info about it), devices are
> > identified by checking if the corresponding entries are in the pnp
> > listing. If that is the case, well, here's the problem.
> 
> Looking at /usr/src/kernel-source-2.6.9/drivers/pnp/card.c I see that
> the match_card function checks for the presence of all the devices in
> the .devs list.  It also checks that card->id matches the .id value.
> 
> Question: What is card-id in your case?

I've got no idea. I've got no other entries, starting at CSC, other
than CSC0000 and CSC0010. Though according to
http://docs.us.dell.com/support/edocs/systems/pmojav/specs.htm my
sound card is a Crystal 4237b.

> Question: Are you actually using pnp methods for probing?
>           isapnp or pnpbios?

alsaconf, didn't find it, and as far as I know, it uses pnp. I tried
to run isapnp, though didn't understand what file I was supposed to
give as input. pnpbios didn't exist on my system, though so did
pnpdump.  It outputts the following:

# $Id: pnpdump_main.c,v 1.27 2001/04/30 21:54:53 fox Exp $
# Release isapnptools-1.26
# 
# This is free software, see the sources for details.
# This software has NO WARRANTY, use at your OWN RISK
# 
# For details of the output file format, see isapnp.conf(5)
# 
# For latest information and FAQ on isapnp and pnpdump see:
# http://www.roestock.demon.co.uk/isapnptools/
# 
# Compiler flags:  -DREALTIME -DHAVE_PROC -DENABLE_PCI
-DHAVE_SCHED_SETSCHEDULER -DHAVE_NANOSLEEP -DWANT_TO_VALIDATE
# 
# Trying port address 0273
# Trying port address 027b
# Trying port address 0283
# Trying port address 028b
# Trying port address 0293
# Trying port address 029b
# Trying port address 02a3
# Trying port address 02ab
# Trying port address 02b3
# Trying port address 02bb
# Trying port address 02c3
# Trying port address 02cb
# Trying port address 02d3
# Trying port address 02db
# Trying port address 02e3
# Trying port address 02eb
# Trying port address 02f3
REALTIME operation timeout exceeded - Switching to normal scheduling
# Trying port address 02fb
# Trying port address 0303
# Trying port address 030b
# Trying port address 0313
# Trying port address 031b
# Trying port address 0323
# Trying port address 032b
# Trying port address 0333
# Trying port address 033b
# Trying port address 0343
# Trying port address 034b
# Trying port address 0353
# Trying port address 035b
# Trying port address 0363
# Trying port address 036b
# Trying port address 0373
# Trying port address 037b
# Trying port address 0383
# Trying port address 038b
# Trying port address 0393
# Trying port address 039b
# Trying port address 03a3
# Trying port address 03ab
# Trying port address 03b3
# Trying port address 03bb
# Trying port address 03e3
# Trying port address 03f3
# No boards found

> Question: Does the problem go away if you load snd-cs4236 with module
>           option isapnp=0.

I've tried both with isapnp=1 and isapnp=0. It doesn't seem like any
module options affects the output of modprobe.

Regards, Alexander Toresson