From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000724]: No apparent support for Creative Sounblaster 24 bit.
Date: Wed, 9 Feb 2005 08:57:23 +0100 [thread overview]
Message-ID: <73f20e69edd0b90312c2fedffe81749b@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=724>
======================================================================
Reported By: sjberryman
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 724
Category: OTHERS
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Distribution: Fedora Core1, Core2 and Suse 9.2
Kernel Version: 2.6.9 2.4.28 2.6.8
======================================================================
Date Submitted: 12-13-2004 09:21 CET
Last Modified: 02-09-2005 08:57 CET
======================================================================
Summary: No apparent support for Creative Sounblaster 24 bit.
Description:
No apparent support for Creative Sounblaster 24 bit.
Fedora does not find any sound device.
Susi finds a device but can't activate it.
======================================================================
----------------------------------------------------------------------
pzad - 02-09-05 07:25
----------------------------------------------------------------------
This card probably doesn't have AC97 too.
Search ca0106 driver for line
if ((chip->serial != 0x10061102) && (chip->serial != 0x10071102) ) { /*
The SB0410 and SB0413 do not have an ac97 chip. */
and add chip->serial of your card there too.
----------------------------------------------------------------------
sHINOBI - 02-09-05 08:57
----------------------------------------------------------------------
Errm, to be honest I'm not sure with the chip->serial number. I guess it
should be listed with lspci -nvv command. Relevant part is:
01:0d.0 Class 0401: 1102:0007
Subsystem: 1462:1009
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (500ns min, 5000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at de00 [size=32]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
BTW should be the James notified about this card?
Issue History
Date Modified Username Field Change
======================================================================
12-13-04 09:21 sjberryman New Issue
12-13-04 09:21 sjberryman Distribution => Fedora Core1, Core2
and Suse 9.2
12-13-04 09:21 sjberryman Kernel Version => 2.6.9 2.4.28 2.6.8
12-13-04 09:26 sjberryman Issue Monitored: sjberryman
12-13-04 10:07 pzad Note Added: 0002821
12-16-04 18:28 tiwai Status new => resolved
12-16-04 18:28 tiwai Resolution open => not an issue
12-16-04 18:28 tiwai Assigned To => tiwai
12-16-04 18:28 tiwai Assigned To tiwai =>
01-19-05 09:08 sjberryman Status resolved => feedback
01-19-05 09:08 sjberryman Resolution not an issue => reopened
01-19-05 09:08 sjberryman Note Added: 0003263
01-19-05 14:27 tiwai Note Added: 0003266
01-22-05 22:15 nadavkav Note Added: 0003379
01-22-05 23:20 fmoraes Note Added: 0003381
01-25-05 22:39 Kane32 Note Added: 0003411
01-26-05 13:18 nadavkav Note Added: 0003416
02-08-05 23:26 sHINOBI Issue Monitored: sHINOBI
02-08-05 23:32 sHINOBI Note Added: 0003534
02-09-05 07:25 pzad Note Added: 0003535
02-09-05 08:57 sHINOBI Note Added: 0003536
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-02-09 7:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 7:57 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-10 11:12 [ALSA - driver 0000724]: No apparent support for Creative Sounblaster 24 bit bugtrack
2005-06-13 8:25 bugtrack
2005-06-13 7:33 bugtrack
2005-06-12 13:43 bugtrack
2005-06-11 13:13 bugtrack
2005-06-11 13:11 bugtrack
2005-06-11 11:34 bugtrack
2005-06-10 16:58 bugtrack
2005-06-10 11:28 bugtrack
2005-05-28 18:07 bugtrack
2005-05-28 18:02 bugtrack
2005-05-28 14:06 bugtrack
2005-02-09 6:25 bugtrack
2005-02-08 22:32 bugtrack
2005-01-26 12:18 bugtrack
2005-01-25 21:39 bugtrack
2005-01-22 22:20 bugtrack
2005-01-22 21:15 bugtrack
2005-01-19 13:27 bugtrack
2005-01-19 8:08 bugtrack
2004-12-16 17:28 bugtrack
2004-12-13 9:07 bugtrack
2004-12-13 8:21 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=73f20e69edd0b90312c2fedffe81749b@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