Re: Audio issues on Zaurus

On Wed, 11 May 2016 22:13:53 +0200 Alexandre Ratchov wrote: > > If I use aucat or mpg123 or flac123 to play something, I get > > "pxa2x0_dma_to_fifo: bogus length 17640" on the console and the player just > > hangs there with no sound. > > now this one is fixed; the problem was

Re: dmesg -s produces no output in -current

On Fri, May 13, 2016 at 11:43:43AM +0100, Dimitris Papastamos wrote: > After I rebuilt and booted the kernel today I noticed dmesg -s > produces no output. I suspect this is to do with the recent change: Here is alternative way to fix sendsyslog(2) with LOG_CONS. I also works when /dev/console

Re: two audio beep bugs

On Fri, May 13, 2016 at 09:35:48AM -0400, Ted Unangst wrote: > Mark Kettenis wrote: > > > > I personally think the wsconsctl settings should be respected by X. > > > But perhaps we should have a more fundamental discussion about things > > first about how X should interact with wscons. There is

Re: two audio beep bugs

On 5/13/16, Ted Unangst wrote: > Mark Kettenis wrote: >> >> I personally think the wsconsctl settings should be respected by X. > >> But perhaps we should have a more fundamental discussion about things >> first about how X should interact with wscons. There is a more >>

Re: two audio beep bugs

Mark Kettenis wrote: > > I personally think the wsconsctl settings should be respected by X. > But perhaps we should have a more fundamental discussion about things > first about how X should interact with wscons. There is a more > fundamental problem here where X assumes it has full control

dmesg -s produces no output in -current

Hi everyone, After I rebuilt and booted the kernel today I noticed dmesg -s produces no output. I suspect this is to do with the recent change: If sendsyslog(2) is called with LOG_CONS before syslogd(8) has been started and before init(8) has opened the console, the kernel could

Re: two audio beep bugs

> Date: Fri, 13 May 2016 11:57:57 +0200 (CEST) > From: Mark Kettenis > > I personally think the wsconsctl settings should be respected by X. > The way the X code is structured, it is difficult to make xset(1) > control the keyboard.bell settings directly. A possible way

Re: two audio beep bugs

> Date: Fri, 13 May 2016 10:43:43 +0200 > From: Matthieu Herrb > > On Fri, May 13, 2016 at 12:56:52AM -0400, Ted Unangst wrote: > > 1. I have wsconsctl keyboard.bell.volume=0 because I don't like things > > beeping > > at me. This recently stopped working in xterm, where I

Re: two audio beep bugs

On Fri, May 13, 2016 at 12:56:52AM -0400, Ted Unangst wrote: > 1. I have wsconsctl keyboard.bell.volume=0 because I don't like things beeping > at me. This recently stopped working in xterm, where I now get a loud beep. > Related to loss of pcvt? > > I'm not sure where the failure is, but my

Re: two audio beep bugs

On 2016-05-13 00:56:52, Ted Unangst wrote: > 1. I have wsconsctl keyboard.bell.volume=0 because I don't like things beeping > at me. This recently stopped working in xterm, where I now get a loud beep. > Related to loss of pcvt? > > I'm not sure where the failure is, but my

Re: two audio beep bugs

On Fri, May 13, 2016 at 12:56:52AM -0400, Ted Unangst wrote: > 1. I have wsconsctl keyboard.bell.volume=0 because I don't like things beeping > at me. This recently stopped working in xterm, where I now get a loud beep. > Related to loss of pcvt? > > I'm not sure where the failure is, but my

Re: two audio beep bugs

On 13 May 2016 at 06:56, Ted Unangst wrote: > 1. I have wsconsctl keyboard.bell.volume=0 because I don't like things beeping > at me. This recently stopped working in xterm, where I now get a loud beep. > Related to loss of pcvt? > > I'm not sure where the failure is, but my