| Title: | AlphaServer 4100 |
| Moderator: | MOVMON::DAVIS S |
| Created: | Tue Apr 16 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 648 |
| Total number of notes: | 3158 |
I've installed DU 3.2g to a Rawhide 1 CPU 512M mem. Installation worked fine, but when when the system came to multiuser the console display after appearing the Digital logo, have frozen. No mouse move nothing. Logging in from another another system i saw that /usr/lib/X11/xdm/xdm-errors file grows rapidly w/ message: BLT engine hung in s3TDrawColorImage GLOBALWAIT; resetting. The Comet search engine showed me a similar symptom. The advise was it's about some HW error. I replaced the PB2GA-JC adapter, w/o any success. I've read all related conferences, but none tells any workaround. Can anybody of you give me some advise? Thanx in advance --zoly [Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 592.1 | HARMNY::CUMMINS | Thu May 08 1997 12:16 | 24 | ||
What operating system was used on this machine previously? NT? UNIX
3.2F? If UNIX 3.2F, had it booted okay previously?
If NT, it's likely it has NT ECU data in ESC NVRAM, in which case UNIX
will appear to hang during boot (no ECU data for COMx ports). The SRM
console on 4100/4000 hardcodes ECU data and passes it to UNIX/VMS, if
no valid data is present in ESC NVRAM. Thus, one can successfully run
UNIX/VMS on a system with an empty ECU data NVRAM region, provided
there are no EISA options installed.
If you're unsure about which ECU data is in NVRAM, I'd recommend one of
the following two steps:
1. Run UNIX/VMS ECU and try UNIX boot again after a system init.
2. If no diskette handy, type "P00>>>dep eerom:c00 -n bff -b 0" to
clear the ECU data region. Then init the system and attempt to
boot UNIX. Note: console will issue a warning that the ECU data
region is invalid on the subsequent power-up/reset, but it will
hardcode the ECU data such that you can determine whether the ECU
data is your problem. Then, you can round up a UNIX/VMS diskette
and properly update the ECU data when you have the chance to do
so.
| |||||
| 592.2 | Nor UNIX nor NT | NNTPD::"[email protected]" | zoly | Thu May 08 1997 13:50 | 2 |
This machine came w/ FIS'd DU4.0b i suppose. Here none can tell me. [Posted by WWW Notes gateway] | |||||