Sponsored Content
Operating Systems Solaris Solaris sun4v - how do you determine physical RAM? Post 302429945 by achenle on Wednesday 16th of June 2010 07:50:12 AM
Old 06-16-2010
The 'lgrpinfo' utility might do it. I don't recall offhand when that was rolled into Solaris 10 so you may not have it, and it may not work under LDOMs, but it's designed to show physical RAM configuration.
 

10 More Discussions You Might Find Interesting

1. Solaris

getting available physical RAM

What command should I be using on Solaris 9 to get an accurate representation of the available physical RAM? (4 Replies)
Discussion started by: dangral
4 Replies

2. HP-UX

determine the physical size of the hard disk

Hi is there a cmd in hpux 11 to determine the physical size of the hard disk. not bdf command. i have searched the other threads here but cant find an answer. thank you guys (4 Replies)
Discussion started by: hoffies
4 Replies

3. Solaris

RAM Physical Memory usage by each Process.

Hi All, I am trying to find the physical memory usage by each process/users. Can you please let me know how to get the memory usage?. Thanks, bsraj. (12 Replies)
Discussion started by: bsrajirs
12 Replies

4. UNIX for Dummies Questions & Answers

How to accurately determine memory (RAM) information

I'm writing a shell script to display as much useful information on physical and virtual memory availability and usage as possible. I need a CLI tool to print these numbers for me. The utilities that I know to give out some statistics are the following: free top vmstat sysctl In Linux... (1 Reply)
Discussion started by: fiori_musicali
1 Replies

5. Red Hat

red hat Linux 5.0 is detecting 3gb ram but physical ram is 16gb

Hi, On server 64bit Hw Arch , Linux 5.0(32bit) is installed it is showing only 3gb of ram though physical is 16gb can u give me idea why? (4 Replies)
Discussion started by: manoj.solaris
4 Replies

6. AIX

How to determine the physical volume fo the disks

This is the report I got running the comand rptconf, but I would like to know what is the capacity of the disks installed into our server power 6 with AIX System Model: IBM,7778-23X Machine Serial Number: 1066D5A Processor Type: PowerPC_POWER6 Processor Implementation Mode: POWER 6... (6 Replies)
Discussion started by: cucosss
6 Replies

7. Red Hat

Physical RAM

Hi, I have a server (BL460c) with 32G of physical RAM. It currently only uses approx 5% its capacity but will use more (not sure how much more) pending the launch of further applications. If I need to build another node of similar functionality should I consider downgrading the physical... (2 Replies)
Discussion started by: Duffs22
2 Replies

8. Solaris

ZFS : Can arc size value exceed Physical RAM ?

Hi, kstat -p -m zfs -n arcstats -s size returns zfs:0:arcstats:size 8177310584 this values is approx (7.61 GB) but my Physical Memory size is only 6144 Megabytes. Can this happen ? if yes, then how can I find free memory on the system. BTW, I ran the kstat commands from a Non... (2 Replies)
Discussion started by: sapre_amit
2 Replies

9. Solaris

T5220 How to determine physical memory installed?

Hi, looking to upgrade memory on a pair of T5220's from 32GB to 64GB. Cannot determine current DIMM size and slots used. i.e. not sure if Qty 16 x 2GB or Qty 8 x 4GB. If there are no empty slots, i need to go with higher density DIMMs and retire exsisting the 2GB prtdiag follows. #... (3 Replies)
Discussion started by: edrew
3 Replies

10. Solaris

Solaris 10 virtual disk (ramdisk) create for sun4v (T-2000 simulator) architecture

have been trying to create a 2 GB ramdisk (virtual) to run on my T-2000 simulator (Legion) which has sun4v architecture. I have a SPARC workstation which runs on sun4u architecture with Solaris 10. I have created a ramdisk image using dd command, newfs, then used ufsrestore to restore the... (3 Replies)
Discussion started by: Zam_1234
3 Replies
pcram(7D)																 pcram(7D)

NAME
pcram - PCMCIA RAM memory card device driver SYNOPSIS
memory@<socket>/pcram@<technology>,0:c memory@<socket>/pcram@<technology>,0:c,raw The PCMCIA RAM memory card device driver supports disk-like I/O access to any standard PCMCIA static random access memory (SRAM) card and dynamic random access memory (DRAM) card. The driver supports standard PCMCIA SRAM/DRAM cards that contain a Card Information Structure (CIS). RAM card densities in the 512Kilobytes to 64Mbyte range are supported. PRECONFIGURATION
If a PC card memory device is recognized, the pcram device driver is automatically loaded, the physical address allocated, and special files created (if they do not already exist). Known Problems and Limitations The Solaris pcmem driver is not capable of handling "combo" memory cards with multiple types of memory on them (for example, combined SRAM and nonvolatile FLASH). Inserting such a card into a system running the Solaris software may cause a system panic. Because the PC card memory device is designed as a pseudo-floppy diskette type, the only utility that can be used for formatting is fdfor- mat(1). CONFIGURATION
Configuration topics include initial installation and configuration, identifying an unrecognized device, special files, using PC card mem- ory devices, and hot-plugging. Initial Installation and Configuration 1. Install the Solaris software. 2. Boot the system. 3. Insert the card. Identifying an Unrecognized Device If you insert a memory device and it is not recognized (no special files created), use the prtconf command. 1. Become root. 2. Run the prtconf -D command to display the configuration recognized by the system. A recognized device will appear in the prtconf out- put. For example: # prtconf -D . . . pcic, instance #0 (driver name: pcic) . . . memory, instance #0 (driver name: pcmem) pcram, instance #0 (driver name: pcram) 3. If your memory device does not appear at the end of the prtconf output, it is not supported and cannot be used with the pcram driver. Special Files The special files created for PC card memory devices act like disks and have names in the form /dev/dsk/c#t#d#p# or /dev/dsk/c#t#d#s#. Abbreviations used in the names are: o c# Controller # o t# Card technology type #, defined as follows: 0 Null--no device 1 ROM 2 OTPROM (One Time PROM) 3 UV EPROM 4 EEPROM 5 Flash EPROM 6 SRAM 7 DRAM o d# Device region of type #, usually zero o p# fdisk partition # o s# Solaris slice # Note - A device name can be specified either by a partition name (p#) or a slice name (s#), but not both. Using PC Card Memory Devices Since the Solaris Volume Management software recognizes PC Card memory devices, no special vold configuration is required. If you do not want to use vold to manage your PC card memory devices, comment out the use pcmem line in the /etc/vold.conf file. To comment out a line, insert a # character at the beginning of the line. PC Card memory devices do not need to have file systems on them, though typically, before using a new PC Card memory card, you will want to create a file system on it. DOS PCFS is the best format to use. (You can use virtually any file system format on a PC card memory card, but most other file system formats are platform-dependent, making them unsuitable for moving data between different types of machines. See "Using a PCMCIA Memory Card" in the OpenWindows Advanced User's Guide.) Note - If you want to redirect the output of a tar command (or dd or cpio) to a PC card memory device, first create a file system on the card, using the fdformat(1) command without arguments. The card must be reformatted before it can be written on again. Hot-Plugging If a memory card is removed while in use, the device driver returns errors until the memory card is inserted into the appropriate socket. Close and reopen the device with the card reinserted, and the memory card will work. o If you remove the card while in use as a file system, unmount the file system using the umount command. Then reinsert the card and remount the file system using the mount command. o If you remove the card and interrupt a tar or cpio process, stop the process, reinsert the card, and restart the process. /kernel/drv/pcram pcram driver /dev/dsk/cntndnsn block files /dev/rdsk/cntndnsn raw fileswhere: cn controller n tn technology type n 0x1ROM,0x2OTPROM,0x3EPROM, 0x4EEPROM,0x5FLASH,0x6SRAM, 0x7DRAM dn technology region in type n sn slice n fdformat(1), pcmcia(7D), dkio(7I), pcmem(7D) 23 Oct 2000 pcram(7D)
All times are GMT -4. The time now is 09:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy