[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20000818: 20000818: 20000818: problem with 8 bit color and ldm error
- Subject: 20000818: 20000818: 20000818: problem with 8 bit color and ldm error
- Date: Fri, 18 Aug 2000 15:33:06 -0600
Rajul,
What you need you need to do is exit out to the root command line login
prompt and run "kdmconfig". Once in kdmconfig, chose an 8 bit display setting
that matches your monitor. CDE will automatically launch using the visual you
define kdmconfig. This is slightly different than the SPARC solaris
way of defining multiple visuals such as you found in the support archives.
Steve Chiswell
>From: "Pandya, Rajul E." <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200008182015.e7IKFwN29048
>Hi Steve,
>
>Thanks for your help. At this point I am lost though. Which logs should I
>examine? If I specify nothing, it knows what to do. As soon as I specify a
>device it balks. I did a truss command to trace the system calls, but that
>only pointed to devices like /dev/pm0 and /dev/svr0, none of which worked
>when I tried them after the -dev command.
>
>Any idea what logs I should look at. If I could figure out what device is
>used by no -dev specification, or if I could figure out a way to set it to 8
>bits without specifying a device, I'd be in good shape I think.
>
>Anyway, any help you could give would be _much_ appreciated. I am in over my
>head, I think.
>
>Thanks,
>Rajul
>
>
>> -----Original Message-----
>> From: Unidata Support [SMTP:address@hidden]
>> Sent: Friday, 18 August 2000 14:31
>> To: Pandya, Rajul E.
>> Cc: 'Unidata Support'
>> Subject: 20000818: 20000818: problem with 8 bit color and ldm error
>>
>>
>> Rajul,
>>
>> The output below shows that you are running with a 24 bit
>> true color display as the default visual:
>>
>> > default visual id: 0x20
>> > visual:
>> > visual id: 0x20
>> > class: TrueColor
>>
>> This does have to be configured to be 8 bit pseudocolor.
>>
>> The "defdepth 8" or "defclass PseudoColor" should be the
>> appropriate option in the Xservers. You may have to examing your
>> logs to find out what the appropriate /dev is for your system.
>>
>> Steve Chiswell
>>
>>
>> >From: "Pandya, Rajul E." <address@hidden>
>> >Organization: UCAR/Unidata
>> >Keywords: 200008181702.e7IH2IN23459
>>
>> >Hi Steve,
>> >
>> >Thanks for the quick response. My replies are interspersed below.
>> >
>> >> -----Original Message-----
>> >> From: Unidata Support [SMTP:address@hidden]
>> >> Sent: Friday, 18 August 2000 12:09
>> >> To: Pandya, Rajul E.
>> >> Cc: 'address@hidden'
>> >> Subject: 20000818: problem with 8 bit color and ldm error
>> >>
>> >>
>> >> Rajul,
>> >>
>> >> Did you run the "xdpyinfo" command before trying to make modifications
>> to
>> >> Xservers?
>> >>
>> > I did, and I am nearly positive it is in 8-bit mode. Here is the
>> >output, though, after starting with an Xservers that says only
>> > :0 Local local_uid@console root /usr/openwin/bin/Xsun :0
>> >-nobanner
>> >
>> > Here is the output of xdpyinfo:
>> >
>> > name of display: :0.0
>> > version number: 11.0
>> > vendor string: Sun Microsystems, Inc.
>> > vendor release number: 3610
>> > maximum request size: 262140 bytes
>> > motion buffer size: 256
>> > bitmap unit, bit order, padding: 32, LSBFirst, 32
>> > image byte order: LSBFirst
>> > number of supported pixmap formats: 6
>> > supported pixmap formats:
>> > depth 1, bits_per_pixel 1, scanline_pad 32
>> > depth 4, bits_per_pixel 8, scanline_pad 32
>> > depth 8, bits_per_pixel 8, scanline_pad 32
>> > depth 15, bits_per_pixel 16, scanline_pad 32
>> > depth 16, bits_per_pixel 16, scanline_pad 32
>> > depth 24, bits_per_pixel 32, scanline_pad 32
>> > keycode range: minimum 8, maximum 136
>> > focus: window 0x4c00009, revert to PointerRoot
>> > number of extensions: 25
>> > AccessX
>> > Adobe-DPS-Extension
>> > DOUBLE-BUFFER
>> > DPMS
>> > DPSExtension
>> > Extended-Visual-Information
>> > LBX
>> > MIT-SCREEN-SAVER
>> > MIT-SHM
>> > MIT-SUNDRY-NONSTANDARD
>> > Multi-Buffering
>> > RECORD
>> > SECURITY
>> > SHAPE
>> > SUN_ALLPLANES
>> > SUN_DGA
>> > SUN_SME
>> > SYNC
>> > SolarisIA
>> > TOG-CUP
>> > XC-APPGROUP
>> > XC-MISC
>> > XInputDeviceEvents
>> > XInputExtension
>> > XTEST
>> > default screen number: 0
>> > number of screens: 1
>> >
>> >screen #0:
>> > dimensions: 1280x1024 pixels (361x288 millimeters)
>> > resolution: 90x90 dots per inch
>> > depths (2): 1, 24
>> > root window id: 0x25
>> > depth of root window: 24 planes
>> > number of colormaps: minimum 1, maximum 1
>> > default colormap: 0x22
>> > default number of colormap cells: 256
>> > preallocated pixels: black 0, white 16777215
>> > options: backing-store YES, save-unders YES
>> > largest cursor: 64x64
>> > current input event mask: 0x78003f
>> > KeyPressMask KeyReleaseMask ButtonPressMask
>> >
>> > ButtonReleaseMask EnterWindowMask LeaveWindowMask
>> >
>> > SubstructureNotifyMask SubstructureRedirectMask FocusChangeMask
>> >
>> > PropertyChangeMask
>> > number of visuals: 2
>> > default visual id: 0x20
>> > visual:
>> > visual id: 0x20
>> > class: TrueColor
>> > depth: 24 planes
>> > available colormap entries: 256 per subfield
>> > red, green, blue masks: 0xff0000, 0xff00, 0xff
>> > significant bits in color specification: 8 bits
>> > visual:
>> > visual id: 0x21
>> > class: DirectColor
>> > depth: 24 planes
>> > available colormap entries: 256 per subfield
>> > red, green, blue masks: 0xff0000, 0xff00, 0xff
>> > significant bits in color specification: 8 bits
>> >
>> >
>> >
>> >> Output from that command would be useful in determining if your machine
>> >> normally boots with the default visual as 8 bit pseudocolor. In that
>> case
>> >> you don't need to modify the Xservers file. If you do, the command
>> >> line arguments to Xsun are in the manpage:
>> >>
>> >> setenv MANPATH /usr/openwin/man:${MANPATH}
>> >> man Xsun
>> >>
>> > The man pages suggest that what I am doing is ok. Here is the text
>> >of the man pages:
>> >
>> >User Commands Xsun(1)
>> >
>> >
>> >
>> >NAME
>> > Xsun - Solaris server for X Version 11
>> >
>> >SYNOPSIS
>> > Xsun [ option ] ...
>> >
>> >DESCRIPTION
>> > Xsun is the Solaris server for Version 11 of the X window
>> > system on Solaris hardware. It is normally started by
>> > xinit(1) via openwin(1).
>> >
>> >OPTIONS
>> > In addition to the options described in Xserver(1), Xsun
>> > accepts the following command-line switches:
>> >
>> > -dev filename
>> > This option specifies the name of the framebuffer
>> > device file to be used instead of the default frame-
>> > buffer /dev/fb. Multiple instances of this option
>> > indicate multiple screens on the same server. After
>> > each -dev option a list of modifiers changes the
>> > behavior of the named device.
>> >
>> > [ left | right | top | bottom ]
>> > Specify the position of a given screen in rela-
>> > tion to the previous one on the command line.
>> > The default right.
>> >
>> > dpix n
>> > The dpi in the x direction for this screen is
>> > n. The default is 90.
>> >
>> > dpiy n
>> > The dpi in the y direction for this screen is
>> > n. The default is 90.
>> >
>> > defclass [ GrayScale | StaticGray | PseudoColor |
>> > StaticColor | DirectColor | TrueColor ] Use the
>> > specified visual as the default visual. The
>> > default is device dependent.
>> >
>> > defdepth n
>> > A visual of depth n is the default visual. The
>> > default is device dependent.
>> >
>> > grayvis
>> > Only report GrayScale and/or StaticGray visu-
>> > als.
>> >
>> > The following is an example of the -dev option that
>> > might be used on a system with a cg6 and a bw2:
>> >
>> >
>> >
>> >
>> >SunOS 5.7 Last change: 30 January 1997 1
>> >
>> >
>> >
>> >
>> >
>> >
>> >User Commands Xsun(1)
>> >
>> >
>> >
>> > -dev /dev/cgsix0 defclass GrayScale -dev
>> > /dev/bwtwo0 right
>> >
>> > The Xsun server also supports the format used by the
>> > X11R6 sample X Server. Multiple screen systems are
>> > specified by using the following syntax on the com-
>> > mand line:
>> >
>> > -dev <device 1>:<device 2>:...:<device n>
>> >
>> > The server uses device 1 as screen 0, device 2 as
>> > screen 1, etc., and the server assumes that screens
>> > are ordered left to right in ascending screen
>> > number. This means that the cursor moves off the
>> > right side of screen n and onto the left side of
>> > screen n + 1. When this format is used, no other
>> > -dev options are valid.
>> >
>> >
>> >> If you are in 8 bit pseudocolor, then you will want to ensure that
>> >> the "ntl" program can access the colors it needs. Some Solaris CDE
>> >> programs
>> >> such as the anserbook that come up automatically steal lots of colors
>> >> and may have to be shut down before running GEMPAK.
>> >>
>> >> Please send the xdpyinfo putput if you aren't sure if your default
>> >> visual is 8 0r 24 bits.
>> >>
>> > So I think that my edit of /etc/dt/config/Xservers should be ok,
>> >according to the man pages, anyway. Once again, the command issued in
>> that
>> >file when I am trying to get 8 bit color is:
>> >
>> > :0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner
>> >-dev /dev/fb defdepth 8 defclass PseudoColor
>> >
>> >
>> >
>> >> I'll forward the LDM question to others to answer.
>> > Ok, thanks.
>> >
>> > Rajul
>> >
>> >
>> >> Steve Chiswell
>> >>
>> >> >Hi,
>> >> >
>> >> >I have two problems, one with the setting the default color on the PC
>> >> >running Solaris, and the other with a strange message from ldmadmin.
>> >> >
>> >> >First the Color Problem:
>> >> >
>> >> >I have installed the binary of Gempak and things seem to be installed
>> >> >correctly, as much as I can tell, but I can't seem to switch the
>> display
>> >> to
>> >> >8 bit Pseudo color. From looking through the email archives, I think I
>> >> >needed to have an /etc/dt/config/Xservers file with a command like:
>> >> >
>> >> > :0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner
>> -dev
>> >> >/dev/fb defdepth 8 defclass PseudoColor
>> >> >
>> >> >Unfortunately, this command, or any that uses the -dev flag causes
>> Xsun
>> >> to
>> >> >bomb and write the following messdage to /var/dt/Xerrors:
>> >> >
>> >> >Fatal server error:
>> >> >InitOutput: Error loading module for /dev/fb
>> >> >
>> >> >
>> >> >Fri Aug 18 08:30:00 2000
>> >> >error (pid 261): Server for display :0 terminated unexpectedly 1
>> >> >The loadable module for the display device /dev/fb is not installed.
>> >> >
>> >> >
>> >> >I tried a couple of other devices, (/dev/vt100, /dev/dtty) just for
>> fun
>> >> and
>> >> >got no better results.
>> >> >
>> >> >Anyway, here is the results of uname and a listing of /dev/fb.
>> >> >
>> >> >rossby:/# uname -a
>> >> >SunOS rossby.wcupa.edu 5.7 Generic_106542-08 i86pc i386 i86pc
>> >> >
>> >> >
>> >> >rossby:/# ls -l /dev/fb
>> >> >lrwxrwxrwx 1 root other 30 Apr 17 16:22 /dev/fb ->
>> >> >../devices/isa/
>> >> >chanmux:chanmux
>> >> >
>> >> >
>> >> >I am completely stumped. Any help would be great.
>> >> >
>> >> >Rajul Pandya
>> >> >Department of Geology and Astronomy
>> >> >West Chester University
>> >> >West Chester, PA 19383
>> >> >V:610.436.2213 F:610.436.3036
>> >> >http://geology.wcupa.edu/~rpandya
>> >> >
>> >>
>> >>
>> **************************************************************************
>> >> Unidata User Support UCAR Unidata
>> >> (303)497-8644 P.O. Box
>> >> address@hidden Boulder, CO
>> >>
>> --------------------------------------------------------------------------
>> >> Unidata WWW Service http://www.unidata.ucar.edu/
>> >>
>> **************************************************************************
>> >
>>
>> **************************************************************************
>> Unidata User Support UCAR Unidata
>> (303)497-8644 P.O. Box
>> address@hidden Boulder, CO
>> --------------------------------------------------------------------------
>> Unidata WWW Service http://www.unidata.ucar.edu/
>> **************************************************************************
>