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
When this machine boots up it switches successfully to radeondrm but
when X starts the display gets garbled [1]. Switching to the console
and back again fixes the issue [2] but now the console is blank with
the cursor blinking top left corner. It still accepts input though,
and the X display is
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
Date: Sun, 23 Mar 2014 14:37:49 +0100
From: Thomas Pfaff tpf...@tp76.info
When this machine boots up it switches successfully to radeondrm but
when X starts the display gets garbled [1]. Switching to the console
and back again fixes the issue [2] but now the console is blank with
the
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
Synopsis: ehci: kernel diagnostic assertion (reg 0x3) == 0 failed
Category: amd64
Environment:
System : OpenBSD 5.5
Details : OpenBSD 5.5-current (GENERIC) #18: Sat Mar 22 22:41:35
MDT 2014
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
Date: Sun, 23 Mar 2014 17:53:47 +0100 (CET)
From: Donovan Watteau tso...@gmail.com
ehci0 at pci0 dev 3 function 3 SiS 7002 USB rev 0x00: apic 2 int 23
panic: kernel diagnostic assertion (reg 0x3) == 0 failed: file ../../../
arch/amd64/pci/pci_machdep.c, line 272
Stopped at
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
Date: Sun, 23 Mar 2014 16:57:37 +0100
From: Thomas Pfaff tpf...@tp76.info
On Sun, 23 Mar 2014 16:46:52 +0100 (CET)
Mark Kettenis mark.kette...@xs4all.nl wrote:
Date: Sun, 23 Mar 2014 14:37:49 +0100
From: Thomas Pfaff tpf...@tp76.info
When this machine boots up it switches
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.
On Sun, 23 Mar 2014 19:23:50 +0100 (CET)
Mark Kettenis mark.kette...@xs4all.nl wrote:
When this machine boots up it switches successfully to radeondrm but
when X starts the display gets garbled [1]. Switching to the console
and back again fixes the issue [2] but now the console is
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
21 matches
Mail list logo
