[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference wrksys::alphastation

Title:Alpha Workstation Conference
Notice:See note 1.* for conference notices
Moderator:WRKSYS::HOUSE
Created:Wed Sep 07 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1996
Total number of notes:9122

1844.0. "AlphaStation 255/233 with dual head PBXGB-AA" by COMICS::CORNEJ (What's an Architect?) Thu Feb 06 1997 10:38

    I have a customer with several dozen AlphaStation 255/233s with dual
    PBXGB-AAs in them.
    
    They came with UNIX V3.2d FIS'd and both heads worked.  Installing
    V3.2g from the CD prevents the second screen working.  The symptoms are
    that the first screen comes up fine, but the second screen only goes
    white.  The mouse DOES track across between screens,  but any keyclick
    on the second screen will cause the system to hang.  So hung, infact,
    that the reset button in the front does not work.
    
    Looking in /usr/var/X11/xdm/xdm-errors I see a major difference:-
    
    	V3.2d...
    
    Screen 0 ZLXp2-EV4 Revision #2 8 bits/pixel 2097152 bytes
    Screen 1 ZLXp2-EV4 Revision #2 8 bits/pixel 2097152 bytes
    
    	V3.2g...
    
    Screen 0 ZLXp2-EV4 Revision #2 8 bits/pixel 2097152 bytes
    Server scanline padding disagrees with ROM, adjusting
    Screen 1 ZLXp2-EV4 Revision #0 8 bits/pixel 16777216 bytes
                                 ^                 ^
                                 ------These are different
    
    This is on the same hardware box. Firmware is from the V3.6 CD
    
    Open3D was NOT installed on the 3.2g system because the support appears
    to be there already.  Is it still required for dual headed?
    
    Jc
     
T.RTitleUserPersonal
Name
DateLines
1844.1DECWIN::MCCARTNEYThu Feb 06 1997 10:548
The support is in Digital UNIX, but the newer code can always be found in
the Open3D kit.  I'd have them install Open3D and see if the problem goes
away. 

Also, are they running XDM and CDE window manager?  CDE does not support a 
second screen.

Irene
1844.2taCOMICS::CORNEJWhat's an Architect?Thu Feb 06 1997 11:247
    Thanks Irene,
    
    They are not running CDE.  I'll try the Open3D kit to see if it helps
    (is it really later than 3.2g?).
    
    Jc
    
1844.3DECWIN::MCCARTNEYThu Feb 06 1997 11:386
While Open3D may have shipped prior to 3.2g, no new code for that DDX has been
checked in for a VERY long time (> 1 year!).  I know Open3D has fixed quite
a few bugs in that time.  All the base OS has is a shadow copy of the DDX
code.  Open3D has the master copy and thus a set of newer fixes.

Irene
1844.4COMICS::CORNEJWhat's an Architect?Thu Feb 06 1997 13:565
    We just tried Open3D - it made no difference - same symptoms.
    
    Jc
    
    
1844.5COMICS::CORNEJWhat's an Architect?Fri Feb 07 1997 05:054
    Does anyone have a 255/233 who can try this with V3.2g?
    
    Jc
    
1844.6Confused Install ??NETRIX::"[email protected]"John McNultyMon Feb 10 1997 10:0739
I have an update to this call.  The customer has now installed Open3D and
after rebuilding the kernel (which he'd forgotten to do) and rebooting it
now works.  Here's the wierd bit though.   After a fresh install, the 
message written to xdm-errors (as John said in his base note) is:

    Screen 0 ZLXp2-EV4 Revision #2 8 bits/pixel 2097152 bytes
    Server scanline padding disagrees with ROM, adjusting
    Screen 1 ZLXp2-EV4 Revision #0 8 bits/pixel 16777216 bytes
                                 ^                 ^
                                 ------These are different

But after installing Open3D and rebuilding the kernel, etc, the message
changes to:

    Screen 0 ZLXp2-EV4 Revision #2 8 bits/pixel 2097152 bytes
    Screen 1 ZLXp2-EV4 Revision #2 8 bits/pixel 2097152 bytes
    
As it should be.   It looks to me like something is wrong in the installation
or implementation for the ZLXp2-EV4 in the base V3.2g product.  Even though
it says screen 1 is a ZLXp2-EV4 it displays the memory size of a ZLXp2-EV5
(PBXGB-CA).  And Open3D is required to overwrite the duff code and put it
right.  

Just to make sure, I got him to check the jumper settings on both cards.
Screen 0 has VGA enabled and screen 1 disabled, which is correct.  And
both cards have the "Alias" jumpers open (disabled) which is also correct
(the ZLXp2-EV5 is the opposite - Alias jumpers are close [enabled]).

So this is definately a bug in the V3.2g base product.  Time for an
IPMT?

John
------------------------------------------------------------------------------

Email: [email protected]                            John McNulty
Tel: (44) 1256 373862                            UK CSC, Unix Support Group
DTN: 833-3862                                    Digital Equipment Corporation

[Posted by WWW Notes gateway]
1844.7COMICS::CORNEJWhat's an Architect?Thu May 08 1997 13:1714
    3 months later...
    
    The customer has started to compare the performance with and without
    the Open3D kit installed (they only loaded the drvers).  They claim
    (and I have no reason to disbelieve them right now) that the graphics
    were faster without Open3D installed.  They make no explicit use of 
    Open3D as such.   
    
    Is this likely to be true?
    
    Do the driver bugfixes make it into the base OS in DU V4.0(anything)?
    
    Jc