05-09-2013
You have 8 x 4GB DIMMs.
Edit: I was confused by the 4GB and missed that was for a pair of modules
Last edited by jlliagre; 05-13-2013 at 05:43 PM..
10 More Discussions You Might Find Interesting
1. HP-UX
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
2. Solaris
what is the command to find the physical memory in soalris OS and how to find whether paging is happening or not ? (2 Replies)
Discussion started by: jayaramanit
2 Replies
3. Solaris
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies
4. Solaris
Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies
5. Solaris
I have a Sun T5120, and I want to programmatically determine how much RAM it has.
# uname -a
SunOS myhost 5.10 Generic_141444-09 sun4v sparc SUNW,SPARC-Enterprise-T5120
The box has 64Gb; I tried prtdiag and prtconf, but they give me bogus info
prtconf gives me:
# prtconf |grep -i... (12 Replies)
Discussion started by: thomn8r
12 Replies
6. AIX
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. Solaris
How to determine, whether Sun WorkShop is installed on Solaris worksation?
And if It's installed, how to start one? (2 Replies)
Discussion started by: wolfgang
2 Replies
8. Shell Programming and Scripting
I currently have a shell script that utilizes the "Date" binary - this application is slightly different on OS X (BSD General Commmand) and Linux systems (gnu date). In particular, the version on OS X requires the following to get a date 14 days in the future "date -v+14d -u +%Y-%m-%d" where gnu... (1 Reply)
Discussion started by: colinjohnson
1 Replies
9. Solaris
I would like to know how to identify the installed "Physical Processor" .here is the output #psrinfo -pv of from 2 systems :
- System 1
The physical processor has 8 virtual processors (0-7)
SPARC-T4 (chipid 0, clock 2848 MHz)
-System 2
The physical processor has 8 virtual... (3 Replies)
Discussion started by: ahmedamer12
3 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
.
I am trying to find whether Solaris 11 installed on physical server or on VMware/KVM.
I tried uname -a but it's giving only whether i installed on X86 or sparc machine.
I tried prtdiag command but it's giving below information.
command : prtdiag -v |grep "System... (2 Replies)
Discussion started by: sravani25
2 Replies
mem(7D) Devices mem(7D)
NAME
mem, kmem, allkmem - physical or virtual memory access
SYNOPSIS
/dev/mem
/dev/kmem
/dev/allkmem
DESCRIPTION
The file /dev/mem is a special file that provides access to the physical memory of the computer.
The file /dev/kmem is a special file that provides access to the virtual address space of the operating system kernel, excluding memory
that is associated with an I/O device.
The file /dev/allkmem is a special file that provides access to the virtual address space of the operating system kernel, including memory
that is associated with an I/O device. You can use any of these devices to examine and modify the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. Byte addresses in /dev/kmem and /dev/allkmem are interpreted as
kernel virtual memory addresses. A reference to a non-existent location returns an error. See ERRORS for more information.
The file /dev/mem accesses physical memory; the size of the file is equal to the amount of physical memory in the computer. This size may
be larger than 4GB on a system running the 32-bit operating environment. In this case, you can access memory beyond 4GB using a series of
read(2) and write(2) calls, a pread64() or pwrite64() call, or a combination of llseek(2) and read(2) or write(2).
ERRORS
EFAULT Occurs when trying to write(2) a read-only location (allkmem), read(2) a write-only location (allkmem), or read(2) or
write(2) a non-existent or unimplemented location (mem, kmem, allkmem).
EIO Occurs when trying to read(2) or write(2) a memory location that is associated with an I/O device using the /dev/kmem spe-
cial file.
ENXIO Results from attempting to mmap(2) a non-existent physical (mem) or virtual (kmem, allkmem) memory address.
FILES
/dev/mem Provides access to the computer's physical memory.
/dev/kmem Provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an
I/O device.
/dev/allkmem Provides access to the virtual address space of the operating system kernel, including memory that is associated with an
I/O device.
SEE ALSO
llseek(2), mmap(2), read(2), write(2)
WARNINGS
Using these devices to modify (that is, write to) the address space of a live running operating system or to modify the state of a
hardware device is extremely dangerous and may result in a system panic if kernel data structures are damaged or if device state is
changed.
SunOS 5.10 18 Feb 2002 mem(7D)