Unable to start X

[Tim Woods_2]

After rebooting my HP-UX 11.0 D380 the X server will not start up.

When I try to start it manually I get the message:

X server: Error in /etc/X11/X0screens (line 511)
Device name invalid or missing after keyword "Screen".
X server: Will try default "/dev/crt"
Failure to open default device file `/dev/crt`.
Please either specify the proper device filename in
your /etc/X11/X0screens file or fix `/dev/crt`. This filename is either
non-existent or is not a character special file.

Fatal server error:

giving up.
xinit: Connection refused (errno 239): unable to connect to X server
xinit: No such process (errno 3): Server error.

There is no /dev/crt file on the server. I have X running on my N4000 successfully and it alos has no /dev/crt file but generates no errors. Prior to this the D380 had not been rebooted in the 5 months I've been with the company so I have no idea if this is from a pre-existing change that was made and took effect after the reboot.

The reboot was done to increase space in /var, /usr, and /tmp but no other changes were made.

I have run "/sbin/insf -e -d framebuf" to generate the file to no avail.

Any Ideas? Thanks.

Tim

[Sachin Patel]

I think you can create /dev/crt file
#mknod /dev/crt c 174 0x000000

I don't know that this is your problem or not. but you can try.

Here are couple more thing that is posted by MR X (Alex)

2) Run /usr/contrib/bin/X11/dr_dt. The end of the output from this
script says: X ERRORs and X WARNINGs. These errors and warnings
should be resolved before CDE will run properly.

3) Check the error log /var/dt/Xerrors
Check the error log $HOME/.dt/errorlog (Only if particular user has login problem)

4) The output from "nslookup " and "nslookup " should
be the same. This checks for a) duplicate IP addresses or
hostnames or b) problems with name resolution. If nslookup fails
then CDE will fail to start. If the first line returned from nslookup
is: "Name Server" then you are using DNS. Move "/etc/resolv.conf" to
another name, i.e. /etc/resolv.conf.orig and rerun nslookup. If
nslookup now succeeds then try logging into CDE again.

5) Check permissions and ownership of the following files:
-r--r--r-- 1 bin bin 616 Jul 1 16:03 /etc/hosts
-r--r--r-- 1 root sys 1010 Jun 25 18:22 /var/adm/inetd.sec

6) Check the contents of /var/adm/inetd.sec. It should contain
dtspc allow
spc allow
mserve allow
If not add the lines and run "/usr/sbin/inetd -c" to reread the file.

7) /usr/sbin/ping
You should get back 0% packet loss. If you get something different
then check your network configuration.

8) Make sure the $LANG environment variable is set correctly. It should
be set to C or unset for American-English.

9) Exit the failsafe session. From the CDE login select Options ->
Command Line Login. When the screen turns black, press and
you should get a Console Login prompt. Login as root.

10) mv $HOME/.dt $HOME/.dt.orig
mv $HOME/.dtprofile $HOME/.dtprofile.orig
exit (to return to CDE) - try logging in as root.

11)/etc/dt/config/Xserver file needs this line to start X
* Local local@console /usr/bin/X11/X :0

Sachin Patel

[S.K. Chan]

Look at file
/usr/lib/X11/Xserver/info/screens/hp
which explains how to customize X*screens

[Helen French]

hey,

Check the log files and X session configurations.

I had a similar problem long back, when i restarted my HP workstation after a system change. It was unable to start the X session, but later found out a simple mouse connection problem ..check out the connections too !

or u can try reconfiguring the session

HTH,
Shiju

[Alex Glennie]

try rmsf /dev/*crt*
insf -evd framebuf

If the above fails what's the contents of your X0.screens + the output from graphinfo ?

[Tim Woods_2]

Sorry it took me so long to get back to this topic.

I tried everything suggested here, but nothing seemed to help. I found out that I could still run SAM remotely from another system, but I could not XDMCP directly to the server.

I applied the rest of my patch bundles, rebooted the system, and everything worked fine. I'm still not sure what the problem was, but thanks to everyone that responded.