Operating System - HP-UX
1820592 Members
1670 Online
109626 Solutions
New Discussion юеВ

Re: 11i "pointing device issue"

 
Ken Martin_1
Occasional Advisor

11i "pointing device issue"


After loading 11i on a B132 on bootup it complains about "not finding a pointing device for X" and that "samd" is respawning too fast.

Editing inittab to stop respawning "samd" stopped that message. Don't know if that's good or bad?

The current PS2 style mouse and keyboard worked fine under 10.20 on this B132 with CDE.

Any ideas why 11i would complain about the mouse?

Thanks
7 REPLIES 7
Craig Rants
Honored Contributor

Re: 11i "pointing device issue"

I have never seen a B class machine before but when I last had a pointing device message showing up all the time it was looking for a USB mouse. Once I plugged one in, it started looking for a USB keyboard (which means more messages). HP never gave me a good solution for this other than to leave them plugged in.

Maybe someone else out that has a good way to disable this search.

C
"In theory, there is no difference between theory and practice. But, in practice, there is. " Jan L.A. van de Snepscheut
Sanjay_6
Honored Contributor

Re: 11i "pointing device issue"

Hi Ken,

Take a look at this thread, Not sure it will solve your probelm, but try it anyway,

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=58581936138f42b530/screen=ckiDisplayDocument?docId=200000036518917

Hope this helps.

Regds
Sachin Patel
Honored Contributor

Re: 11i "pointing device issue"

Hi ken,
Are you having problem running cde?

I had same error message on 11i. I have solution for it. but only if you have problem running cde.

Sachin Patel
Is photography a hobby or another way to spend $
Ken Martin_1
Occasional Advisor

Re: 11i "pointing device issue"

Sachin,

When I loaded (installed) 11i from the B3920-14052 CD (11i Sept. 2001) on the B132 I didn't see a question for CDE. After the install it trys to start 'X'. That fails with the mouse issue as noted and the "samd" respawning too quickly issue as noted.

If I login and bypass 'X' I can run SAM ok and do other shell based operation.

Is CDE on there by default? What's your idea?

Ken
Alex Glennie
Honored Contributor

Re: 11i "pointing device issue"

Out of interest what media did you use for 11.i it should have been I guess.

http://info-library.hp-tcsc.com/documents/hpux11i_TCOE_5980-6644ENUS_110701_screen.pdf CDE and X11 is normally installed as part of the Core O/S check with swlist -l bundle / or fileset ?

The error you quoted is normally generated by either : mouse/keyboard not plugged in or faulty h/w or .....

Permissions or non existant device files so try :

rm /dev/*crt*
rm /dev/*ps2*

ioinit -c
ioinit -i
insf -evd framebuf
insf -evd ps2

also ensure the drivers (ps2) are installed in the kernal ?
Eugen Cocalea
Respected Contributor

Re: 11i "pointing device issue"

Hi,

I never worked with 11i so far, but, in 11.00 I would take a look at /etc/X11/X0devices. There you can define the mouse and keyboard type. I suppose that they are USB by default in 11i.

The file is very well documented and easy to configure, so go ahead and put there your devices.

E.
To Live Is To Learn
Sachin Patel
Honored Contributor

Re: 11i "pointing device issue"

Hi Ken,
I had same error and I was thinking same as this guys. I didn't resolv problem for day and so I called HP. here is what they told me to reolve problem.

ls /dev/pty |wc -w
ls /dev/ptym | wc -w
60 is the default, if you see 60 as a response, no increases have been
made.

You will need to increase the npty kernel paramater which will require a
reboot.


1. Use SAM --> Kernel --> Configurable Parameters
npty (10.20 and 11.X)
nstrpty (11.X only)
set NPTY and NSTRPTY to the desired number (512 for example), save and
reboot.
NPTY and NSTRPTY are the desired number of connections.

2. Rebuild the special device files at the command prompt as follows:

insf -d ptys -n 512 512 being the number you set NPTY in SAM (10.20
and
11.X)
insf -d ptym -n 512 (10.20 and 11.X)

insf -d pts -s 512 -e -v (for 11.X only )

This will create ptys so that the total is 512.

NOTE: 512 was used as an example value. You should determine the number of
PTYs needed based on the number of users logins to the system.

Then hp wrote
It seems that SAM disables the pty
driver from the kernel after your change of npty. This is known by
the labs and they are working on a fix. Here is the workaround to
resolve the problem.




To work around this problem, edit /usr/sam/lib/kc/drivers.tx. Search
for a line beginning with "pty0". Change the field containing
"Unallowed" to something else, like "pty". Do the same for a line
beginning with "pty1". Save the file. As root, run
"/usr/sam/lbin/getkinfo -b". Sam should now no longer exhibit the
faulty behavior.

Then hp wrote at last
# cd /stand/build
# /usr/lbin/sysadm/system_prep -v -s system
# kmsystem -c y -S ./system pty0
# kmsystem -c y -S ./system pty1
# mk_kernel -s system
# mv /stand/system /stand/system.prev
# mv /stand/vmunix /stand/vmunix.prev
# mv /stand/dlkm /stand/dlkm.prev
# mv /stand/build/system /stand/system
# kmupdate /stand/build/vmunix_test
# cd /
# shutdown -r -y 0

I am still not able to run cde on itanium box using 11i (HP says they do not support cde on console yet) but x is working fine.

I hope this will help

Sachin Patel
Is photography a hobby or another way to spend $