*BSD News Article 11740


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA1988 ; Wed, 24 Feb 93 13:00:12 EST
Newsgroups: comp.os.386bsd.questions
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sun-barr!cs.utexas.edu!wupost!newsfeed.rice.edu!rice!news.Rice.edu!rich
From: rich@Rice.edu (Richard Murphey)
Subject: Re: Garbled login after installing XFree-1.2 
In-Reply-To: lwinzele@uiuc.edu's message of Mon, 22 Feb 1993 18:09:24 GMT
Message-ID: <RICH.93Feb22222544@omicron.Rice.edu>
Sender: news@rice.edu (News)
Reply-To: Rich@Rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
References: <C2v3s3.Hz7@ux1.cso.uiuc.edu>
Date: Tue, 23 Feb 1993 04:25:44 GMT
Lines: 57

In article <C2v3s3.Hz7@ux1.cso.uiuc.edu> lwinzele@uiuc.edu (Loren Winzeler) writes:
   After installing XFree86-1.2 and using the binary "nostrip" kernel
   on agate, I am having troubles with the regular login screen.  
   Everything runs fine in my opinion, including X, except that on boot
   up, the login prompt is garbled into special characters and trash.
   I can still login in though, but the characters echoed to the screen
   are junk.  After a single failed password or login, the words
   login: and Password: print correctly.

If this happens upon booting *before* you have run X, then it's not a
problem in the X server but a problem in the kernel or your
configuration or your hardware.  Try the kernel-1.2.pccons-fix-1.tar.Z
or kernel-1.2.codrv-fix-1.tar.Z in /pub/386BSD/0.1-ports/XFree86-1.2
just for comparison.

   I think the problem is in my /etc/ttys file.  I changed to console
   to vga for X.  Is this all that should be changed?  What emulation
   should be used, pc3?  The documentation on this what unclear. 

The documentation tells you to run the install script
/usr/X386/lib/X11/etc/x386install.  Do this and/or double check the
steps it goes through.

   I installed the pccons linkkit and compiled it (using the older gcc,
   stealing the extra lib file from ref to solve the __main missing bug)
   but have not even moved the new server into use.  I have not been
   running xdm upon startup.  Should I be?

Not till you are able to start the xerver correctly otherwise.  Even
then it sounds like you will need the XFree86-1.2-xdm-nodes.tar.Z from
agate.berkeley.edu (128.32.136.1) in either /pub/incoming/XFree86-1.2
or in /pub/386BSD/0.1-ports/XFree86-1.2.

   Since I have limited space and cannot install source or recompile,
   should I be using the kernel with pccons support?  (Does it have
   all the 0.2.1 patches?)  The nostrip kernel binary on agate was
   supposed to have pccons support, right?  (I guess I avoided misnaming
   problems by not using the kernels in the 1.2 directory, eh.)

pccons support is the most common configuration and there is no reason
you can't stick with it.  The 0.2.1 patchkit adds the proper X support
to pccons for XFree86-1.2.

   Also, I have not looked into it, but upon boot up an error message is
   now echoed to the screen...

   Find: .X11-unix .. file or dir not found.

This can happen if the server is killed without the opportunity to
remove this file as it normally does.  If you get the distribution set
up correctly and X386 exits normally you shouldn't get this message.

   Was something added to the rc.local?

there are no required changes to rc.local, and no, the install scripts
don't touch it.  Rich