From owner-freebsd-questions@FreeBSD.ORG Wed Sep 22 15:02:01 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 36EC116A4CE for ; Wed, 22 Sep 2004 15:02:01 +0000 (GMT) Received: from frontend1.messagingengine.com (frontend1.messagingengine.com [66.111.4.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07BB443D2D for ; Wed, 22 Sep 2004 15:02:01 +0000 (GMT) (envelope-from nkinkade@fastmail.fm) X-Sasl-enc: AWXjyb0YQsxSvY2nU3NLEA 1095865319 Received: from gentoo-npk.bmp.ub (unknown [206.27.244.136]) by www.fastmail.fm (Postfix) with ESMTP id A5B33C1566F; Wed, 22 Sep 2004 11:01:59 -0400 (EDT) Received: from nkinkade by gentoo-npk.bmp.ub with local (Exim 4.21) id 1CA8bH-0002kv-0z; Wed, 22 Sep 2004 09:00:07 -0600 Date: Wed, 22 Sep 2004 09:00:07 -0600 From: Nathan Kinkade To: Michael Wichmann Message-ID: <20040922150007.GD3633@gentoo-npk.bmp.ub> Mail-Followup-To: Michael Wichmann , freebsd-questions@freebsd.org References: <200409221505.37494.michaelwichmann@gmx.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xB0nW4MQa6jZONgY" Content-Disposition: inline In-Reply-To: <200409221505.37494.michaelwichmann@gmx.net> User-Agent: Mutt/1.5.6i Sender: cc: freebsd-questions@freebsd.org Subject: Re: Num lock status on boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nathan Kinkade List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2004 15:02:01 -0000 --xB0nW4MQa6jZONgY Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 22, 2004 at 03:05:22PM +0200, Michael Wichmann wrote: > Hello everyone, >=20 > Just a quick question about this little thing, that bugs me from time to= =20 > time:) Num-lock ist turned off by default after I boot up FreeBSD=20 > 5.2.1. Is there any way to enable it by default? >=20 > 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 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 the issue came up frequently. You can try playing around with xset(1) and the 'led' option. I also recall that there was a small program developed for the very purpose of automatically activating the Numlock when booting into X. A few web searches should pull up a lot of information. Nathan --=20 PGP Public Key: pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0xD8527E49 --xB0nW4MQa6jZONgY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBUZN2O0ZIEthSfkkRAqWBAJ9X7LNUFIJdz+kHJdXY+/aDlvy4bwCgyK0X GyIglpFK5BUG+hqhA+43NHI= =UHu8 -----END PGP SIGNATURE----- --xB0nW4MQa6jZONgY--