Operating System - HP-UX
1824721 Members
3576 Online
109674 Solutions
New Discussion юеВ

Couldn't open X pointer device! Is one attached?

 
SOLVED
Go to solution
Haral Tsitsivas
Advisor

Couldn't open X pointer device! Is one attached?

I moved a disk drive with HP-UX 10.20 from one HP 715 to another (80 to 33).
After making the necessary changes for ip and hw address I can login and use the computer but I dtlogin will not run on it. It fails with the following error (error message written to /var/dt/Xerrors):

error (pid 1080): Server for display gila:0 terminated unexpectedly 1

Fatal Server error:
Couldn't open X pointer device! Is one attached?

X connection to gila:0.0 broken (explicit kill or server shutdown).

How do I redefine the mouse?
8 REPLIES 8
Printaporn_1
Esteemed Contributor

Re: Couldn't open X pointer device! Is one attached?

please make sure that you're proper connect mouse and keyboard.
enjoy any little thing in my life
Bill McNAMARA_1
Honored Contributor

Re: Couldn't open X pointer device! Is one attached?

You might want to make sure that the keyboard path and/or pointer path defined at the bch are well defined.
Interrupt the boot (10seconds) and type he

However, You may want to find out where your pointer is defined in the Xserver config:
ls /etc/X11/X0*
ioscan -fnk
to look for hil device file.

cat the device file and shake the mouse around to make sure it works...

Later,
Bill
It works for me (tm)
Haral Tsitsivas
Advisor

Re: Couldn't open X pointer device! Is one attached?

Once the boot process starts I cannot interrup the boot process... CTRL-B doesn't seem to work.

The files in /etc/X11 are default, with everything commented. I did an "ioscan -fnk" and it reports:

hil 0 2/0/0 hil CLAIMED INTERFACE Built-in HIL
/dev/hil_1.1 ../dev/hil_1.7
/dev/hilkbd_1 /dev/rhil_1

I added "/dev/hil_1.1" to X0devices but it did not help.

How do I get to bch and the he command?

Sridhar Bhaskarla
Honored Contributor

Re: Couldn't open X pointer device! Is one attached?

Take the disk out and see if you can be able to boot the workstation till the bootadmin prompt. If it doesn't work, then you have to physically check the connections or the firmware version of your 715.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Haral Tsitsivas
Advisor

Re: Couldn't open X pointer device! Is one attached?

The disk is fine (I can obviously boot and login at the console, so the keyboard is fine too)... The mouse works too (I can boot HP-UX 10.10 from another disk on the same machine and run dtlogin and login in the full CDE desktop). The X0devices file on the 10.10 OS though only contains comments, so it does not help me configure the 10.20 OS.

Sridhar Bhaskarla
Honored Contributor

Re: Couldn't open X pointer device! Is one attached?

It's very interesting.

You wrote that you couldn't stop the boot process. So, it won't matter if it is 10.20 disk or 10.10 disk as booting till that point is independent of your bootable disk.

Did you run an insf -e after the system came up?

-Sri

You may be disappointed if you fail, but you are doomed if you don't try
Charles Slivkoff
Respected Contributor
Solution

Re: Couldn't open X pointer device! Is one attached?

The I/O paths to the HIL & framebuffer devices are different between the 715/80 and 715/50. These steps should get you started:



1/ Remove the following files:

/dev/*crt*

/dev/*ps2*

/dev/*hil*

/etc/ioconfig

/stand/ioconig

2/ Reboot the system (do NOT skip this step)

3/ During the boot, you will be prompted that ioconfig is missing. Run "/sbin/ioinit -c" as suggested in the prompt. Then run "/sbin/insf -e".

4/ If all went well, the X server should be able to now find the input devices.



These steps basically force a remapping of the I/O devices with device file major numbers. The mapping you currently have does not match the hardware, thus the problems.



Haral Tsitsivas
Advisor

Re: Couldn't open X pointer device! Is one attached?

Thanks Chuck! Removing ioconfig and running insf -e changed the error message somewhat (X server rejected last DLD broker), so I installed the most recent X server patch (PHSS_23535) and when I rebooted I received an error asking me to remove /dev/graphics1 and run "/sbin/insf -e -d framebuf". Dtlogin was then able to start.