01-09-2004
From Sunsolve:
After installing Solaris[TM] 2.6 on an Ultra[TM] 10 with an m64 graphics card
and rebooting, the following error message was displayed:
X-server cannot be started on display :0
Trying to start OpenWindows failed with the messages:
9 SUNWxxxxx bad class
instance, line 163 in
/usr/openwin/server/etc/owconfig
Resolution Top
* Check to see what graphics card are installed by using the
following command:
# prtconf -F
* Check the device driver packages for the graphics card.
# pkginfo -l SUNW_package_name
* If possible, get a copy of the /usr/openwin/server/etc/owconfig from
another Ultra 10 with the same graphic card.
The possible error message:
frame buffer , it was not defined in the file.
may be caused by the fact that the /usr/openwin/server/etc/OWconfig file
was copied from another Ultra that did not contain entries for the m64
framebuffer because the Ultra 10 did not have the framebuffer.
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I've just bought an Ultra 60 running solaris 9 (or so I've been led to believe). When I start up, it looks for a (presumably) domain/network to hook up to and the following messages are displayed:
Boot device: net file and args:
Network link setup failed
Please check cable and try... (3 Replies)
Discussion started by: alarmcall
3 Replies
2. UNIX for Dummies Questions & Answers
I have just installed Solaris 10 x86 version on a Compaq Evo desktop station with a Sun 19" SVGA monitor model # CM751U. The desktop has 256MB RAM. The video card is a nVidia Riva TNT2 64. If I do a scanpci command; it returns the card as a nVidia Corporation NV6 (Vanta/Vanta LT)
The Xserver... (1 Reply)
Discussion started by: sjteng
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
From my workstation (win XP)I open a telnet session on Linux(Red Hat) server.
When I issue :
# xclock
I have :
Error: Can't open display:
Then :
# export DISPLAY=192.16.1.87:0.0
# xclock
Error: Can't open display: 192.16.1.87:0.0
Do you have an idea ?
Many thanks. (6 Replies)
Discussion started by: big123456
6 Replies
4. Solaris
I have problem with my V490 server which running on solaris 8. The error show on log file
X_mkdir: nosuch file or directory
Fatal server error:
Failed to establish all listening sockets
error (pid 299): server unexpectedly died
error (pid 299): server for display :0 cant be started
... (1 Reply)
Discussion started by: shamsul
1 Replies
5. Solaris
Hi
I am trying to debug an issue with an automated install I have set-up. So to start I just ran a simple
ok; boot cdrom - install
but when it came to the IP address field it would only take the following format 123.123.123.12 and would not let me enter the last digit
Anybody got any... (9 Replies)
Discussion started by: eeisken
9 Replies
6. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
7. Solaris
Hi all,
I've somehow gained the idea that I _need_ to run at least 1 box with Solaris, but things don't go as I had planned :-)
I pulled this ancient IBM eserver xseries 305 out of the dust, and got myself a fresh copy of the required cd's for Solaris 10u7. FAIL, for some reason the box and the... (7 Replies)
Discussion started by: mr.aart
7 Replies
8. Solaris
This is the error message that I am getting on a Solaris 10 sparc server
scsi: no major number
cannot load drivers for /pci@400.....
Can't load the root filesystem
Type 'go' to resume
{0} ok
Is there a way for me to correct this issue. It looks like I am missing a scsi driver to boot up... (5 Replies)
Discussion started by: trinityforce
5 Replies
9. Solaris
Hello guys,
I am a newbie. Just freshly installed Solaris 11. When I try to type for example root@t1000:~# man zpool It says bash: man: command not found. It used to show manual pages before installation. Any help is appreciated. Thanks. (5 Replies)
Discussion started by: nazimbilir
5 Replies
10. UNIX for Beginners Questions & Answers
Can anyone offer any advice on how to modify the script below to work on a new system we have, that has no graphics capability? We admin the system through a serial RAS device. I've tried running the below script through the RAS and through an ssh -X session. It failed with something like "GTK... (3 Replies)
Discussion started by: yelirt5
3 Replies
LEARN ABOUT HPUX
gvid_no_claim_dev
gvid_no_claim_dev(5) File Formats Manual gvid_no_claim_dev(5)
NAME
gvid_no_claim_dev - PCI Vendor/Device ID that the gvid graphics driver will not claim
VALUES
Failsafe
Default
Allowed values
Recommended values
Specific to the device you wish to prevent from claiming.
DESCRIPTION
This tunable specifies the PCI Vendor ID and/or Device ID of a graphics device that the HP graphics driver should not claim.
The graphics driver was designed to be a general purpose driver for all PCI graphics cards. As a result, the driver will attempt to claim
any PCI graphics display device found on the system. This can be a problem for graphics device developers who need their own graphics
driver to claim their own graphics device.
The value of will specify a PCI Vendor ID and/or Device ID of a graphics card that the gvid graphics driver should not claim. It is a 32
bit number, with the upper 16 bits containing the PCI Vendor ID and the lower 16 bits containing the PCI Device ID. Either the Vendor ID
or Device ID can use a wildcard value of
For example, if is set to the value the driver will ignore graphics devices with a PCI Vendor ID of and a Device ID of If is set to the
driver will not claim any graphics cards with a Vendor ID of regardless of the Device ID.
Who Is Expected to Change This Tunable?
Anyone who wishes the graphics driver to ignore a specific graphics device. This will typically be someone writing their own graphics
driver for their own hardware.
Restrictions on Changing
Changes to this tunable take effect at the next reboot.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
Tunable Kernel Parameters gvid_no_claim_dev(5)