Bug 82012 - (SOUND EMU10K1)OSS use of SoundBlaster out ports 'wrong'
(SOUND EMU10K1)OSS use of SoundBlaster out ports 'wrong'
Status: CLOSED DUPLICATE of bug 85827
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-01-16 06:01 EST by Christian Schaller
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:51:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Christian Schaller 2003-01-16 06:01:22 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
I have a pc I dual boot with windows, and this computer has a Sound Blaster Live
card. The sound blaster live has two output ports on the back. Windows use one
port as default and Red Hat another. Which means that I need to switch the
speaker cable between the two ports when switchin operating system. (Or dig in
and find out how to reconfigure the port used.).

Anyway I installed ALSA a couple of days ago and found that it defaults to the
same port as Windows does. Which leads me to think that the OSS driver in Red
Hat should do the same. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual Results:  na

Expected Results:  na

Additional info:

Comment 1 Christian Schaller 2003-02-26 14:10:54 EST
Will this be changed for Red Hat 8.1?
Comment 2 Alan Cox 2003-06-10 13:49:19 EDT
The sb live tools on the net for mixer control etc should be enough to let you
change the channel assignments

*** This bug has been marked as a duplicate of 85827 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:51:11 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.