From owner-freebsd-stable@FreeBSD.ORG Thu Feb 17 12:48:08 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27FD916A4CE for ; Thu, 17 Feb 2005 12:48:08 +0000 (GMT) Received: from mvs1.plala.or.jp (c158129.vh.plala.or.jp [210.150.158.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10FEE43D3F for ; Thu, 17 Feb 2005 12:48:07 +0000 (GMT) (envelope-from e-kamo@trio.plala.or.jp) Received: from msc1.plala.or.jp ([172.23.8.24]) by mvs1.plala.or.jp with ESMTP id <20050217124806.CQUQ15772.mvs1.plala.or.jp@msc1.plala.or.jp>; Thu, 17 Feb 2005 21:48:06 +0900 Received: from [220.33.68.15] by msc1.plala.or.jp with ESMTP id <20050217124805.BNNF20796.msc1.plala.or.jp@[220.33.68.15]>; Thu, 17 Feb 2005 21:48:05 +0900 Message-ID: <4214928B.2070005@trio.plala.or.jp> Date: Thu, 17 Feb 2005 21:48:11 +0900 From: Eitarou Kamo User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: ja, en-us, en MIME-Version: 1.0 To: Daniel O'Connor , stable@freebsd.org, ceri@submonkey.net, robbak@gmail.com References: <200502151407.45801.michaelnottebrock@gmx.net> <4212F91A.20301@trio.plala.or.jp> <20050216164252.GI21348@submonkey.net> <200502171101.58572.doconnor@gsoft.com.au> In-Reply-To: <200502171101.58572.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Subject: Re: xf86enableIO error (Feb 2005 Snapshots for FreeBSD available) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 12:48:08 -0000 Hi, Xorg is working fine now. Thanks. Eitarou Daniel O'Connor wrote: >On Thu, 17 Feb 2005 03:12, Ceri Davies wrote: > > >>On Wed, Feb 16, 2005 at 04:41:14PM +0900, Eitarou Kamo wrote: >> >> >>>I got an io error >>>"xf86EnableIO: Fatal to open /dev/io for extended I/O" >>>when running "Xorg -configure". >>> >>>Has this snapshot been fixed this problem? >>> >>> >>Do you have a /dev/io? >>Do you have "device io" in your kernel configuration? >> >> > >Also check your securelevel is low enough (<1) you can find out what it is by >running sysctl kern.securelevel > > >