[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: startx from 3.3.3.1-8



On Wed, 23 Jun 1999, Bob Nielsen wrote:

> Shouldn't this be 'startx -- -bpp 16'?  This works for me:
You are completely right.  It was a mistake of mine because I used 
a script and my brain failed in remembering what was done exactly.


(--) Mach64: PCI: Mach64 VT rev 64, Aperture @ 0xe0000000, Block I/O @
0x6200
(--) Mach64: Card type: PCI
(--) Mach64: Memory type: EDO (3)
(--) Mach64: Clock type: Internal
(--) Mach64: Maximum allowed dot-clock: 200.000 MHz
(**) Mach64: Mode "1024x768": mode clock =  75.000
(**) Mach64: Mode "800x600": mode clock =  50.000
(**) Mach64: Mode "640x480": mode clock =  45.800
(**) Mach64: Virtual resolution: 1160x870
(--) Mach64: Video RAM: 2048k
(--) Mach64: Using hardware cursor
(--) Mach64: Using 16 MB aperture @ 0xe0000000
(--) Mach64: Ramdac is Internal
(--) Mach64: Ramdac speed: 200 MHz
(**) Mach64: Color weight: 565
(--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 slots
(--) Mach64: Font cache: 0 fonts


> (**) SVGA: Using 16 bpp, Depth 16, Color weight: 565

As you see, the 16 bpp addition is missing and I'm really sure that
it was displayed before when I used the slink packages.

The output of xdpyinfo says:

name of display:    :0.0
version number:    11.0
vendor string:    The XFree86 Project, Inc
vendor release number:    3330
maximum request size:  4194300 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    2
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
keycode range:    minimum 8, maximum 134
focus:  window 0x2400014, revert to Parent
number of extensions:    19
    BIG-REQUESTS
    DOUBLE-BUFFER
    DPMS
    LBX
    MIT-SCREEN-SAVER
    MIT-SHM
    MIT-SUNDRY-NONSTANDARD
    RECORD
    SECURITY
    SHAPE
    SYNC
    XC-APPGROUP
    XC-MISC
    XFree86-DGA
    XFree86-Misc
    XFree86-VidModeExtension
    XInputExtension
    XKEYBOARD
    XTEST
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    1160x870 pixels (393x295 millimeters)
  resolution:    75x75 dots per inch
  depths (1):    16
  root window id:    0x25
  depth of root window:    16 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x21
  default number of colormap cells:    64
  preallocated pixels:    black 0, white 65535
  options:    backing-store YES, save-unders YES
  largest cursor:    64x64
  current input event mask:    0x58003d
    KeyPressMask             ButtonPressMask          ButtonReleaseMask        
    EnterWindowMask          LeaveWindowMask          SubstructureNotifyMask   
    SubstructureRedirectMask PropertyChangeMask       
  number of visuals:    1
  default visual id:  0x20
  visual:
    visual id:    0x20
    class:    TrueColor
    depth:    16 planes
    available colormap entries:    64 per subfield
    red, green, blue masks:    0xf800, 0x7e0, 0x1f
    significant bits in color specification:    6 bits

So it seems to be OK.  But I wonder why some images look disturbed which
where OK with XF86 3.3.2.  Do I have to use a new configuration file
XF86Config for 3.3.3.1?  I've used just the old one.

Kind regards

        Andreas.




Reply to: