From owner-freebsd-questions@FreeBSD.ORG Wed Nov 3 14:45:21 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 21D0316A4CE for ; Wed, 3 Nov 2004 14:45:21 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 859F643D53 for ; Wed, 3 Nov 2004 14:45:20 +0000 (GMT) (envelope-from nlamprecht@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so140078wri for ; Wed, 03 Nov 2004 06:45:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=bkCeZvBbjf0Evgxl9lmbvGEF8Fmo26/vTFIH5bEEBbhky8xDJu5xVi5GaCVL58c9AxIIRB2UBZMFs34EiCyEAp6iqCtteo8UEmV/yvJ9rLGIt6KmkXIiWhQi4juDWybixPQqwmQ4iv6xLotoVXGvbH85PPZ70/yZfod5mss8cpI= Received: by 10.54.37.47 with SMTP id k47mr163450wrk; Wed, 03 Nov 2004 06:45:15 -0800 (PST) Received: by 10.54.38.55 with HTTP; Wed, 3 Nov 2004 06:45:14 -0800 (PST) Message-ID: <7cbadc870411030645228b0dd6@mail.gmail.com> Date: Wed, 3 Nov 2004 16:45:14 +0200 From: Nelis Lamprecht To: Gerard Samuel In-Reply-To: <4188EBE7.1000000@trini0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4188EBE7.1000000@trini0.org> cc: FreeBSD Questions Subject: Re: FreeBSD 5.3 and XFree86 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nelis Lamprecht List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 14:45:21 -0000 On Wed, 03 Nov 2004 09:32:07 -0500, Gerard Samuel wrote: > I just upgraded from 5.2.1 to 5.3. When running startx, it ends up with > this error -> > > Fatal server error: > xf86EnableIO: Failed to open /dev/io for extended I/O > Does /dev/io exist ? Have you got Xwrapper installed (/usr/ports/x11/wrapper) ? Only other cause for this is if your kern.securelevel is set above 1 A quick google would have given you several clues :) Nelis