- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Problems after upgrade from Tru64 4.0e to 5.1B
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 08:01 PM
тАО03-17-2004 08:01 PM
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?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 08:44 PM
тАО03-17-2004 08:44 PM
Re: Problems after upgrade from Tru64 4.0e to 5.1B
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.
_JB_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 09:12 PM
тАО03-17-2004 09:12 PM
Re: Problems after upgrade from Tru64 4.0e to 5.1B
# 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 09:21 PM
тАО03-17-2004 09:21 PM
Re: Problems after upgrade from Tru64 4.0e to 5.1B
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 09:30 PM
тАО03-17-2004 09:30 PM
Re: Problems after upgrade from Tru64 4.0e to 5.1B
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 09:37 PM
тАО03-17-2004 09:37 PM
Re: Problems after upgrade from Tru64 4.0e to 5.1B
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 09:49 PM
тАО03-17-2004 09:49 PM
Re: Problems after upgrade from Tru64 4.0e to 5.1B
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 10:00 PM
тАО03-17-2004 10:00 PM
SolutionOK, 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.
_JB_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 11:02 PM
тАО03-17-2004 11:02 PM
Re: Problems after upgrade from Tru64 4.0e to 5.1B
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-17-2004 11:50 PM
тАО03-17-2004 11:50 PM
Re: Problems after upgrade from Tru64 4.0e to 5.1B
go into console mode (>>>)
type
>>> runecu
or
>>> ecu