From owner-freebsd-questions  Thu Nov 30 14:37:38 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from SCSUD.CTSTATEU.EDU (scsud.ctstateu.edu [149.152.40.2])
	by hub.freebsd.org (Postfix) with SMTP id AED7637B402
	for <freebsd-questions@freebsd.org>; Thu, 30 Nov 2000 14:37:35 -0800 (PST)
Received: from bretthauerd ([149.152.173.125]) by SCSUD.CTSTATEU.EDU with SMTP;
          Thu, 30 Nov 2000 17:07:17 -0500
Message-Id: <3.0.6.32.20001130170730.019041e0@scsu.ctstateu.edu>
X-Sender: bretthauer@scsu.ctstateu.edu
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Thu, 30 Nov 2000 17:07:30 -0500
To: Mike Heasley <mike@bikegods.org>, freebsd-questions@freebsd.org
From: Dave Bretthauer <bretthauer@scsu.ctstateu.edu>
Subject: Re: X 3.3.6 not working on FreeBSD 4.2
In-Reply-To: <20001130123026.A7814@pandora.inter.nut>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 12:30 PM 11/30/00 -0800, Mike Heasley wrote:
>> From: Dave Bretthauer <bretthauer@scsu.ctstateu.edu>
>> 
>> At 03:11 PM 11/29/00 -0600, Drew Sanford wrote:
>> >Dave Bretthauer wrote:
>> >
>> >> Fatal server error:
>> >> xf86OpenConsole: KDENABIO failed (Operation not permitted)
>> >
>> >Are you using KDE? Have you tried this without using KDE? This could be 
>> >a KDE problem and not an X problem.
>> 
>> I noticed that, too, and wondered why it was there.  No, I did not install
>> KDE (in fact, the reason I used vanilla X for a client is because I got the
>> same message after doing a full install with Gnome + Sawtooth).
>
>Just to add another data point, I'm having the exact trouble you are.
>I installed 4.2, configured X (it ran just fine at my selected resolutions
>during the install), rebooted, and got the above KDENABIO error.  I too
>did not install KDE, and I seriously doubt that has anything to do with
>it since it's an error in the X server itself.
>
>I wasn't able to find the error string in the XFree documentation, but
>my best guess at its meaning is possibly "keyboard enable I/O" error?
>Maybe it's a problem with the console driver in the kernel?  This is
>just speculation of course.
>
>I get the error in a number of situations: using the XF86_SVGA server,
>the VGA16 server, and the Mach64 server for my card.  I also rebuilt
>the kernel and got the same results.  Any ideas are much appreciated!

Well, you saved me the trouble of rebuilding a kernel for now! 8^)

I should add a couple more pieces of info:  I have now done fresh installs
of 4.2 on 3 different PCs.  One has a Matrox Millenium, one has ATI Mach64,
and the newest one has ATI 3D Rage Pro.  I've had the same result on all 3.  

If I'd never set up X before, I'd figure I did something wrong and RTFM
more carefully.  But I *did* set it up, with Gnome and Afterstep (no longer
an option), on both the Matrox and Mach64 PCs before.  And it worked.  Then
I  cvsup'd from 4.1 to 4.1.1 sometime in October on the Matrox box
(currently a test machine for me), and that's when it stopped working.  I'd
hoped a fresh install would help, but that didn't cure the problem, either.

I'd appreciate any thoughts as well!

Dave


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message