- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: vmunix:
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
тАО07-25-2004 09:55 PM
тАО07-25-2004 09:55 PM
vmunix:
vmunix: prom_getenv:Invalid ev type:0
vmunix: prom_getenv:Invalid ev type:0
Has anyone seen this before? Can you shed any light?
TIA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2004 10:50 PM
тАО07-25-2004 10:50 PM
Re: vmunix:
It tells you that a console variable is set to an invalid value.
Check /usr/include/machine/prom.h for the names of the console variables that the prom_getenv() function migth be trying to obtain.
The simple execution of command "consvar -l", could trigger this event to appear in /var/adm/messages.
If you get this message by executing
"consvar -g language", you know immediately that the console variable "language" is set to an invalid value.
rgds,
__Johan__
_JB_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2004 11:23 PM
тАО07-25-2004 11:23 PM
Re: vmunix:
But without giving any technical informations i can only guess it is v5.x
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2004 12:15 AM
тАО07-26-2004 12:15 AM
Re: vmunix:
The system at question is a GS60 6/525 DEC21000 with 4xEV6 cpus and 8Gb ram running v4.0f.
It would appear that issuing consvar -g sys_serial_num is triggering this message. Why would this value be set incorrectly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2004 01:09 AM
тАО07-27-2004 01:09 AM
Re: vmunix:
I get the same error whenever I issue this same command. I have recently had service performed on my machine that involved a new main board, and my cpu serial number does not match my system serial number. In addition, my firmware was installed for T64 V5.1B, but I am running V4.0F. Have you recently had service performed or did your machine originally come with a higher version ?
This may have been an issue all along with my DS10 AlphaServer, but I noticed it after looking at the serial number when the main board was changed.
I suspect that this is an issue with the firmware, as I do not get the error when I issue the #consvar -nc -g sys_serial_num. This command does not convert between the hex values and strings. If you issue the command #consvar -v -g sys_serial_number, you will see all of the detail in the conversion, and you will get the error. I can recreate the error using several of the consvar commands, and I suspect it is due to the SRM firmware (6.4-9) being much more advanced than the OS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2004 01:22 AM
тАО07-27-2004 01:22 AM