On 27-May-2002 Brian A. Seklecki wrote:
> MH> The latter. Use "X -configure" now.
> 
> right, there's a -probe or -probeonly to replace SuperProbe.  There should
> be an X11R6/bin/xf86cfg program to replace XF86Setup.

this did sure answer my XF86Setup question.
thanx both! for aswering.

may i address xf86cfg question?

now i know xf86cfg, it gives me problems..
i used same disk at 2 stations
one's
vga1 at pci0 dev 13 function 0: Rendition Inc. product 0x2000 (rev. 0x02)
the other
vga1 at pci0 dev 13 function 0: Trident Microsystems TGUI 9440 (rev. 0xe3)

xf86cfg (and X -configure) do 'something' on scrn
then blackout the scrn.. and XFree86.8.log ends w/

(**) Option "Device" "/dev/mouse"
(==) Mouse0: Buttons: 3
(II) Keyboard "Keyboard0" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)

Fatal server error:
Caught signal 10.  Server aborting


When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.8.log".
Please report problems to xfree86@xfree86.org.

(II) TRIDENT(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000


and on the serial console (serial boot) it showes one thing extra:
xf86OpenConsole.



now again..i don't know what's going on (( ...
or what to do next...
is it i did f.i. forget to edit XF86Config.new?
or is it cause i have serial boot?
or wrong monitor (did swap as well)

to be as complete as possible, found these:

(II) TRIDENT(0): VESA BIOS detected
(II) TRIDENT(0): VESA VBE Version 1.2
(II) TRIDENT(0): VESA VBE Total Mem: 1024 kB
(II) TRIDENT(0): VESA VBE OEM: TRIDENT MICROSYSTEMS INC.
(WW) TRIDENT(0): remove MTRR d5200000 - d5210000
(--) TRIDENT(0): Revision is 1
(==) TRIDENT(0): Using SW cursor
(--) TRIDENT(0): Found TGUI9440AGi chip
(--) TRIDENT(0): RAM type is Standard DRAM
(--) TRIDENT(0): VideoRAM: 1024 kByte
(--) TRIDENT(0): Memory Clock is 56.48 MHz
(==) TRIDENT(0): Min pixel clock is 12 MHz
(--) TRIDENT(0): Max pixel clock is 90 MHz
(WW) TRIDENT(0): Monitor0: Using default hsync range of 28.00-33.00kHz
(WW) TRIDENT(0): Monitor0: using default vrefresh range of 43.00-72.00Hz
(II) TRIDENT(0): Clock range:  12.00 to  90.00 MHz
(II) TRIDENT(0): Not using default mode "640x350" (hsync out of range)
(II) TRIDENT(0): Not using default mode "320x175" (bad mode
clock/interlace/doublescan)
(II) TRIDENT(0): Not using default mode "640x400" (hsync out of range)
(II) TRIDENT(0): Not using default mode "320x200" (bad mode
clock/interlace/doublescan)

dunno if them hsyncs out of range hurt?

??,
~n

-- 
------------------------------------
  ## UNIX's an abbreviation ##
    * my pc's my backplane _*
------------------------------------