Technical article 126647

After installing SCO OpenServer 6 Maint. Pack 2 (MP2) on Fujitsu-Siemens-Computers PRIMERGY TX150-S5 or TX200-S3 or TX300-S3, the X-server display (X-scologin) fails to start.

OpenServer 6.0.0

Written · Last revised

Problem

Before I installed SCO OpenServer 6.0.0 Maintenance Pack 2 (MP2) on my Fujitsu Siemens PRIMERGY TX150-S3 / TX200-S3 / TX300-S3, the Xorg Xserver X-scologin display started OK on TTY02 screen.

But after installing SCO OpenServer MP2, the Xserver X-scologin display fails to start on TTY02 screen.

These are the last lines in the /var/adm/Xorg.0.log file of a successful Xserver display before MP2 was installed:

-----
(II) Reloading /usr/X11R6/lib/modules/libint10.a
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 1664 kB
(II) VESA(0): VESA VBE OEM: Matrox Graphics Inc.
(II) VESA(0): VESA VBE OEM Software Rev: 3.6
(II) VESA(0): VESA VBE OEM Vendor: Matrox
(II) VESA(0): VESA VBE OEM Product: MGA-G200
(II) VESA(0): VESA VBE OEM Product Rev: 00
(II) VESA(0): virtual address = bfcc3000,
        physical address = 0xfc000000, size = 1703936
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Backing store disabled
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(**) Option "Protocol" "Xqueue"
(**) Mouse0: Protocol: Xqueue
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(==) Mouse0: Buttons: 3
(==) Mouse0: Setting wheel resolution to 1
(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "Xqueue"
(**) Keyboard0: Protocol: Xqueue
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "gb"
(**) Keyboard0: XkbLayout: "gb"
(WW) Option "XkbVariant" requires an string value
(**) Option "Panix106" "off"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard0"
(type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type:
MOUSE)
-----

This is the error message in the /var/adm/Xorg.0.log file after installing MP2:

-----
(II) Reloading /usr/X11R6/lib/modules/libint10.so
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 1664 kB
(II) VESA(0): VESA VBE OEM: Matrox Graphics Inc.
(II) VESA(0): VESA VBE OEM Software Rev: 3.6
(II) VESA(0): VESA VBE OEM Vendor: Matrox
(II) VESA(0): VESA VBE OEM Product: MGA-G200
(II) VESA(0): VESA VBE OEM Product Rev: 00
(II) VESA(0): virtual address = bf758000,
        physical address = 0xfc000000, size = 1703936
(II) VESA(0): VBESetVBEMode failed
(EE) VESA(0): Set VBE Mode failed!
Fatal server error:
AddScreen/ScreenInit failed for driver 0
Please consult the The X.Org Foundation support
         at http://wiki.X.Org
 for help.
Please also check the log file at "/var/adm/Xorg.0.log"
for additional information.
-----

HARDWARE: Fujitsu Siemens PRIMERGY TX150-S5, TX200-S3, TX300-S3 Matrox G200E graphics chipset from ServerEngines

Cause

This is caused by a BIOS bug in the ServerEngines' integrated MATROX G200E Graphic Chip which manifests itself in SCO OpenServer6 MP2 that include Xorg package 6.9.0 update.

This BIOS bug has been reported on all Intel based Unix / windows operating systems that are installed on OEM Servers that use ServerEngine Matrox G200E Video Chip.

Solution

This has been fixed in SCO OpenServer oss703a Patch: The X Server Upgrade for Maintenance Pack 2.

Available at:
http://www.sco.com/support/update/download/release.php?rid=182

Please read the OSS703a Cover Letter for details.

Once installed, restart the scologin:
# scologin stop
# scologin start

The Xserver Xscologin display will now start successfully on TTY02 screen.

The oss703a has also an updated Xorg "mga" Matrox video driver.

You can exchange it with the generic "vesa" driver in the /etc/xorg.conf file in the Device section if you want to use the native Matrox "mga" video driver:

from --> Driver      "vesa"
to ----> Driver      "mga"
Restart scologin again.
NOTES:    ServerEngines are in the process of issuing a BIOS update
          for their ServerEngine chips that fixes the video Matrox
          G200E BIOS bug and will be handing it to all OEMs that use
          ServerEngine Chips. With this BIOS fix, you will not need to install
          oss703a patch any more.

From the Xinuos technical article database, record 126647. Reproduced with permission. The original is at www.sco.com/ta/126647, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.