Sponsored Content
Full Discussion: /dev/mem on Dell Poweredge
Top Forums Programming /dev/mem on Dell Poweredge Post 302165550 by ragisreekanth on Friday 8th of February 2008 06:46:24 AM
Old 02-08-2008
Question /dev/mem on Dell Poweredge

Hi,

I have a C++ program to access /dev/mem and retrieve details like Vendor, Manufacturer details of the motherboard. This works fine on all the machines except for on Dell Poweredge 2850,1950... machines.
I receive a 'EFAULT' when I try to access /dev/mem on these servers.
I suspect some change to the addressing structure. Could someone give me any ideas/pointers in this regard.

TIA
Sreekanth
 

8 More Discussions You Might Find Interesting

1. Linux Benchmarks

Dell Dual Xeon PowerEdge 4600

Notes: System Configuration: Dell Computer Corporation PowerEdge 4600 (4 X Intel(R) XEON(TM) CPU 2.00GHz 1988.782 MHz) hyperthreaded System clock frequency: 99.0827 MHz Memory size (approximate): 2559 Megabytes ========================= CPUs ======================== CPU # CPU... (0 Replies)
Discussion started by: tnorth
0 Replies

2. Linux Benchmarks

Dell Poweredge 2400 / 533

CPU/Speed: Dual PIII 533 Ram: 256Mb PC133 Motherboard: Unknown, Intel Chipset Cache: 256k on board Controller: PARC Raid 2/Si, AIC-7880U Disk: 30Gb RAID 5 Load: 1 user. Clean boot, init 5 but X-Windows not loaded. Kernel: See Benchmarks. pgms: gcc 3.2.3 ... (2 Replies)
Discussion started by: Garp
2 Replies

3. Solaris

Installing Solaris 10 on Dell PowerEdge 2800

hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request... the installation crashes when trying to detect the NICS... (0 Replies)
Discussion started by: xinugeek
0 Replies

4. Red Hat

Installing RedHat 8.0 onto Dell PowerEdge SC1425 - hdc: status error: status = 0x58

I have successfully installed RedHat 8.0 onto a Dell PowerEdge SC1425 today. This server has two SATA hard drives, and an IDE DVD-ROM drive. Using the following kernel parameters, i successfully installed across both hard drives from CD: ide0=0x1f0,0x3f6,14 vga=791 resolution=1024x768 expert... (5 Replies)
Discussion started by: fishsponge
5 Replies

5. Filesystems, Disks and Memory

Linux and Dell 1500sc Poweredge Server

Does anybody no how to get around the fact that the Red Hat installation does not see the SCSI hard drives. It lets you manually pick the proper device, but still fails saying no drive detected (or something to that effect). I was going to install windows 2003 Server and use VMware...but again,... (1 Reply)
Discussion started by: Fatflea
1 Replies

6. UNIX for Dummies Questions & Answers

Stange problem Dell PowerEdge 1950/ Boradcom Netextreme NIC

I have 2 Dell Poweredge 1950 servers running . I have been having intermittent performance issues with the NIC cards on one of them. The two servers are identical and are running the same operating system. The server that has the issue is on the DMZ on a a static IP and is hosting a website. ... (0 Replies)
Discussion started by: skotapal
0 Replies

7. SCO

Continueing relyability problems with SCO 6.0 on Dell Poweredge 1800 with PERC DC4.

Hello all, I'am experiencing weird relyability problems with a SCO 6.0 Openserver server that runs on a Dell Poweredge 1800 equipped with a PERC DC4 raid controller and 4 36 GB 15 K rpm hot swappable scsi harddisks. It runs a RAID 10 configuration. It uses the mega hba, Revision 8.03a Release... (1 Reply)
Discussion started by: frederik1
1 Replies

8. SCO

Dell PowerEdge 2600 tape backup

I was asked to get a Dell PowerEdge 2600 server, out of warranty, running SCO 3.2v5.06 to perform a full backup. I spent hours researching and preparing a strategy only to fail on-site. The only device names in /dev for a tape drive were /dev/xStp0 /dev/xcdt0 /dev/xct0 ... (6 Replies)
Discussion started by: ezlarry
6 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)
All times are GMT -4. The time now is 02:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy