Date: Tue, 21 Oct 2003 14:16:12 -0400 From: WiggTekMicro Corp <wiggtekmicro@comcast.net> To: Dylan Wylie <d.wylie@hccnet.nl>, Mobile-BSDlist <freebsd-mobile@freebsd.org> Subject: Re: XFree86 won't run on 5.1 installed on Lifebook S-2020. Message-ID: <1066760171.6841.32.camel@wiggtekmicrogate> In-Reply-To: <3F958FF7.26064.81D117@localhost> References: <3F9581EB.5342.4AF44B@localhost> <3F958FF7.26064.81D117@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-Jv8/mWGoADyBOoT+Pc5T Content-Type: text/plain Content-Transfer-Encoding: 7bit I think that I have noticed a bit more than I did last night. I noticed that the /root/.Xauthority file seems to be missing. I am doing further research as to what this file does, and how to put it in. I am completely understanding that I am the independent variable. No need for smilies, I know how things are when it comes to non-phd's in Computer Science, attempting to do things that they won't completely understand, until about their fifth year at Berkeley.... ::))) -- Respectfully, Martes G.W. Wiggtekmicro Corp --=-Jv8/mWGoADyBOoT+Pc5T Content-Disposition: inline Content-Description: Forwarded message - Re: XFree86 won't run on 5.1 installed on Lifebook S-2020. Content-Type: message/rfc822 Received: from smtp.hccnet.nl ([62.251.0.13]) by rwcrmxc12.comcast.net (rwcrmxc12) with ESMTP id <20031021180031r1200248e7e>; Tue, 21 Oct 2003 18:00:31 +0000 Received: from upsilon by smtp.hccnet.nl via fia142-13-100.dsl.hccnet.nl h9LI0Kf1006602 (8.12.10/2.03); Tue, 21 Oct 2003 20:00:20 +0200 (MET DST) From: "Dylan Wylie" <d.wylie@hccnet.nl> To: wiggtekmicro@comcast.net Date: Tue, 21 Oct 2003 19:58:47 +0200 MIME-Version: 1.0 Subject: Re: XFree86 won't run on 5.1 installed on Lifebook S-2020. Message-ID: <3F958FF7.26064.81D117@localhost> Priority: normal In-reply-to: <1066755985.6841.28.camel@wiggtekmicrogate> References: <3F9581EB.5342.4AF44B@localhost> X-mailer: Pegasus Mail for Windows (v4.11) Content-type: text/plain; charset=US-ASCII Content-description: Mail message body Content-Transfer-Encoding: 7bit On 21 Oct 2003 at 13:06, WiggTekMicro Corp wrote: > The checkered screen with the large "X" appears, so I know that the > -configure file is functional. However, when I try to run that file, > after modification for my specific equipement, the same screen appears, > for a moment, and then the session exits with the bad monitor name :0 > errors. I have just finished with 4.8, so I will probably try that. > However, I had the same problems with 4.4 on a publishers copy. It had > 3.3 xfree86. I have gotten the graphic interface to work twice, in as > many days of doing the same things I did when I had it working. > > Thanks for the comments. What OS release are you running? > -- > Respectfully, > > > Martes G.W. > Wiggtekmicro Corp > So your also copying the working XF86Config.new to /etc/X11/XF86Config ? Are you convindced about the XFConfig file you're using when doing startx? I'm running 5.1 on a laptop and 4.8 on a desktop as a server. 4.8 has worked great with X, I haven't configured X on the 5.1 yet. This is why I'm especialy interested in why your not getting it to run. That is however also why I'm curious as to why you've had the same problem on completely different systems. The only non-discriminating factor seems to be the user :) It realy sounds like your leaving something out or something, though I must admit I don't consider myself knowledgeble enough to realy help you further. What does your XF86Config actually look like? Have you tried not changing anything at all after doing a #XFree86 -configure and then copying the generated XF86Config.new to /etc/X11/XF86Config and then do startx? Are you changing the monitor name? If so, make sure you change all instances of this name througout the XF86Config file. Better yet, don't change it :) Mabe it's being referenced to. Any luck? Dylan --=-Jv8/mWGoADyBOoT+Pc5T--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1066760171.6841.32.camel>