From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001520]: Soundchip was not detected
Date: Fri, 17 Mar 2006 18:42:18 +0100 [thread overview]
Message-ID: <4ad5d91d9483bd4765bedc6e413cb782@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1520>
======================================================================
Reported By: Henne
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1520
Category: ISA - cs4236
Reproducibility: always
Severity: feature
Priority: normal
Status: new
Distribution: Slackware 9.0
Kernel Version: 2.6.14-rc4
======================================================================
Date Submitted: 11-01-2005 10:35 CET
Last Modified: 03-17-2006 18:42 CET
======================================================================
Summary: Soundchip was not detected
Description:
I have an HP Omnibook 5700 CTX with some CS423x chip onboard, which is not
detected by alsaconf. I did not find the ids in cs4236.c so I think the
Pnp ID's
must added to this file.
======================================================================
----------------------------------------------------------------------
tiwai - 03-17-06 12:14
----------------------------------------------------------------------
First, the PnP stuff seems to have a problem with recent kernels. It got
fixed in the latest 2.6.16-rc. Please try it.
Also, build ALSA driver (use the CVS version instead of 1.0.11rc3) with
--with-debug=detect option. It will give you more debug messages. At
least, the driver shows the resources assigned by pnp, so you can compare
with the desired values.
----------------------------------------------------------------------
Henne - 03-17-06 18:42
----------------------------------------------------------------------
I tried that(2.6.16-rc6,alsa-(driver/kernel)cvs), but it doesnt work. I
also tried every configuration in the BIOS (Fastboot and PnP), but
everytime I get EBUSY on ALSA, but OSS works.
I compared the sources of the drivers and noticed that the OSS-driver uses
another initialisation-routine, which writes a magic number to the chip.
I looked at the spec of the CS4232, where this kind of init is described,
too.
Issue History
Date Modified Username Field Change
======================================================================
11-01-05 10:35 Henne New Issue
11-01-05 10:35 Henne Distribution => Slackware 9.0
11-01-05 10:35 Henne Kernel Version => 2.6.14-rc4
11-08-05 18:48 tiwai Note Added: 0006637
11-08-05 21:00 Henne Note Added: 0006643
11-12-05 19:33 Henne Note Added: 0006688
11-15-05 10:10 Henne Note Added: 0006729
02-06-06 09:34 Henne Note Added: 0007944
03-16-06 13:57 Henne Note Added: 0008602
03-17-06 12:14 tiwai Note Added: 0008642
03-17-06 18:42 Henne Note Added: 0008650
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-03-17 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 17:42 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 13:59 [ALSA - driver 0001520]: Soundchip was not detected bugtrack
2006-04-23 22:27 bugtrack
2006-03-17 11:14 bugtrack
2006-03-16 12:57 bugtrack
2006-02-06 8:34 bugtrack
2005-11-15 9:10 bugtrack
2005-11-12 18:33 bugtrack
2005-11-08 20:00 bugtrack
2005-11-08 17:48 bugtrack
2005-11-01 9:35 bugtrack
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=4ad5d91d9483bd4765bedc6e413cb782@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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