Openwin Error


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Openwin Error
# 1  
Old 12-05-2001
If you have a process called dtlogin running, just set up your Exceed to do an XDMCP session to your E450.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

SunBlade 150 can't start openwin: /usr/openwin/bin/xinit: Server error.

Hi. I have a Microsystems SunBlade 150 shell# cat /etc/release Solaris 8 2/02 s28s_u7wos_08a SPARC shell# uname -a SunOS HOSTNAME 5.8 Generic_108528-14 sun4u sparc SUNW,Sun-Blade-100 shell# prtconf -F /pci@1f,0/SUNW,m64B@13:m640 When I join to the only account the server try to... (5 Replies)
Discussion started by: siegroup
5 Replies

2. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ... (2 Replies)
Discussion started by: christr
2 Replies

3. Hardware

seeking QUIET hardware Sparc Solaris 8/Openwin

I have several applications locked to Solaris 8 (and older) and have been very happy with my Sparcs and Ultras but am getting tinnitus problems from fans and disks. Any tips on a quiet thin client (with decent graphics, not video or gaming level but 24bit and multi monitor would be useful) that... (0 Replies)
Discussion started by: batchman
0 Replies

4. UNIX for Dummies Questions & Answers

> 5 ")syntax error: operand expected (error token is " error

im kinda new to shell scripting so i need some help i try to run this script and get the error code > 5 ")syntax error: operand expected (error token is " the code for the script is #!/bin/sh # # script to see if the given value is correct # # Define errors ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies

5. Solaris

Why X-server doesn't read /usr/openwin/lib/locale/C/OWfontpath???

Hi all! Solaris 10. Why did X-server stop to read OWfontpath? Any suggestions. Thanks. (0 Replies)
Discussion started by: wolfgang
0 Replies

6. UNIX for Dummies Questions & Answers

awk Shell Script error : "Syntax Error : `Split' unexpected

hi there i write one awk script file in shell programing the code is related to dd/mm/yy to month, day year format but i get an error please can anybody help me out in this problem ?????? i give my code here including error awk ` # date-month -- convert mm/dd/yy to month day,... (2 Replies)
Discussion started by: Herry
2 Replies

7. UNIX for Dummies Questions & Answers

openwin use old serial mouse

Solaris 10 on an Ultra 45, there are two serial ports (com A and B) And I need to be able to use an old serial trackball mouse in the openwin dt enviornment. Do I have any options? Even if I have to buy an external device for conversion? Want to configure openwin to use an old serial pointer device... (0 Replies)
Discussion started by: ajp7701
0 Replies

8. UNIX for Dummies Questions & Answers

OpenWin error

I have a client who is using Solaris 8 and on login the system tris to open windows but then generates the following error failed to open /usr/openwin/AcceleratedX/etc/Siteinfo Fatal Server error Failed to configure the xserver Help Please! Thanks (0 Replies)
Discussion started by: alvinc77
0 Replies

9. Post Here to Contact Site Administrators and Moderators

/usr/openwin/bin/xinit: unable to connect to Xserver

Hi Gents, I have downloaded Sol 8 2/04 from Sun's web page and I have tried to install it into a V890. I can boot from a CD 1of 2 without any problem. After the selection of the language and the Locale, the TWM (Sol Install Console window) cannot starts up. The following are the errors... (0 Replies)
Discussion started by: mmakhol
0 Replies

10. UNIX for Dummies Questions & Answers

OpenWin Locked up

I have a server that is on solaris 9 and openwin is locked. The mouse won't respond and I can't seem to kill the openwin pid on the server.. Is there a command line to kill openwin from the server side? (2 Replies)
Discussion started by: jphorton
2 Replies
Login or Register to Ask a Question
pgxconfig(1M)						  System Administration Commands					     pgxconfig(1M)

NAME
pgxconfig, GFXconfig, TSIgfxp_config - configure the PGX32 (Raptor GFX) Graphics Accelerator SYNOPSIS
/usr/sbin/pgxconfig [-dev device-filename] [-res video-mode [try | noconfirm | nocheck] ] [-file machine | system] [-depth 8 | 24] [-24only true | false] [-cachedpixmap true | false] [-defaults] /usr/sbin/pgxconfig [-propt] [-prconf] /usr/sbin/pgxconfig [-help] [-res ?] /usr/sbin/pgxconfig [-i] DESCRIPTION
The pgxconfig utility configures the PGX32 (Raptor GFX) Graphics Accelerator and some of the X11 window system defaults for PGX32 (Raptor GFX). A previous version of this utility was named GFXconfig. The first form of pgxconfig shown in the synopsis above stores the specified options in the OWconfig file. These options are used to ini- tialize the PGX32 (Raptor GFX) device the next time the window system is run on that device. Updating options in the OWconfig file provides persistence of these options across window system sessions and system reboots. The second, third, and fourth forms, which invoke only the -prconf, -propt, -help, and -res ? options, do not update the OWconfig file. For the third form all other options are ignored. The -i option starts pgxconfig in interactive mode. Options may be specified for only one PGX32 (Raptor GFX) device at a time. Only PGX32 (Raptor GFX)-specific options can be specified through pgxconfig. The normal window system options for specifying default depth, default visual class and so forth are still specified as device modifiers on the openwin command line. See the Xsun(1) manual page avail- able with the SUNWxwman package. The user can also specify the OWconfig file that is to be updated. By default, the machine-specific file in the /usr/openwin directory tree is updated. The -file option can be used to specify an alternate file to use. For example, the system-global OWconfig file in the /etc/openwin directory tree can be updated instead. Both of these standard OWconfig files can only be written by root. OPTIONS
The following options are supported: -cachedpixmap true | false When set to false, it forces the PGX32 (Raptor GFX) device to use 24-bit only when running OpenWindows. The default value is true. Certain applications make use of a cached pixmap when writing to the display device. Such a technique can cause garbled output and can cause the X server to crash. If you experience such behavior, try setting the -cachedpixmap option to false. -defaults Reset all option values to their default values. -depth 8 | 24 Sets the screen depth to 8 or 24 bits per pixel. 24 bits per pixel enables TrueColor graphics in the window system. -dev device-filename Specify the PGX32 (Raptor GFX) special file. The default is /dev/fbs/gfxp0, or /dev/fbs/raptor0 if applicable. -file machine|system Specifies which OWconfig file to update. If machine is specified, the machine-specific OWconfig file in the /etc/openwin directory tree is updated. If system is specified, the global OWconfig file in the /usr/openwin directory tree is updated. If the specified file does not exist, it is created. This option has no effect unless other options are specified. The default is machine. -help Print a list of the pgxconfig command line options, along with a brief explanation of each. -i Start pgxconfig in interactive mode. -prconf Print the PGX32 (Raptor GFX) hardware configuration. Thie following is a typical display: --- Hardware Configuration for /dev/fbs/gfxp0 --- DAC: version 0x0 Type: Board: PROM: version 0x0 PROM Information: RAM: EDID Data: Monitor Sense ID: Card possible resolutions: 640x480x60, 800x600x75, 1024x768x60 1024x768x70, 1024x768x75, 1280x1024x75, 1280x1024x76 1280x1024x60, 1152x900x66, 1152x900x76, 1280x1024x67 960x680x112S, 960x680x108S, 640x480x60i, 768x575x50i, 1280x800x76, 1440x900x76, 1600x1000x66, 1600x1000x76, vga, svga, 1152, 1280, stereo, ntsc, pal Monitor possible resolutions: 720x400x70, 720x400x88, 640x480x60 640x480x67, 640x480x72, 640x480x75, 800x600x56, 800x600x60, 800x600x72, 800x600x75, 832x624x75, 1024x768x87, 1024x768x60, 1024x768x70, 1024x768x75, 1280x1024x75, 1280x1024x76, 1152x900x66, 1152x900x76, 1280x1024x67, 960x680x112S, vga, svga, 1152, 1280 stereo Current resolution setting: 1280x1024x76 Possible depths: 8, 24, 8+24 Current depth: 8 -propt Print the current values of all PGX32 (Raptor GFX) options in the OWconfig file specified by the -file option for the device specified by the -dev option. Print the values of options as they would be in the OWconfig file after the call to pgxconfig would have completed. The following is a typical display: --- OpenWindows Configuration for /dev/fbs/gfxp0 --- OWconfig: machine Video Mode: not set Depth: 8+24 -res video-mode [try | noconfirm | nocheck ] Specify the built-in video mode used to drive the monitor connected to the specified PGX32 (Raptor GFX) device. The format for video-mode can be one of the following: widthxheightxrate The width is the screen width in pixels, height is the screen height in pixels, and rate is the vertical fre- quency of the screen refresh. As a convenience, -res also accepts formats with @ prepended to the refresh rate rather than x. For example: 1280x1024@76. The list can be obtained by running pgxconfig with the -res ? option (the third form shown in the command synopsis above). Note that not all resolutions are supported by both the video board and by the monitor. The pgxconfig utility will not permit you to set a resolution not supported by the board unless the noconfirm or nocheck option is specified. It will also request confirmation before setting a resolution not supported by the monitor if the nocheck option is not specified. Symbolic names For convenience, the video modes listed below have symbolic names defined. Rather than the form widthx- heightxrate, the symbolic name may be supplied as the argument to -res. If the symbolic name is none, the screen resolution will be the video mode that is currently programmed in the device when the window system is run. svga 1024x768x60 1152 1152x900x76 1280 1280x1024x76 vga 640x480x60 none default console resolution The -res option also accepts additional, optional arguments immediately following the video mode specification. Any or all of these may be present. noconfirm Using the -res option, the user could put the system into an unusable state, a state where there is no video output. This can hap- pen if there is ambiguity in the monitor sense codes for the particular code read. To reduce the chance of this occurring, the default behavior of pgxconfig is to print a warning message to this effect and to prompt the user to find out if it is okay to con- tinue. The noconfirm option instructs pgxconfig to bypass this confirmation and to program the requested video mode anyway. This option is useful when pgxconfig is being run from a shell script. nocheck If present, normal error checking based on the monitor sense code is suspended. The video mode specified by the user will be accepted regardless of whether it is appropriate for the currently attached monitor. (This option is useful if a different monitor is to be connected to the PGX32 (Raptor GFX) device). Use of this option implies noconfirm as well. try This option allows the user to test the specified resolution before committing it. It displays a pattern on the screen with the specified resolution. If the test pattern appears correctly, the user may answer "y" to the query. The other permissable answer is "n". This sub-option should not be used with pgxconfig while the configured device is being used (for example, while running the window system) as unpredictable results may occur. To run pgxconfig with the try sub-option, the window system should be brought down first. -res ? Print the list of possible resolutions supported by the PGX32 and the monitor. -24only Force the PGX32 (Raptor GFX) device to use 24 bit only when running Openwindows. DEFAULTS
For a given invocation of pgxconfig, if an option does not appear on the command line, the corresponding OWconfig option is not updated; it retains its previous value, except for -depth and -24only. A default value is used if a PGX32 (Raptor GFX) option has not been specified with pgxconfig when the window system is run. The option defaults are as follows: -dev /dev/fbs/gfxp0 -file system -res none The default of none for the -res option indicates that when the window system is run, the screen resolution will be the video mode that is currently programmed in the device. EXAMPLES
Example 1: Switching the Resolution on the Monitor Type The following example switches the monitor type to the resolution of 1280 x 1024 at 76 Hz: example# /usr/sbin/pgxconfig -res 1280x1024x76 FILES
/dev/fbs/gfxp0 device special file /usr/openwin/server/etc/OWconfig system configuration file /etc/openwin/server/etc/OWconfig machine configuration file SEE ALSO
PGX32 Installation Manual SunOS 5.10 8 Apr 2004 pgxconfig(1M)