From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001709]: 5.1 doesn't work
Date: Thu, 5 Jan 2006 22:02:55 +0100 [thread overview]
Message-ID: <2ac4b1c551e8d45fbe3f7179be07ca96@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1709>
======================================================================
Reported By: piezo
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1709
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Fedora Core 4
Kernel Version: 2.6.11-1.1369
======================================================================
Date Submitted: 01-04-2006 13:50 CET
Last Modified: 01-05-2006 22:02 CET
======================================================================
Summary: 5.1 doesn't work
Description:
I'm new to linux. I've been googling for a awnser to this problem for a
week now. found a few with the same sort of problems but no awnsers.
I can get sterio sound but not 5.1 surround. This is very irritating as I
bought a Audity2 soundcard for the purpose of using it's 5.1 sound
capability.
initially xine kept telling me that another process was using the PCM
device. found how to fix this. using
======================================================================
----------------------------------------------------------------------
piezo - 01-05-06 00:23
----------------------------------------------------------------------
"Sound Blaster Audigy 2 value" pci card
followed the Alsa setup instructions.
detected correctly (SB0400)
can only seem to use it in sterio or (with fixes) fake 5.1 (which is
really sterio duplicated).
----------------------------------------------------------------------
rlrevell - 01-05-06 22:02
----------------------------------------------------------------------
2.6.11 is way too old for such a new device. Try a newer kernel.
Issue History
Date Modified Username Field Change
======================================================================
01-04-06 13:50 piezo New Issue
01-04-06 13:50 piezo Distribution => Fedora Core 4
01-04-06 13:50 piezo Kernel Version => 2.6.11-1.1369
01-05-06 00:23 piezo Note Added: 0007461
01-05-06 22:02 rlrevell Note Added: 0007483
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-05 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 21:02 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-18 12:40 [ALSA - driver 0001709]: 5.1 doesn't work bugtrack
2006-01-04 23:23 bugtrack
2006-01-04 12:50 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=2ac4b1c551e8d45fbe3f7179be07ca96@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