- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Y2K patches broke Xserver
Operating System - HP-UX
1819927
Members
3051
Online
109607
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-02-2000 09:45 PM
тАО01-02-2000 09:45 PM
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.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-03-2000 08:31 AM
тАО01-03-2000 08:31 AM
Re: Y2K patches broke Xserver
Have a look at doc id W1556862 its a bit old but maybe the answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2000 12:54 AM
тАО01-04-2000 12:54 AM
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 ?
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
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 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2000 05:41 PM
тАО01-06-2000 05:41 PM
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP