On Sun, Mar 23, 2014 at 07:06:51PM +0100, Alexandre Ratchov wrote:
On Sun, Mar 23, 2014 at 11:38:11AM -0600, Theo de Raadt wrote:
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the best option.
Do you have a stereo
previously on this list Alexandre Ratchov contributed:
I was talking about raising initial hardware volume and lowering
the initial software volume (current defaults are the opposite)
My dads a bit of an audio junkie having built his first record player
when he was 14 and he tells me
On 3/24/14 7:01 AM, Alexandre Ratchov wrote:
I was talking about raising initial hardware volume and lowering
the initial software volume (current defaults are the opposite). I
agree that it doesn't make sense to have everything cranked.
Not that my opinion is worth anything, but I strongly
If you're trying to surf the web one handed in the basement after your family
goes to sleep you want the hardware muted by default.
On Sun, Mar 23, 2014 at 10:50:21AM +0100, Remi Locherer wrote:
On Sat, Mar 22, 2014 at 04:31:22PM -0600, Theo de Raadt wrote:
Date: Sat, 22 Mar 2014 21:49:19 +0100 (CET)
From: remi.loche...@relo.ch
With the snapshot from March 22 the volume keys on my ThinkPad
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the best option.
When I do that, the audio circuits pick up noise from the hard
drive. So there is backgorund noise all the time, even when I am
not doing audio.
If hardware
On Sun, Mar 23, 2014 at 14:22, Alexandre Ratchov wrote:
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the best option.
Strongest possible disagree. The keyboard beep on my thinkpads at full
volume is mind shattering. Among other
On Sun, Mar 23, 2014 at 14:22, Alexandre Ratchov wrote:
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the best option.
Strongest possible disagree. The keyboard beep on my thinkpads at full
volume is mind shattering.
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the best option.
Do you have a stereo system connected to your PC? I would not
made this the default. Start low and if you want a loud default
setting, use mixerctl.conf
If hardware
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the best option.
Do you have a stereo system connected to your PC? I would not
made this the default. Start low and if you want a loud default
setting, use mixerctl.conf
So that is
On Sun, Mar 23, 2014 at 11:52:49AM -0400, Ted Unangst wrote:
On Sun, Mar 23, 2014 at 14:22, Alexandre Ratchov wrote:
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the best option.
Strongest possible disagree.
so, diff to
On Sun, Mar 23, 2014 at 11:52:49AM -0400, Ted Unangst wrote:
On Sun, Mar 23, 2014 at 14:22, Alexandre Ratchov wrote:
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the best option.
Strongest possible disagree.
On Sun, Mar 23, 2014 at 11:56:44AM -0600, Theo de Raadt wrote:
On Sun, Mar 23, 2014 at 11:52:49AM -0400, Ted Unangst wrote:
On Sun, Mar 23, 2014 at 14:22, Alexandre Ratchov wrote:
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
On Sun, Mar 23, 2014 at 11:38:11AM -0600, Theo de Raadt wrote:
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the best option.
Do you have a stereo system connected to your PC? I would not
made this the default. Start low
On Sun, Mar 23, 2014 at 18:53, Alexandre Ratchov wrote:
On Sun, Mar 23, 2014 at 11:52:49AM -0400, Ted Unangst wrote:
On Sun, Mar 23, 2014 at 14:22, Alexandre Ratchov wrote:
So we should take all our hardware mixers, and crank them to full
volume right at boot time.
IMO, this is the
Slamming outputs.master=255 would be way worse than the current
situation. There are sounds, like the beep made when suspending and
resuming, that do not go through sndiod. Maxing out the hardware volume
is not a viable option.
suspend/resume and text console beeps usually run through
On Sun, Mar 23, 2014 at 18:24, Miod Vallat wrote:
Slamming outputs.master=255 would be way worse than the current
situation. There are sounds, like the beep made when suspending and
resuming, that do not go through sndiod. Maxing out the hardware volume
is not a viable option.
Date: Sun, 23 Mar 2014 14:51:24 -0400
From: Ted Unangst t...@tedunangst.com
On Sun, Mar 23, 2014 at 18:24, Miod Vallat wrote:
Slamming outputs.master=255 would be way worse than the current
situation. There are sounds, like the beep made when suspending and
resuming, that do not go
On Sun, Mar 23, 2014 at 02:27:57PM +0100, Alexandre Ratchov wrote:
On Sun, Mar 23, 2014 at 10:50:21AM +0100, Remi Locherer wrote:
On Sat, Mar 22, 2014 at 04:31:22PM -0600, Theo de Raadt wrote:
Date: Sat, 22 Mar 2014 21:49:19 +0100 (CET)
From: remi.loche...@relo.ch
Synopsis: volume keys not working on thinkpad x201
Category: kernel
Environment:
System : OpenBSD 5.5
Details : OpenBSD 5.5-current (GENERIC.MP) #16: Sat Mar 22 01:04:40
MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=relo.ch;
s=relo.ch-dec2013; t=1395521365;
bh=KDZL4Qy+ccBjd0+xefXm0iLbwWEZHI4Iu3fQGzrl1iA=;
h=Date:Message-Id:To:Subject:From:Cc:Reply-To;
b=NKOibw5wzjqXx1J8o4fy1FLpQ6+FfabL0zr7kgluhyyV/jBfAeNDqqQpTZr5lmniW
Date: Sat, 22 Mar 2014 21:49:19 +0100 (CET)
From: remi.loche...@relo.ch
With the snapshot from March 22 the volume keys on my ThinkPad
x201 do not work anymore. mixerctl still works. Before I was
running the snapshot from Feb 3 with which the volume keys
worked.
22 matches
Mail list logo
