| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 639.1 | | UTRTSC::utoras-198-48-95.uto.dec.com::JurVanDerBurg | Change mode to Panic! | Mon May 26 1997 02:06 | 5 |
| You need "Multimedia Services Version 2.0 for OpenVMS Alpha",
order number AE-QN8LB-TE, also known as MMOV.
Jur.
|
| 639.2 | Pointers... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Tue May 27 1997 10:44 | 10 |
|
BULOVA::DECWINDOWS would be a better spot for DECwindows questions,
and BGSDEV::MULTIMEDIA_SERVICES would be a better spot for the
Multi-Media questions.
The two packages of interest will be the Multi-Media-Video (MMOV)
kit, and the Open3D kit -- between the two, you should have the
drivers you need. Make *sure* you install the correct version of
each of these kits for your particular hardware and software...
|
| 639.3 | Still won't work after MM Service installed | HGOV05::MICHAELWAN | | Thu Jun 05 1997 07:29 | 24 |
| I still have problems with the graphic card after I've installed
Multimedia service. I posted my question on the DECWindows and
Multimedia Service notes file but no one answered, so I have to try
this notes file again.
After I installed the Multimedia Service kit, the console workstation
still cannot work.
When I did '$ decw$device', the message was:
-->
%DECW$DEVICE-W-NODEVICE, no graphics devices found.
The output of '$show dev g /full' was:
-->
Device GPA0:, device type DECwindows output device, is offline,
record-orienteddevice, carriage control, shareable.
I checked the system and noticed that the mmov$server process was
running and there was no error message in the log file.
I am sure that the graphic card is OK, since I can run X-windows with
multi-media service installed on Digital UNIX with another drive.
|
| 639.4 | Is It Even Supported? | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Thu Jun 05 1997 10:38 | 10 |
|
Assuming the controller is listed in the DECwindows, MMOV, and/or
Open3D SPDs, and assuming WINDOW_SYSTEM is non-zero and no error
messages are logged at startup, then elevate this via IPMT, please.
If the controller is not listed in the SPD, then it is likely not
supported.
OpenVMS SPDs are available in the kit distribution areas mentioned
in notes 8.* and 9.*. You'll have to check with the DECwindows
and MMOV folks for the locations of their SPDs.
|
| 639.5 | | UTRTSC::utojvdbu1.uto.dec.com::JurVanDerBurg | Change mode to Panic! | Fri Jun 06 1997 03:06 | 12 |
| If the device is offline then you may need to check the configuration. I had
similar problems with a AV301 board in an Alphastation 400, and the problem was
caused because in that configuration we ran out of interrupts. And if that happens
one of the devices on the PCI bus does not get an interrupt assigned, causing the
device to stay offline. How does the configuration look? You may try to disable
one of the com ports to free an interrupt, that's what we did.
Nice to see that problems from the pc architecture are showing up on Alpha's as well....
Jur.
|
| 639.6 | It's a Trubo Channel machine. | HGOV06::MICHAELWAN | | Fri Jun 06 1997 05:51 | 2 |
| The Alpha 3000-800 is a Turbo Channel machine. Does PCI interrupt
applies? If yes, how do I control the interrupts?
|
| 639.7 | | EEMELI::MOSER | Orienteers do it in the bush... | Fri Jun 06 1997 07:40 | 26 |
|
My guess is that it cannot find and load the MMOV$ICBM, which it needs
in order to config and load the needed drivers.
Can you post the output from $ MC SYSMAN IO AUTO/LOG/FULL and also
the SDA output from SDA> CLUE CONFIG?
/cmos
tuija> mc sysman io auto/log/ful
%SYSMAN-I-OUTPUT, command execution on node TUIJA
%IOGEN-I-PREFIX, searching for ICBM with prefix MMOV$
%IOGEN-I-ACTIVATE, activating ICBM MMOV$ICBM_0402
%IOGEN-I-ACTIVATE, activating ICBM MMOV$ICBM_04
%IOGEN-I-ACTIVATE, activating ICBM MMOV$ICBM
%IOGEN-E-ACTERR, error activating ICBM
-RMS-E-FNF, file not found
%IOGEN-W-NOICBM, failed to find ICBM with prefix MMOV$
%IOGEN-I-PREFIX, searching for ICBM with prefix SYS$
%IOGEN-I-ACTIVATE, activating ICBM SYS$ICBM_0402
%IOGEN-I-ACTIVATE, activating ICBM SYS$ICBM_04
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKA0
%IOGEN-I-SCSIPOLL, scanning for devices through SCSI port PKB0
|
| 639.8 | | UTRTSC::utojvdbu1.uto.dec.com::JurVanDerBurg | Change mode to Panic! | Fri Jun 06 1997 09:18 | 7 |
| > The Alpha 3000-800 is a Turbo Channel machine. Does PCI interrupt
> applies? If yes, how do I control the interrupts?
No, that does not apply then. Missed that one, sorry.
Jur.
|