From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000312]: MasterVolume & Headphone volume switched...
Date: Wed, 30 Jun 2004 16:40:19 +0200 [thread overview]
Message-ID: <fa7e0afb10ff535c5c0b01d88a9bf072@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=0000312
======================================================================
Reported By: subdude
Assigned To:
======================================================================
Project: ALSA - driver
Bug ID: 312
Category: PCI - via82xx
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Slackware Current
Kernel Version: 2.4.26
======================================================================
Date Submitted: 05-29-2004 11:11 CEST
Last Modified: 06-30-2004 16:40 CEST
======================================================================
Summary: MasterVolume & Headphone volume switched...
Description:
The onboard sound chip is called a VIA 8233/8235.
I am running dxs_support=4
I have tried:
ac97_quirks=-1 thru 3 = no effect
======================================================================
----------------------------------------------------------------------
subdude - 06-01-2004 07:19 CEST
----------------------------------------------------------------------
The motherboard is an ECS L7VMM2 uATX with onboard VIA VT8375 Northbridge
and VT8235 Southbridge chipset.
The CPU is an AMD XP2400+ with 512 MByte 266 DDRAM.
The AGP X4 socket has a nVidia 64 MByte MX-440 gpu.
The sound chip is identified as a VIA 8233/8235.
Sound is excellent at dxs_support=4.
The ONLY problem is the Headphone Volume is really the Master Volume.
How do I fix????
----------------------------------------------------------------------
tiwai - 06-30-2004 16:40 CEST
----------------------------------------------------------------------
Please show the output of lspci -nv (for the entry of VIA823x only).
About the HP output - I guess you mistyped:
it's ac97_quirk (without 's').
Try ac97_quirk=1 or ac97_quirk=2.
Bug History
Date Modified Username Field Change
======================================================================
05-29-04 11:11 subdude New Bug
05-29-04 11:11 subdude Distribution => Slackware Current
05-29-04 11:11 subdude Kernel Version => 2.4.26
05-29-04 11:12 subdude Bug Monitored: subdude
06-01-04 07:19 subdude Bugnote Added: 0001288
06-30-04 16:40 tiwai Bugnote Added: 0001359
======================================================================
-------------------------------------------------------
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-06-30 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 14:40 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-10 2:39 [ALSA - driver 0000312]: MasterVolume & Headphone volume switched noreply
2004-07-15 9:28 noreply
2004-09-24 11:31 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=fa7e0afb10ff535c5c0b01d88a9bf072@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.