From: Takashi Iwai <tiwai@suse.de>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: "Ivan N. Zlatev" <contact@i-nz.net>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2/4] 2.6.23-rc4: known regressions
Date: Tue, 04 Sep 2007 10:36:06 +0200 [thread overview]
Message-ID: <s5hzm02vnd5.wl%tiwai@suse.de> (raw)
In-Reply-To: <46DC6D2A.9070306@m3y3r.de>
At Mon, 03 Sep 2007 22:23:06 +0200,
Thomas Meyer wrote:
>
> Takashi Iwai schrieb:
> > At Wed, 29 Aug 2007 18:42:56 +0300,
> > Ivan N. Zlatev wrote:
> >
> > ... but without the hardware :-<
> >
> > IMO, this is actually no real regression. In the earlier verison, you
> > didn't have controls for multiple outputs, thus the mixer control was
> > named as Master. Now you do have multiple individual controls, and
> > thus there is no master any more, instead. That's the trade-off.
> >
> Konnichiwa.
>
> Ok. Seen from this viewpoint this is no real regression. But do you have
> an idea how can i fix my setup?
>
> Currently i have these .Xmodmap key bindings:
>
> keycode 174 = XF86AudioLowerVolume
> keycode 176 = XF86AudioRaiseVolume
> keycode 160 = XF86AudioMute
>
> Some kde component while take care of the "XF86AudioLowerVolume" and
> "XF86AudioRaiseVolume" events and change the value of the "master"
> volume control.
>
> This is still happening with 2.6.23-rc5, but the master volume, stopped to be connected with the build-in speakers.
> When i connect headphones to my notebook the "MacBook-Volume-Up" and "MacBook-Volume-Down" keys still work, but they stopped to work with the build-in speaker, but will work with the headphones plugged in.
>
> The problem is, that i use the build-in speakers more often than the headphones.
> When a headphone is connected the build-in speakers go silent.
>
> And i agree with Mr. Juhl that a master volume control should control both outputs, i.e. built-in speakers and headphones.
>
> Any ideas?
The key events above are just event labels, and it's up to the desktop
system how they are interpreted. Most desktop systems like KDE or
GNOME should have the dedicated settings. They can be set up to
change the multiple volumes as a single action, but I'm not sure about
the details.
Alternatively, you can assign "PCM" volume, which controls usually all
digital output (in software).
Takashi
next prev parent reply other threads:[~2007-09-04 8:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46D58CC6.4020605@googlemail.com>
2007-08-29 15:27 ` Michal Piotrowski
2007-08-29 15:42 ` Ivan N. Zlatev
2007-08-29 15:54 ` Takashi Iwai
2007-08-29 22:34 ` Bill Davidsen
2007-09-02 12:19 ` Jesper Juhl
2007-09-04 8:30 ` Takashi Iwai
2007-09-03 20:23 ` Thomas Meyer
2007-09-04 8:36 ` Takashi Iwai [this message]
2007-08-30 8:21 ` Danny ter Haar
2007-08-31 22:01 ` Len Brown
2007-08-29 15:27 ` [3/4] " Michal Piotrowski
2007-08-29 21:54 ` [NFS] " J. Bruce Fields
2007-08-29 15:27 ` [4/4] " Michal Piotrowski
2007-08-30 10:42 ` Soeren Sonnenburg
2007-09-02 22:33 ` Michal Piotrowski
2007-09-03 6:12 ` Arkadiusz Miskiewicz
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=s5hzm02vnd5.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=akpm@linux-foundation.org \
--cc=contact@i-nz.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=thomas@m3y3r.de \
/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
all inboxes | Powered by JetHome®