Problems after upgrade from Tru64 4.0e to 5.1B

[bill johnston_3]

We upgraded our alpha ds20 through all versions and have developed the following problems as a result;

the console keyboard and mouse have stopped responding to input once the the screen message "jumping to bootstrap" appears, although there is no problem at console prompt and firmware is successfully upgraded to 6.3.

More importantly we have an application that has always been able to fax out through the modem on tty01 but now cannot run and displays the message "cannot get UUCP lock for port /dev/tty01".

sysman shows a modem on tty01 and enabled.

HELP!

Sorry if you've seen this post somewhere else, as I submitted it once already but lost it?

[Johan Brusche]

Your other post was in the wrong forum "Digital Imaging". (Click on your name in the post, and you will see both entries in your profile ;-))

Can you tell us the outcome of the commands:

consvar -g console
sizer -v
sizer -gt
sizer -wk
sizer -wp


Johan.

[bill johnston_3]

Here are the results of the commands that you asked me to run, ignore the first as we are having to run a serial console in order to use the server at all.

# consvar -g console
console = serial
# sizer -v
Compaq Tru64 UNIX V5.1B (Rev. 2650); Mon Mar 15 13:16:56 GMT 2004
# sizer -gt
ZLXp2-EV5
# sizer -wk
PCXAL
# sizer -wp
PCXAS

hope this helps, and thanks for your quick response.

[Michael Schulte zur Sur]

Hi Bil,

the console variable is set to serial.
You must set it back to graphics.
shutdown machine and at the console prompt type
set console graphics

This should solve your mouse/keyboard problem.

greetings,

Michael

[bill johnston_3]

Hi Michael,

As I wrote in the last post we have set the console variable to serial in order to get access to the machine and use it.

The loss of the keyboard and mouse happened prior to that setting when the console variable was still set to graphics.

we have tried moving the variable away and back and rebooting with no success.

cheers

[Michael Schulte zur Sur]

Oops,

missed that. :-(

what kind of graphics card do you have. May be it is not supported anymore or has to be configured with the eisa configuration utility?

Can you post show config from the console as attachment?

greetings,

Michael

[bill johnston_3]

sorry haven't got a sho config I can post, and my finance director is already miffed so a reboot is unlikely just to get one.

however I can tell you that the graphics card is a PBXGB-AA (PCI)

incidently, we have graphics, just no keyboard and mouse (both PS2)

server is a Digital Alpha DS20 model no DH-55NJA-AA with no modifications.

cheers

[Johan Brusche · Accepted solution]

OK, to get the mouse and kb back you will have to run the "ecu" aka Eisa Configuration Utility in console mode. Just a 'save' and 'exit' from this utility will be enough.
This is usually required for EISA hardware anytime a firmaware update is performed.

The kb and mouse are behind an EISA bridge ASIC on the DS20 motherboard.

Unfortunately a shutdown is required to get at the SRM.

Johan.

[bill johnston_3]

thanks for that, it may help with the com port as well then?

just one thing...

how do i run the ECU, I have a disk that came with the system 5 years ago labelled ecu diskette V1.11A, but have never used it to my recollection, and it is not bootable.

?????

cheers.

[Ralf Puchner]

bill,

go into console mode (>>>)
type

>>> runecu

or

>>> ecu