From owner-freebsd-questions Sun Aug 26 20:11:38 2001 Delivered-To: freebsd-questions@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id 42DB137B403 for ; Sun, 26 Aug 2001 20:11:32 -0700 (PDT) (envelope-from clabrown@granitepost.com) Received: from sager (austin.granitepost.com [209.150.104.143]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id BAA12560 for ; Mon, 27 Aug 2001 01:08:44 -0400 (EDT) Reply-To: From: "Clarence Brown" To: Subject: RE: can't start X Windows Date: Sun, 26 Aug 2001 23:22:05 -0500 Message-ID: <000201c12eaf$d4d3f660$8f6896d1@granitepost.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3B895745.E7708C02@home.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK, I commented out the kern_securlevel_enable="YES" and the kern_securelevel=1 lines. This allows XWindows to start. I can type XFree86 -configure and it generates a config file that will start XWindows like the documentation says. This gives me a gray hatched screen with an "X" cursor which can be controlled with the mouse. However KDE won't run, I added the line to start kde to the .xinitrc file and I saw KDE Begin to start the first time. The screen went blue, and I saw a KDE dialog box as it seemed to start building its configuration files, but eventually the screen went to a solid dark gray with no cursor. I have to hit Ctrl-Alt-Bkspace to get back to a prompt. Now when I type startx I see the hatched screen and "X" cursor for a second, then it switches to the dark gray blank screen. It also switches to the same screen with the default .xinitrc file that starts twm instead of kde. Is this a problem with kde or Xwindows? I installed both xwindows and kde from packages on the 4.3 CD. Are there known bugs in the package of KDE distributed on the 4.3 CD? Any suggestions? Cla. > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Rob > Sent: Sunday, August 26, 2001 3:09 PM > To: Doug Denault > Cc: Clarence Brown; freebsd-questions@FreeBSD.ORG > Subject: Re: can't start X Windows > > > Don't forget to also install "wrapper" from the ports. Then you won't > need SETUID server. Rob. > > > Doug Denault wrote: > > > > Are you using kernel security? If you have > > 'kern_securelevel_enable="YES"', remove that and try again. If > > kern_securelevel=1, you can not write to /dev/io. I am not > sure about '0'. > > > > On Sun, 26 Aug 2001, Clarence Brown wrote: > > > > > Hi: > > > > > > I'm trying to start xwindows on FreeBSD 4.3 > > > newly installed from CD. The machine is > > > an HP NetServer with built in graphics using > > > a Cirus GD5446 chip and 2 meg. > > > > > > I tried to follow the instructions in the > > > handbook, but running XFree86 -configure > > > produces the same error as below, it does not > > > make a starting config file. > > > > > > I tried running xf86config to produce the > > > config file, and that works but I still > > > get the same error when trying to startx. > > > I get the same errors when i select the > > > card as Cirus 544x, or 5446 noname, or > > > Generic VGA. > > > > > > (WW) checkDevMem: failed to open /dev/mem (Operation not > permitted) > > > linear framebuffer access unavailable > > > and > > > > > > Fatal server error: > > > xf86EnableIO: Failed to open /dev/io for extended I/O > > > > > > Here is the log: > > > > > [cut] > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > -- > The Numeric Python EM Project > > www.members.home.net/europax > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message