From owner-freebsd-questions Wed Jan 31 17:31: 7 2001 Delivered-To: freebsd-questions@freebsd.org Received: from FreeBSD.mine.nu (unknown [203.106.71.187]) by hub.freebsd.org (Postfix) with ESMTP id AA52337B491 for ; Wed, 31 Jan 2001 17:30:44 -0800 (PST) Received: from FreeBSD.mine.nu (-@localhost [127.0.0.1]) by FreeBSD.mine.nu (8.8.8/8.8.8) with SMTP id JAA22610; Thu, 1 Feb 2001 09:42:57 +0800 (MYT) (envelope-from skywizard@time.net.my) From: Ariff Abdullah Reply-To: skywizard@time.net.my Organization: FreeBSD 2.2.8-RELEASE To: treznor@sunflower.com, Tyler McGeorge , Jim Conner Subject: Re: Unable to startx Date: Thu, 1 Feb 2001 09:36:56 +0800 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: freebsd-questions@freebsd.org References: <20010201004156.24530.qmail@web10603.mail.yahoo.com> In-Reply-To: <20010201004156.24530.qmail@web10603.mail.yahoo.com> MIME-Version: 1.0 Message-Id: <01020109425700.22409@FreeBSD.mine.nu> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 01 Feb 2001, Tyler McGeorge wrote: > I'm just guessing on this one, never had the problem > myself, seeing how no working serial port=no serial > mouse and lack of PS/2 port means no working mouse, so > I don't have much experience with X. :P However, This > sounds like a possible permissions problem. I'm not > sure, but I think X may need to be started as root > initially. But seeing how you said you ran it > from /stand/sysinstall, this is probably not the case. > I would delete all the X packages, not sure which or > how many, but you can find out with pkg_info, which > you might want to pipe that to grep and filter out > anything that doesn't reference XF86 or something > similar. After you delete those packages, add them > again, and if possible, do it from the FTP just to > simplify things (I have packages on CD and it's a > hassle). > > Hope this helps, > Ty > --- Jim Conner wrote: > > I have had the very same thing happen to me. I even > > posted the question > > here on this mailing list only to find that nobody > > responded. Of course, > > this meant to me that nobody knew the problem. I > > even sent a bug report to > > the XF86 folks and received no response from them as > > well. > > > > *shrug* > > > > Let me know if you get an answer to this one as I am > > still wondering how to > > fix it even though I have since not used that > > machine anymore. > > > > - Jim > > > > > > At 07:51 AM 2/1/2001 +0800, Alan Tsang wrote: > > > > > > >Hi > > > > > >I installed and setup the Release 4.2 but was > > unable to startx. > > > > > >I followed the normal procedures, boot the > > installation floppies and > > >configured everything. > > > > > >In the installation screen, I was able to use > > XF86Setup to configure the X, > > >started X server test and save the configuration > > file. > > > > > >However, when I boot the installed system and tried > > to startx, I got message > > >"xf86OpenConsole: KDENABIO failed (operation not > > permitted). > > > > > >Even worse, when I tried to reconfigure X using > > XF86Setup or inside > > >/stand/sysinstall, the configuration program just > > cannot start the X server > > >anymore. > > > > > >I would be grateful if anyone can help on the > > issue. > > > > > >Thanks > > > > > >Alan Tsang > > > > > > > > > > > > Something to do with kern.securevel ( sysctl kern.securelevel ) X cannot start because you set the security level too high, preventing the X server to communicate with your hardware. Read your /etc/rc.conf and /etc/defaults/rc.conf ("kern_securelevel_enable" variable). Try to disable it first (put "NO"). This require a reboot. man init. good luck -- +----------------------------------------+ | /\_____ | | / ./__ | | / __/ < I do understand.. | | / ___/ | | / / | | ^^^^^^^^^^^^^^^^^^^^^^ | | *warf* *warf* | | | +----------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message