public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Alsa Problem With Kernel 2.6.37
Date: Sat, 8 Jan 2011 14:41:23 -0500	[thread overview]
Message-ID: <20110108144123.693d9d60.frank.peters@comcast.net> (raw)
In-Reply-To: <pan.2011.01.08.18.10.03@cox.net>

On Sat, 8 Jan 2011 18:10:03 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> 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



  reply	other threads:[~2011-01-08 20:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08 16:28 [gentoo-amd64] Alsa Problem With Kernel 2.6.37 Frank Peters
2011-01-08 17:20 ` [gentoo-amd64] " Nikos Chantziaras
2011-01-08 18:22   ` Res: " Axial Astaroth
2011-01-08 18:10 ` Duncan
2011-01-08 19:41   ` Frank Peters [this message]
2011-01-08 21:20     ` Martin Herrman
2011-01-08 23:11       ` Frank Peters
2011-01-09  6:06         ` Duncan
2011-01-09 12:03         ` Rich Freeman
2011-01-09  1:08 ` [gentoo-amd64] Alsa Problem With Kernel 2.6.37[Solved] Frank Peters
2011-01-22 12:00   ` Zhu Sha Zang
2011-01-22 15:24     ` Frank Peters
2011-01-22 18:13       ` Zhu Sha Zang

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=20110108144123.693d9d60.frank.peters@comcast.net \
    --to=frank.peters@comcast.net \
    --cc=gentoo-amd64@lists.gentoo.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