|
I will assume this is an internal system, and not for a customer...
This question would be better suited to the Open3D (BGSDEV::OPEN3D)
or DECwindows (BULOVA::DECWINDOWS) notes conferences -- if that board
is supported by a package outside the OpenVMS kit and the DECwindows
kit, it is likely present in Open3D kit.
When looking at the Open3D kit, don't blindly pull over and install
the latest version without determining if that version supports both
V7.1 and that board.
(This is the generic-Alpha and porting-to-Alpha conference...)
|
|
Hi,
Thanks for your promptly reply...
This driver is to configure a system that will be ship to the
customer. Usually this system comes with a diskette with a driver for
the graphical board for the Operating System (OpenVMS 7.1), but we did
not receive it.
This is a specific driver for this board (ATIMach64 ISA) and I'm
not sure if it's inside of Open3D. And the customer does not have the
Open3D license.
Thanks in advance,
Carlos Morey
|
| : This driver is to configure a system that will be ship to the
: customer. Usually this system comes with a diskette with a driver for
: the graphical board for the Operating System (OpenVMS 7.1), but we did
: not receive it.
: This is a specific driver for this board (ATIMach64 ISA) and I'm
: not sure if it's inside of Open3D.
: And the customer does not have the Open3D license.
The license is not needed for 2D operations. Drivers shipped with
OpenVMS often first appear or are first updated on the Open3D kit,
as it ships more frequently than OpenVMS.
---
Two articles found via a COMET search (see note 10.*)...
---
TITLE: [OpenVMS,Motif] No Graphics Devices Found ISA/PCI Systems w. ATI Mach64GX
PRODUCTS: DECwindows Motif[R] for OpenVMS, Version 1.2-4
OpenVMS Alpha, Version 7.1
ATI MACH64-GX(ISA) GRAPHICS (PB2GA-FB)
COMPONENT: DECwindows Server
DECwindows ISA Device Support Subsystem
SOURCE: Digital Equipment Corporation
SYMPTOM:
On ISA/PCI based systems (ie, AlphaStation 200 through 400, or
AlphaServer 300) equipped with a ISA based ATI Mach64-GX PB2GA-FB
graphics card, DECwindows fails to start giving the following error
message:
%DECW-W-NODEVICE, No graphics device found on this system
-DECW-I-NODECW, DECwindows graphics drivers will not be loaded
DIGITAL RESPONSE:
Engineering has acknowledged this problem and plans to address it on a
future release.
\
\
\ ENGINEERING RESPONSE:
\
\ Provided by John Bruce, OpenVMS Problem Management, 29-APR-97:
\
\ Placing this case in the Solved state, per the previous update.
\
\
\ Update mentioned above - 29-APR-97:
\
\ I've copied the decw$icbm.exe image with the fix to
\ bulova::decw$public:[server.v71]. Customers should copy this to
\ sys$library on their systems.
\
\ CSC NOTE - 22-May-1997:
\
\ The new image from Engineering can be found in the directory below:
\
\ CSC32::DOCROOT:[COMMON.INTDRV.ENG_IMAGES.HPAQ217J0]
\
\ Directory DOCROOT:[COMMON.INTDRV.ENG_IMAGES.HPAQ217J0]
\
\ DECW$ICBM.EXE;1 99 (RWED,RWED,RWE,RE)
\
\ An official ECO is not yet available in TIMA. When it is, please
\ comment on this article. Do not delete the above file without
\ commenting on the article with a valid reason for the file deletion.
WORKAROUND 1:
Contact Digital Customer Support for a workaround to this problem.
WORKAROUND 2:
Execute the following steps to avoid this problem:
1) Ensure that the SYSGEN parameter WINDOW_SYSTEM is set to 1:
$ MCR SYSGEN SHOW WINDOW_SYSTEM
If it is not set to a value of 1, issue the commands:
$ MCR SYSGEN
SYSGEN> USE CURRENT
SYSGEN> SET WINDOW_SYSTEM 1
SYSGEN> WRITE ACTIVE
SYSGEN> WRITE CURRENT
SYSGEN> EXIT
$ REBOOT
2) Check the SYSMAN IO PREFIX LIST to ensure that the DECW$ prefix is
included in the existing list. If it is not, you will need to add it:
$ MCR SYSMAN
SYSMAN> IO SHOW PREFIX
SYSMAN> IO SET PREFIX=(DECW$,*) * = list returned by the show command
SYSMAN> IO AUTO/LOG
SYSMAN> EXIT
3) Ensure that the image SYS$SHARE:DECW$ICBM.EXE is installed in memory.
If it is not installed, then install it:
$ INSTALL LIST/FULL SYS$SHARE:DECW$ICBM
$ INSTALL REPLACE SYS$SHARE:DECW$ICBM
$ EDIT SYS$MANAGER:SYCONFIG.COM
$! The following line was added to install
$! support for the Mach64 Graphics Card
$!
$ INSTALL REPLACE SYS$SHARE:DECW$ICBM
$ ^Z
$ SHUTDOWN
REBOOT the system.
If the system still complains that NO GRAPHICS DEVICES COULD BE FOUND
then:
4) o Boot the system as normal
o Login as "system"
o Create the file:
$ SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT (W:RE)
o Add the following string on the very first line:
CLEAR_PFLAG = ISA_4BYTE
o Save the file
o Set the file protections
o Reboot the system
EXAMPLE:
$ create SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT
CLEAR_PFLAG = ISA_4BYTE
^Z
$ SET FILE/PROTECTION=(W:RE) SYS$COMMON:[SYSMGR]DECW$USER_AUTOCONFIG.DAT
$ REBOOT
\
\
\ WORKAROUND 3:
\
\ This workaround is marked as non-customer viewable and is
\ intended for support personnel only!
\
\ This workaround changes the default handle
\ name for the ISA MACH 64 video card. It could be used to get windows
\ going in the event that the system is not yet configured on the network
\ or some other obscure problem that would prevent you from creating the
\ file. (ie, file already exists and has configuration data for other
\ options that are required etc...)
\
\ o Shut down the system to the SRM console prompt
\ o Issue the command: >>> SHOW CONFIG
\ o Write down the slot number that the card (ISA--VGA) is configured in
\ o Issue the command: >>> isacfg -mod -slot X -handle ISA-
\ where:
\ isacfg = isa configuration
\ -mod = modify
\ -slot = slot specification
\ X = slot number the card is installed in
\ -handle = ISA Device handle
\ ISA- = is the 4 byte handle for the video option.
\
\ o Reinit the system: >>> INIT
\ o REBOOT
ANALYSIS:
A change was made to the way OpenVMS looks at the ISA device handles.
Previous versions of OpenVMS only checked the first 4 bytes of the
device handle to determine which ISA graphics option was installed.
With version 7.1 all eight bytes are now examined by the operating
system; however, the DECW$ICBM logic was not updated to use the full 8
bytes.
NOTE: PCI based ATI Mach64 options and ISA based ATI Mach64 options
installed in EISA slots are not affected by this change.
[R] Motif is a registered trademark of the Open Software Foundation, Inc.
\
\
\ REFERENCES:
\
\ Escalations reported on this problem:
\
\ CHAMP/CSC Service Request (SRQ) #: C970212-4210
\ Field Service Log #: HPAQ217J0
\ IPMT Case_id: CFS.49189
\
\
\ CONTRIBUTORS:
\
\ Technical:
\ Rick Retterer (306346)
\ Dave Bechtold (154097)
\ Jay Word (81352)
\
\ Editorial:
\ Peggy Annin (140028)
\
\\ SOURCE=DIGITAL DWVMS SERVER
\\ PROD=OPENVMS-AXP SPD=41.87 CAT=OPSYS GRP=OPENVMS-AXP OS=OPENVMS-AXP
\\ PROD=MOTIF CAT=OPSYS GRP=USER_INTERFACE OS=OPENVMS-AXP SPD=42.19
\\ 306346 154097 081352
\\ HPAQ217J0 SRC970212004210 EDIT_SRQ=C970311-2983
\\ TYPE=KNOWN_PROBLEM TYPE=ESCALATION RETEST
----
UNIQUE_IDENTIFIER: 0099CE1F-474DF125-1C007A
TITLE: {Draft} ATI MACH64 installed, but DECwindows does not start
NOEDITORIAL_REVIEWED,FIELD_READABLE,NOFLASH,TECHNICAL_REVIEWED,NOREADY)
Copyright (c) Digital Equipment Corporation 1996. All rights reserved.
SOURCE: Digital Equipment Corporation
Product: ISA ATI MACH64, PB2GA-FB
\by: Ed Burkhalter CSC Atlanta
\
Problem:
A new Alphaserver 2100 is shipped with AXP VMS 6.2 installed. AXP VMS
6.2 boots, but DECwindows does not start up. $SH DEV does not see
the Gxxx graphics controller.
Solution:
There should be a QA-4X4AA-HC floppy sent with the system. This floppy
has the VMS software necessary for the ATI MACH 64 card under 6.2 VMS.
Use VMSINSTAL to load the patch. The patch is also in AXPGUP01_062.
QA-3X4AA-HC may be the software necessary for the ISA ATI Mach64 under
Windows Nt.
\by Ed Burkhalter (26970)
\\MAIL_EXPRESS DB=AXP_HARDWARE ADDR=QBUS::E_BURKHALTER NOCR
|