From owner-freebsd-questions@FreeBSD.ORG Wed Sep 22 16:49:28 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 988BE16A4CE for ; Wed, 22 Sep 2004 16:49:28 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A488F43D3F for ; Wed, 22 Sep 2004 16:49:27 +0000 (GMT) (envelope-from michaelwichmann@gmx.net) Received: (qmail 28953 invoked by uid 65534); 22 Sep 2004 16:49:25 -0000 Received: from pD9E8B0DD.dip.t-dialin.net (EHLO antares.starnet) (217.232.176.221) by mail.gmx.net (mp025) with SMTP; 22 Sep 2004 18:49:25 +0200 X-Authenticated: #9941055 From: Michael Wichmann To: freebsd-questions@freebsd.org Date: Wed, 22 Sep 2004 18:49:26 +0200 User-Agent: KMail/1.7 References: <200409221505.37494.michaelwichmann@gmx.net> <20040922150007.GD3633@gentoo-npk.bmp.ub> In-Reply-To: <20040922150007.GD3633@gentoo-npk.bmp.ub> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6230946.qYyL9EYXZo"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200409221849.32675.michaelwichmann@gmx.net> cc: nkinkade@ub.edu.bz Subject: Re: Num lock status on boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2004 16:49:28 -0000 --nextPart6230946.qYyL9EYXZo Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 22 September 2004 17:00, Nathan Kinkade wrote: > On Wed, Sep 22, 2004 at 03:05:22PM +0200, Michael Wichmann wrote: > > Hello everyone, > > > > Just a quick question about this little thing, that bugs me from > > time to time:) Num-lock ist turned off by default after I boot up > > FreeBSD 5.2.1. Is there any way to enable it by default? > > > > Thanks, > > Micha > > There is often a BIOS setting that may affect this, but this is > assuming that you are speaking about booting to a console. If you True... I wasn't aware that this is an X 'issue'. But it turns out num=20 lock is on when I boot, and goes off when I start into X. > are booting into X then, from past experience, it is a bit more > tricky. I haven't looked at it in a while and things may have > changed, but as of a year or so ago there were various hacks and > tools to get the Numlock activated when booting into X. KDE's FAQ > used to have a section on this, in which they stated that it wasn't > really a KDE issue at all, but gave some tips on it simply because Yep. By now (I'm running 3.3), there is an option in the KDE control=20 center to activate num lock on startup... just found out about that:)=20 The numlockx package (... btw thanks Kevin) seems to be the best=20 solution for now, since it's not KDE specific. However, it releaves just some of the pain. X resets the num lock on=20 exit. Any ideas on that? > the Numlock when booting into X. A few web searches should pull up a > lot of information. Point taken... I didn't find anything on the num lock exit issue=20 though:) Greetings, Micha =2D-=20 Michael Wichmann michaelwichmann@gmx.net --nextPart6230946.qYyL9EYXZo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBUa0cyaG8M6g20w0RAncEAJ93Gm3KU14FO0zpPmKIYzULQ3PIQQCfY+c2 p1sCnOEOPUm1U+ODflQdG1g= =8Ria -----END PGP SIGNATURE----- --nextPart6230946.qYyL9EYXZo--