X setup, P9000 server, ViperPCI card, MemBase & IOBase needed

X setup, P9000 server, ViperPCI card, MemBase & IOBase needed

Post by Andrew Joseph Esposi » Fri, 29 Jan 1999 04:00:00



OK, I'm NOT new to Linux.  Ages ago I was running Slackware when the
Linux kernel was pre 1.0.  And ages ago it took me sixteen hours of
calculating the dot timings for my video card and monitor to get X
working.  I don't want to do that again.  And I'm pleased I shouldn't
have to.

I'm running a "straight off the ftp site" version of RedHat 5.2 --
newly formatted hard drives and everything.  I have loaded the P9000
server and have a ViperPCI Weitek P9000 card with 2 meg of memory.

OK.  I read the READMEs and it was documented that I had to explicitly
specify my card's MemBase and IOBase in XF86Config.  Which is probably
why XConfigurator fails to autoconfigure X.  I found documentation
about PCIDUMP.EXE, but nowhere does it mention where you aquire said
program, nor does it specify what OS it runs in.  (I'm not about to
replace my version of RedHat with DOS to run one program!)  I also
found reference to a program called scanpci.  I found this on my
system, ran it, and the output is as follows:

----- begin include -----

PCI says configuration type 1

PCI probing configuration type 1
Probing for devices on PCI bus 0:

pci bus 0x0 cardnum 0x00 function 0x0000: vendor 0x1039 device 0x0406
 SIS 85C501

pci bus 0x0 cardnum 0x01 function 0x0000: vendor 0x1039 device 0x0008
 SIS 85C503

pci bus 0x0 cardnum 0x08 function 0x0000: vendor 0x1de1 device 0xdc29
 Tekram DC290

pci bus 0x0 cardnum 0x0f function 0x0000: vendor 0x10b7 device 0x5950
 3COM 3C595 100bTX

pci bus 0x0 cardnum 0x11 function 0x0000: vendor 0x100e device 0x9001
 Weitek P9000

----- end include -----

The docs say I need to specify the IO Base and the Memory Base.
Anyone care to tell me what is the IO Base and the Memory Base from
the output above???

So, below is my Xf86Config file for another Voodoo Priest to decipher:

----- begin include -----

# File generated by XConfigurator.
# File edited by Andrew Joseph Esposito's own two hands!

#
**********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format
of
# this file.
#
# Or read /usr/X11R6/lib/X11/doc/README.Config.
#
**********************************************************************

#
**********************************************************************
# Files section.  This allows default font and rgb paths to be set
#
**********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath     "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (they are concatenated
together)

    FontPath    "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath    "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath    "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath    "/usr/X11R6/lib/X11/fonts/75dpi/"
#   FontPath    "/usr/X11R6/lib/X11/fonts/100dpi/"

EndSection

#
**********************************************************************
# Server flags section.
#
**********************************************************************

Section "ServerFlags"

    # Uncomment this to cause a core dump at the spot where a signal
is
    # received.  This may leave the console in an unusable state, but
may
    # provide a better stack trace in the core dump to aid in
debugging
    #NoTrapSignals

    # Uncomment this to disable the <Crtl><Alt><BS> server abort
sequence
    # This allows clients to receive this key event.
    #DontZap

    # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode
switching
    # sequences.  This allows clients to receive these key events.
    #DontZoom

EndSection

#
**********************************************************************
# Input devices
#
**********************************************************************

#
**********************************************************************
# Keyboard section
#
**********************************************************************

Section "Keyboard"

    Protocol    "Standard"

    # when using XQUEUE, comment out the above line, and uncomment the
    # following line
    #Protocol   "Xqueue"

    AutoRepeat  500 5

    # Let the server do the NumLock processing.  This should only be
    # required when using pre-R6 clients
    #ServerNumLock

    # Specify which keyboard LEDs can be user-controlled (eg, with
xset(1))
    #Xleds      1 2 3

    #To set the LeftAlt to Meta, RightAlt key to ModeShift,
    #RightCtl key to Compose, and ScrollLock key to ModeLock:

    LeftAlt        Meta
    RightAlt        Meta
    ScrollLock      Compose
    RightCtl        Control

# To disable the XKEYBOARD extension, uncomment XkbDisable.
#    XkbDisable
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    XkbModel    "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#    XkbModel    "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    XkbLayout   "de"
# or:
#    XkbLayout   "de"
#    XkbVariant  "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    XkbOptions  "ctrl:swapcaps"
# These are the default XKB settings for XFree86
#    XkbRules    "xfree86"
#    XkbModel    "pc101"
#    XkbLayout   "us"
#    XkbVariant  ""
#    XkbOptions  ""

   XkbKeycodes     "xfree86"
   XkbTypes        "default"
   XkbCompat       "default"
   XkbSymbols      "us(pc101)"
   XkbGeometry     "pc"
   XkbRules        "xfree86"
   XkbModel        "pc101"
   XkbLayout       "us"
EndSection

#
**********************************************************************
# Pointer section
#
**********************************************************************

Section "Pointer"
    Protocol    "PS/2"
    Device      "/dev/mouse"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
#    Protocol   "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice
#    BaudRate   9600
#    SampleRate 150
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
    Emulate3Buttons
    Emulate3Timeout    50
# ChordMiddle is an option for some 3-button Logitech mice
#    ChordMiddle
EndSection

#
**********************************************************************
# Monitor section
#
**********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "Dell VS17"
    VendorName  "Dell"
    ModelName   "UltraScan"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   30-62

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-90

# This is a set of standard mode timings. Modes that are out of
monitor spec
# are automatically deleted by the server (provided the HorizSync and
# VertRefresh lines are correct), so there's no immediate need to
# delete mode timings (unless particular mode timings don't work on
your
# monitor). With these modes, the best standard mode that your monitor
# and video card can support for a given resolution is automatically
# used.

# 640x400 @ 70 Hz, 31.5 kHz hsync
Modeline "640x400"     25.175 640  664  760  800   400  409  411  450
# 640x480 @ 60 Hz, 31.5 kHz hsync
Modeline "640x480"     25.175 640  664  760  800   480  491  493  525
# 800x600 @ 56 Hz, 35.15 kHz hsync
ModeLine "800x600"     36     800  824  896 1024   600  601  603  625
# 1024x768 @ 87 Hz interlaced, 35.5 kHz hsync
#Modeline "1024x768"    44.9  1024 1048 1208 1264   768  776  784  817
Interlace

# 640x480 @ 72 Hz, 36.5 kHz hsync
Modeline "640x480"     31.5   640  680  720  864   480  488  491  521
# 800x600 @ 60 Hz, 37.8 kHz hsync
Modeline "800x600"     40     800  840  968 1056   600  601  605  628
+hsync +vsync

# 800x600 @ 72 Hz, 48.0 kHz hsync
Modeline "800x600"     50     800  856  976 1040   600  637  643  666
+hsync +vsync
# 1024x768 @ 60 Hz, 48.4 kHz hsync
Modeline "1024x768"    65    1024 1032 1176 1344   768  771  777  806
-hsync -vsync

# 1024x768 @ 70 Hz, 56.5 kHz hsync
Modeline "1024x768"    75    1024 1048 1184 1328   768  771  777  806
-hsync -vsync
# 1280x1024 @ 87 Hz interlaced, 51 kHz hsync
#Modeline "1280x1024"   80    1280 1296 1512 1568  1024 1025 1037 1165
Interlace

# 1024x768 @ 76 Hz, 62.5 kHz hsync
Modeline "1024x768"    85    1024 1032 1152 1360   768  784  787  823
# 1280x1024 @ 61 Hz, 64.2 kHz hsync
Modeline "1280x1024"  110    1280 1328 1512 1712  1024 1025 1028 1054

# 1280x1024 @ 74 Hz, 78.85 kHz hsync
Modeline "1280x1024"  135    1280 1312 1456 1712  1024 1027 1030 1064

# 1280x1024 @ 76 Hz, 81.13 kHz hsync
Modeline "1280x1024"  135    1280 1312 1416 1664  1024 1027 1030 1064

# Low-res Doublescan modes
# If your chipset does not support doublescan, you get a 'squashed'
# resolution like 320x400.

# 320x200 @ 70 Hz, 31.5 kHz hsync, 8:5 aspect ratio
Modeline "320x200"     12.588 320  336  384  400   200  204  205  225
Doublescan
# 320x240 @ 60 Hz, 31.5 kHz hsync, 4:3 aspect ratio
Modeline "320x240"     12.588 320  336  384  400   240  245  246  262
Doublescan
# 320x240 @ 72 Hz, 36.5 kHz hsync
Modeline "320x240"     15.750 320  336  384  400   240  244  246  262
Doublescan
# 400x300 @ 56 Hz, 35.2 kHz hsync, 4:3 aspect ratio
ModeLine "400x300"     18     400  416  448  512  
...

read more »

 
 
 

X setup, P9000 server, ViperPCI card, MemBase & IOBase needed

Post by Andrew Joseph Esposi » Sat, 30 Jan 1999 04:00:00


The answer is:  "scanpci -v12" gives all the pertinent information!

I love it when I answer my own questions.

This message was posted for those people using the Usenet Archive.
Personally, I hate finding a post with the same problem I'm having and
not seeing a reply along with it.

Ola!



>[...]
>I'm running a "straight off the ftp site" version of RedHat 5.2 --
>newly formatted hard drives and everything.  I have loaded the P9000
>server and have a ViperPCI Weitek P9000 card with 2 meg of memory.

>OK.  I read the READMEs and it was documented that I had to explicitly
>specify my card's MemBase and IOBase in XF86Config.  Which is probably
>why XConfigurator fails to autoconfigure X.  I found documentation
>about PCIDUMP.EXE, but nowhere does it mention where you aquire said
>program, nor does it specify what OS it runs in.  (I'm not about to
>replace my version of RedHat with DOS to run one program!)  I also
>found reference to a program called scanpci.  I found this on my
>system, ran it, and the output is as follows:

>----- begin include -----
>[...]

>pci bus 0x0 cardnum 0x11 function 0x0000: vendor 0x100e device 0x9001
> Weitek P9000

>----- end include -----

>The docs say I need to specify the IO Base and the Memory Base.
>Anyone care to tell me what is the IO Base and the Memory Base from
>the output above???

--
Andrew Joseph Esposito
Systems Administrator
FM Strategies, a division of Little and Associates Architects

* phone: 704-561-4600 * 5815 Westpark Dr. C*te NC 28217 *