From: Vojtech Pavlik <vojtech@suse.cz>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.32 doesn't beep?
Date: Wed, 28 Aug 2002 22:30:05 +0200 [thread overview]
Message-ID: <20020828223005.A21207@ucw.cz> (raw)
In-Reply-To: <15725.11451.335811.149069@kim.it.uu.se>; from mikpe@csd.uu.se on Wed, Aug 28, 2002 at 10:04:11PM +0200
On Wed, Aug 28, 2002 at 10:04:11PM +0200, Mikael Pettersson wrote:
> Vojtech Pavlik writes:
> > On Wed, Aug 28, 2002 at 03:00:56PM +0200, Mikael Pettersson wrote:
> >
> > > Linus Torvalds 2.5.32 announcement:
> > > > ... The input layer switch-over may also end up being a bit painful
> > > > for a while, since that not only adds a lot of config options that you
> > > > have to get right to have a working keyboard and mouse (we'll fix that
> > > > usability nightmare), but the drivers themselves are different and there
> > > > are likely devices out there that depended on various quirks.
> > >
> > > I've noticed that in 2.5.32 with CONFIG_KEYBOARD_ATKBD=y, the kernel no
> > > longer beeps via the PC speaker. Both (at the console) hitting DEL or BS
> > > at the start of input or doing a simple echo ^G are now silent.
> > >
> > > Call me old-fashioned, but I want those beeps back :-)
> >
> > 2.5.32 still has quite complex input core config options - sorry, my
> > fault, and I'll fix it soon. You have to enable CONFIG_INPUT_MISC and
> > CONFIG_INPUT_PCSPKR.
>
> That worked. Thanks.
>
> Another issue: I enabled CONFIG_INPUT_MOUSEDEV_PSAUX, but /dev/psaux
> gave an ENODEV when opened. Turns out CONFIG_INPUT_MOUSEDEV is
> also required, but for some reason 'make config' let me set the
> former without also setting the latter. A bug in input's config.in?
Yes, a bug. Fixed now.
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-08-28 20:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 19:47 Linux v2.5.32 Linus Torvalds
2002-08-27 20:22 ` Stephane Wirtel
2002-08-27 20:36 ` Thunder from the hill
2002-08-27 20:48 ` Stephane Wirtel
2002-08-27 20:54 ` Gabor Z. Papp
2002-08-28 6:18 ` Jan-Benedict Glaw
2002-08-28 7:41 ` Edward Coffey
2002-08-28 8:35 ` Russell King
2002-08-27 20:43 ` Udo A. Steinberg
2002-08-27 20:47 ` Andre Hedrick
2002-08-27 20:47 ` Alexander Viro
2002-08-27 22:35 ` Alan Cox
2002-08-28 2:07 ` [PATCH] " Alexander Viro
2002-08-28 1:21 ` Arador
2002-08-28 2:17 ` Alexander Viro
2002-08-27 22:28 ` Chris Funderburg (at home)
2002-08-28 7:31 ` Linux v2.5.32 - some menuconfig oddities Helge Hafting
2002-08-28 7:43 ` Gabor Kerenyi
2002-08-28 8:14 ` Linux v2.5.32 Edward Coffey
2002-08-28 8:17 ` Writing files to remote storage Kevin Liao
2002-08-28 14:18 ` Alan Cox
2002-08-28 13:00 ` 2.5.32 doesn't beep? Mikael Pettersson
2002-08-28 13:05 ` Vojtech Pavlik
2002-08-28 13:12 ` Mikael Pettersson
2002-08-28 13:58 ` Gerhard Mack
2002-08-28 14:33 ` Jos Hulzink
2002-08-28 14:49 ` Vojtech Pavlik
2002-08-28 20:04 ` Mikael Pettersson
2002-08-28 20:30 ` Vojtech Pavlik [this message]
2002-08-29 8:41 ` Gerd Knorr
2002-08-28 17:21 ` Linux v2.5.32 Adrian Bunk
2002-08-31 16:54 ` Linux v2.5.32 (Config options to have a working keyboard) Axel Siebenwirth
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=20020828223005.A21207@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).