On Sat, 8 Jan 2011 18:10:03 +0000 (UTC)
Duncan <1i5t5.duncan@...> wrote:


>  Are the devices actually 
> showing up in /dev/?  Assuming you use udev, maybe it's the problem?  If 
> you run them as modules not built-in, are the alsa kernel modules 
> themselves actually loading?

First, I want to thank all those who took the time to confirm (even though,
from my perspective, it was all bad news :-( ).

The modules are loading without problem.  For example, the kernel
log reports the following:

kernel: ICE1712 0000:04:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21

Both lspci and alsa-info.sh show that the sound card is there, and
this would not happen if the modules were not being properly loaded.
In other words the kernel can detect the card.

I don't use udev.  All modules are loaded manually and the devices
in /dev are permanent.  Permissions are also as they should be,
because an alsa script was used to create the devices.

The problem seems to be with the applications.  The open() routine
reports back "no device found."  Now, open() is a glibc routine but
it will ultimately call the kernel routines that are, I believe, contained
in the alsa modules.  Since kernel 2.6.36 works, it most likely is a
kernel 2.6.37 issue.

I'll have to recompile 2.6.37 with debugging output and see what
happens.

Frank Peters