From owner-freebsd-ports@FreeBSD.ORG  Thu Aug 21 23:19:46 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7152516A4BF
	for <freebsd-ports@freebsd.org>; Thu, 21 Aug 2003 23:19:46 -0700 (PDT)
Received: from exchange.vivato.net (exchange.mabuhaynetworks.com
	[206.169.233.186])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E362143F93
	for <freebsd-ports@freebsd.org>;
	Thu, 21 Aug 2003 23:19:45 -0700 (PDT)	(envelope-from jdl@vivato.net)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Aug 2003 23:19:45 -0700
Message-ID: <D8B86D9BB607124BA1D54EDB7944DB0B0157D1EE@exchange.mabuhay>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Bad X Port?
Thread-Index: AcNoNb93JqfDmmgARryT00BIOO+/hwAILbxA
From: "Jon Loeliger" <jdl@vivato.net>
To: "Eric Anholt" <eta@lclark.edu>
cc: freebsd-ports@freebsd.org
Subject: RE: Bad X Port?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Aug 2003 06:19:46 -0000

>=20
> Do you by chance have non-default xkb settings in your XF86Config?  If
> so, try going back to default and finding the updated xkb howto (don't
> remember where it is), since things changed a lot for 4.3.0.

I don't believe I have any non-standard XF86Config parts.  In fact, it
is likely _so_ basic that it was wrong... or at best "incomplete".

You asked the right question though!  I started digging into the
whole xkb thing, was both disgusted and amazed simultaneously.
Mostly at how ignorant I had been of just the whole complicated
X keyboard mess going on behind my back. :-)

In any event, I added:  Option "XkbDisable"  to my keyboard
input section, and (Presto!) things were suddenly sane again.
I tinkered with my modes in the mean time and things look a
bit wonky, but I can actually get graphical display _and_ keyboard
input now.  Much progress.

Now, as to why just straight disabling xkb makes things work, I
really couldn't say yet.  But it identifies a pretty likely culprit.
At least now I can focus my frobbing towards XKB options and such.
Like, maybe I need an Option XkbModel Dell101 or something...

Thanks for the tips!
jdl