From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000370]: CMedia 8768 Support
Date: Wed, 7 Jul 2004 05:03:23 +0200 [thread overview]
Message-ID: <23583871239fae53d87f8fe14347e11d@bugtrack.alsa-project.org> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000370
======================================================================
Reported By: drbobguy
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Bug ID: 370
Category: PCI - cmipci
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
Distribution: Gentoo
Kernel Version: 2.6.7
======================================================================
Date Submitted: 07-07-2004 04:59 CEST
Last Modified: 07-07-2004 05:03 CEST
======================================================================
Summary: CMedia 8768 Support
Description:
I've recently built a new computer with an on-board CMedia 8768 chip. This
chip is not listed as one of the supported CMedia chips (8738, etc.),
although I suspect that is because it is so new. Just wanted to let you
guys know it apparently doesn't work with the standard cmipci driver (at
least I think I'm doing everthing correctly -- I have a decent amount of
Linux experience but I'm no guru). Here is what I see though:
The card is recognized in /proc/asound as a CMedia 8738M6. However, if I
use a mixer like amixer or gnome-alsamixer none of the mixer settings I
change will take effect (and I am running these as root).
Any advice or comments would be appreciated. I'd be happy to help if you
think there is a possible fix.
======================================================================
----------------------------------------------------------------------
drbobguy - 07-07-2004 05:03 CEST
----------------------------------------------------------------------
By the way I'm on an AMD 64 machine if that makes a difference.
Bug History
Date Modified Username Field Change
======================================================================
07-07-04 04:59 drbobguy New Bug
07-07-04 04:59 drbobguy Distribution => Gentoo
07-07-04 04:59 drbobguy Kernel Version => 2.6.7
07-07-04 05:03 drbobguy Bugnote Added: 0001390
======================================================================
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-07-07 3:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 3:03 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 11:44 [ALSA - driver 0000370]: CMedia 8768 Support bugtrack
2005-05-24 10:36 bugtrack
2005-04-26 7:34 bugtrack
2005-04-25 9:42 bugtrack
2005-01-04 4:12 bugtrack
2004-12-25 16:13 bugtrack
2004-11-22 11:11 bugtrack
2004-10-19 3:35 bugtrack
2004-10-18 21:00 bugtrack
2004-10-18 9:32 bugtrack
2004-10-16 5:32 bugtrack
2004-10-15 22:33 bugtrack
2004-10-14 21:57 bugtrack
2004-10-14 14:19 bugtrack
2004-10-14 14:05 bugtrack
2004-10-14 10:02 bugtrack
2004-10-13 23:24 bugtrack
2004-10-13 14:37 bugtrack
2004-10-13 14:37 bugtrack
2004-10-10 2:57 bugtrack
2004-10-10 2:48 bugtrack
2004-10-09 7:29 bugtrack
2004-10-08 13:36 bugtrack
2004-10-08 13:26 bugtrack
2004-10-08 10:49 bugtrack
2004-10-08 3:17 bugtrack
2004-07-07 2:59 noreply
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=23583871239fae53d87f8fe14347e11d@bugtrack.alsa-project.org \
--to=noreply@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.