Operating System - HP-UX
1819927 Members
3051 Online
109607 Solutions
New Discussion юеВ

Y2K patches broke Xserver

 
Ponder William
New Member

Y2K patches broke Xserver

I'm running an 10.20/S700 box and after installing
the correct Y2K Core-OS packages, X no longer will
load. If I try to manually run it from 'startx',
it yields a "Graphics Resource Manager" error.

Has anyone else had this problem and no of a solution?

thank you.
3 REPLIES 3
Anthony Goonetilleke_1
Regular Advisor

Re: Y2K patches broke Xserver

Have a look at doc id W1556862 its a bit old but maybe the answer.
user not active
Frequent Advisor

Re: Y2K patches broke Xserver

Usually grmd errors are caused by permision problems notably the /tmp
directory, the CDE diagnostic /usr/contrib/bin/X11/dr_dt may show something ?

Check usr/lib/grmd is a symbolic link to /usr/lbin/grmd
ownership should be 4555 owner daemon I think, you can always check on a
working system.

If not, is there already a grmd process running ? It maybe worth your while :

1. Remove all files from the '/var/spool/sockets/X11' directory.
2. Remove the '/var/spool/sockets/grmd' files.
3. Set the permissions to 777 on the '/tmp' directory.

Also worth checking in /etc/services wrt port 5999, make sure its not being
used by something else ?

Be 100 % certain that mouse and keyboards are connected and check the Xservers
log file : /var/dt/Xerrors.

You could check with ipcs -sa ? grep daemon and then use ipcrm -s to
remove and then reboot in case this is semaphore related issue ?

Also I beleive there are debuggable versions of grmd to hand, but it maybe wise
at this stage to log an official call ?

user not active
Frequent Advisor

Re: Y2K patches broke Xserver

Bill,

I've just finished fixing another grmd error and as there's not a great deal
of documentation stating that shared memory and/or semaphores can also cause
this error, thought it wise to point it out. It maybe worth your while upping
semaphore related variables in the kernal, namely : semmns,semmnu,semume and
possibly shmmax or via sam, you can decrease the shared graphics segment memory
the Xserver uses. Or use Glance and the ipcs command to check if this is a
possibility first, before regenning your kernal.

In my case disabling ITO / Oracle applications allowed the grmd to start and
consequently pointed us in the right direction of the fix.