Subject: RE: Questions on X server on Dec 3000/300
To: 'Jarkko Teppo' <email@example.com>
From: Rufeng Li <firstname.lastname@example.org>
Date: 09/27/2002 00:46:10
Thanks for the answer. I made it to work. Hooray!
Thank you all for answering my questions regarding Pelican, and Kudos to
NetBSD for making it possible on a T.C. system. My only complain is the
document that kept me from trying earlier. :-)
From: email@example.com [mailto:firstname.lastname@example.org]On
Behalf Of Jarkko Teppo
Sent: Monday, September 23, 2002 12:57 AM
Subject: Re: Questions on X server on Dec 3000/300
> 1. When booted up, there were 4 identical error messages "wsconfig:
> WSDISPLAYIO_ADDSCREEN: Cannot allocate memory". What caused this error?
> Should I concern about the error?
Virtual consoles are not supported... so the error message is not really
> 2. "startx" error as following:
> No such file or directory (error 2): no server "X" in PATH
> I checked /usr/X11R6/bin (it is in PATH) and startx and xinit are in
> directory, but I could not find "X". I had Xserver.tgz in the
> directory and chose to install all. Why X is not there? What is the
> correct way to install Xserver stuff?
tar xfvzp Xserver.tgz manually and double check the symlink for
/usr/X11R6/bin/X -> /usr/X11R6/bin/XalphaNetBSD.