1829107 Members
2343 Online
109986 Solutions
New Discussion

PA-RISC Identification

 
SOLVED
Go to solution
ConnieK
Regular Advisor

PA-RISC Identification

Is there an easy way to "query" an HP-UX server to identify what level the PA-RISC
processors are (32 bit vs 64 bit)?

Thanks!
Independent by nature
15 REPLIES 15
Stefan Farrelly
Honored Contributor

Re: PA-RISC Identification


look in /usr/sam/lib/mo/sched.models
for the model of your HP server (uname) and it shows you the PA-RISC version of your CPU.
Im from Palmerston North, New Zealand, but somehow ended up in London...
ConnieK
Regular Advisor

Re: PA-RISC Identification

I have found that info - thanks. But knowing what level it is, how can I
determine which it supports 32 bit or 64 bit?
Independent by nature
Andy Monks
Honored Contributor

Re: PA-RISC Identification

Also, you can do 'getconf KERNEL_BITS' to see if your currently running 32/64bit and 'getconf HW_32_64_CAPABLE' to see if your machine can run 32/64 bit.
Rick Garland
Honored Contributor

Re: PA-RISC Identification

Can do 'file /stand/vmunix'
Rick Garland
Honored Contributor

Re: PA-RISC Identification

file/stand/vmunix

If it says 64, OK. If it doesn't say 64, must be 32.
Cheryl Griffin
Honored Contributor

Re: PA-RISC Identification

To check hw capability:
# getconf HW_CPU_SUPP_BITS
"Downtime is a Crime."
Stefan Farrelly
Honored Contributor

Re: PA-RISC Identification


getconf KERNEL_BITS may lie to you if you dont have the correct level of PDC firmware on your system so watch out for that.
Any PA-RISC CPU at version 2.0 and above is 64bit capable.
Im from Palmerston North, New Zealand, but somehow ended up in London...
Andy Monks
Honored Contributor

Re: PA-RISC Identification

Forgot to mention, from HW_32_64_CAPABLE, the responses are :-

1 - 64 bit only
2 - 32 bit only
3 - either 32 or 64 bit
Cheryl Griffin
Honored Contributor

Re: PA-RISC Identification

Check /etc/.supported_bits for 32/64 bit os and hardware compatibility.

# cat /etc/.support_bits
"Downtime is a Crime."
ConnieK
Regular Advisor

Re: PA-RISC Identification

To all that replied, thanks! Here's the outcome/resolution:
Andy & Cheryl: none of the recommended arguments worked with "getconf" - old version, I presume.
Cheryl: /etc/.support_bits <---- not found
Rick: file /stand/vmunix <---- returned "S800 executable -not stripped"
Stefan: I found the RISC model/version in /usr/sam/lib/mo/sched.models to be 1.1b and PA7100. Another administrator here had information stating that the 64-bit version runs only on the 64-bit PA-RISC 8x00 processors.
So, based on what I've gleaned from all of you, this particular HP 9000 T520 can only support 32 bit version of HP-UX 11.0.
Thanks again!



Independent by nature
Stefan Farrelly
Honored Contributor

Re: PA-RISC Identification


Glad you got it sorted. Dont forget to assign points.
Im from Palmerston North, New Zealand, but somehow ended up in London...
Cheryl Griffin
Honored Contributor

Re: PA-RISC Identification

Constance,

>>/etc/.support_bits <---- not found >>
You can look at this on another machine or,

The file is small, so I attached it here in text format. It is available through patch PHCO_20894

hp-ux_patches/s700_800/11.X/PHCO_20894 :64-bit:hardware:enablement:supported_bits:
"Downtime is a Crime."
Cheryl Griffin
Honored Contributor

Re: PA-RISC Identification

Be sure to check this link too:
http://docs.hp.com/dynaweb/hpux11/hpuxen1a/b1396/@Generic__BookView

Has a lot of compatibility information here for 11.00 32 vs 64 bit.

To get there manually (in case the link does not work):
HP-UX 11.0 Release Documentation (under By Release)
HP-UX 11.0 Operating System
Release Notes for 11.0 Extension pack, 12/98
System Configuration Summary
"Downtime is a Crime."
Jim Shroyer_1
Occasional Advisor
Solution

Re: PA-RISC Identification

This will depend on what version of Diagnostics you have loaded but should work for the most part:

/usr/sbin/diag/contrib/pdcinfo -no_banner | grep 'PA [0-9]' | uniq | cut -b9-16
Jim Shroyer_1
Occasional Advisor

Re: PA-RISC Identification

Should have read that more carefully. The last post will just return the type as opposed to 32- or 64-bit.