11-04-2008
adding memory to sun blade server ...
Hi, this is my 1st post here, I don't know is it proper or not for the question I have, but I may try ask anyway, since it is question about sun's hw/sw issue...
I have my blade 1000 installed additional memory kits, it was originally 2G memory installed on Group0(Bank 0/2) Dimm slots, I got some 2nd hand memory kits from eBay, and installed it, after reboot(touch /reconfigure, shutdown,then install memory modules), I use "prtconf -v" but something caught my eye, the " memory-controller, instance #1" is different as usual:
.....
memory-controller, instance #0
Driver properties:
name='logical-bank-ma-regs' type=int items=8 dev=none
value=80007e00.00030000.80007e00.00030100.80007e00.00030200.80007e00.00030300
Register Specifications:
Bus Type=0x400, Address=0x400000, Size=0x48
Device Minor Nodes:
dev=(158,0)
dev_path=/memory-controller@0,400000:mc-us3
spectype=chr type=minor
dev_link=/dev/mc/mc0
SUNW,UltraSPARC-III, instance #1
Driver properties:
name='pm-class' type=string items=1 dev=none
value='CPU'
name='pm-components' type=string items=4 dev=none
value='NAME=CPU Speed' + '1=1/32 of Normal' + '2=1/2 of Normal' + '3=Normal'
Register Specifications:
Bus Type=0x400, Address=0x800000, Size=0x10000
memory-controller, instance #1
Driver properties:
name='logical-bank-ma-regs' type=int items=8 dev=none
value=00000000.00000000.00000000.00000000.00000000.00000000.00000000.00000000
Register Specifications:
Bus Type=0x400, Address=0xc00000, Size=0x48
Device Minor Nodes:
dev=(158,1)
dev_path=/memory-controller@1,400000:mc-us3
spectype=chr type=minor
dev_link=/dev/mc/mc1
I'm wondering about why "memory-controller, instance #1" got all "0" value other then "memory-controller, instance #0"? it actually got total 4G memory now, but why the new installed 2G memory kits got all "0" value information? what does the "value=" mean in the section? anything I shall watch out especially?
my sun balde 1000 was installed solaris 10 8/07, with recommanded patch installed.
thanks.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I would like to upgrade the memory in my Sun Blade 150 workstation. In reading through Sun's Blade 150 DIMM Installation Guide, it indicates that the memory must be "certified by Sun for the Sun Blade 150 system."
Does anyone know if any SDRAM, PC133 • CL=2 • Unbuffered • ECC • 133MHz • 3.3V ... (2 Replies)
Discussion started by: here2learn
2 Replies
2. Solaris
hello,
I have SunBlade 2000 with XVR-1000 graphics card. Xserver won't loaded. I've reinstalled OS 9 ( loaded Driver) nor 10 still won't do it. Anyone has this problem or have any ideas whats' wrong, greatly appreciated!!
thanks in adv. (1 Reply)
Discussion started by: anphdula
1 Replies
3. Solaris
Hi, I've been a member for a while but have never posted. I have a Sun Blade 100 desktop and I just installed Solaris 10 and it is unbearably slow. I only have 128 Meg of RAM and need to upgrade. I have searched and found many online resources that have RAM, but I was wondering if anyone has... (12 Replies)
Discussion started by: BrewDudeBob
12 Replies
4. Hardware
Can you mix DIMMs in a T6320 (sparc) blade? I have read/heard that the DIMMs in a memory bay must be identical but can you have different size DIMMs installed in the blade?
For instance, can you have 1 4GB DIMM in bay 0, 2 2GB DIMMs in bay 1, 4 1 GB DIMMs in bay 2 and 2 2GB DIMMs in bay 3 for a... (0 Replies)
Discussion started by: bluescreen
0 Replies
5. Solaris
I need to add two new hard drives of 300 GB capacity to a SunSPARC T5440 server. The server currently has two hard drives of 146 GB each.
How do I add the new drives to the existing UFS?
What are the procedures involved in setting this server with the new hard drives? I am very new to Solaris... (6 Replies)
Discussion started by: ramatnmcc
6 Replies
6. Solaris
I have recently re-installed Solaris 10 on a Sun Blade 150 followed by a patch set (10_Recommended) dated 2011.12.05.
I have just noticed /bin/sun now returns false, rather than true. See below.
$ uname -a
SunOS myblade1 5.10 Generic_147440-07 sun4u sparc SUNW,Sun-Blade-100
$ /bin/sparc &&... (1 Reply)
Discussion started by: apmcd47
1 Replies
7. Solaris
We have a 6000 chassis with three blades in it. Two of the blades have "Oracle/Sun" memory in them with no complaints. The third blade is populated with Dataram dimms. That 3rd blade continues to flag a slot bad. Oracle has said they would not support the blade with Dataram memory it it. I didn't... (1 Reply)
Discussion started by: brownwrap
1 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I have server SUN BLADE T6340 and i tried install debian sparc on this machine.
Will it work ?
In the specification is written only Solaris 10. (4 Replies)
Discussion started by: PtaQ
4 Replies
9. Solaris
Hi all,
My home server was Solaris for quite a while- I started with an Ultra 2 about 20 years ago, ended with a Blade 2000- but I've transitioned to Linux and am not going back. I miss the Solaris experience a bit (but not the Oracle experience), besides running with modern and small and quiet... (0 Replies)
Discussion started by: gpounce32768
0 Replies
mptutil(1M) mptutil(1M)
NAME
mptutil - Diagnostic utility for Ultra320 SCSI controllers and A7173A PCI-X Dual channel Host Bus Adapters
SYNOPSIS
[options] <device_file>
DESCRIPTION
The command is a diagnostic tool to be used for Ultra320 SCSI controllers claimed by the MPT driver. This command provides the ability to
retrieve various configuration information, perform firmware downloads, issue Task Management commands and read accumulated statistics of
the controller and connected target devices.
The utility can be used with various options with a specified device file. Each device file represents only a single channel on the SCSI
controller. Therefore, commands issued through this utility are channel specific and do not affect the whole adapter (except firmware
download).
Prerequisites:
You must be a privileged user in order to run the command. See privileges(5) for more information on privileged users. In addition, some
of the options are intended for use by HP support personnel and require detailed knowledge of the Ultra320 SCSI driver or firmware to
interpret the output.
OPTIONS
recognizes the following options. All keywords are case-sensitive and are position dependent.
<device_file> where specifies the MPT device file associated with one channel of the Ultra320 SCSI controller.
The device files are created at boot time or during Online Addition of an adapter. They have the name /dev/mptX, where X is
the instance number of the SCSI channel, as reported by for the MPT driver and the
When used without any options it provides information such as the Driver and Firmware version, Vendor ID, Device ID, Adapter
NVRAM size, Vital Product Data (VPD) along with the driver's current state.
The following driver states are defined:
This state indicates that the hardware has not been initialized by the driver. This state could result if the driver was
unable to successfully initialize the channel.
This state indicates that the controller initialization is complete. Driver is in the process of retrieving/setting various
configuration parameters.
This state indicates that driver is online and ready to perform normal SCSI I/O operation.
This state indicates that driver is currently performing Task Management commands such SCSI BUS RESET, ABORT TASK, BUS
DEVICE RESET etc.
This state indicates that driver has detected a controller fault and is currently recovering from that condition.
This state indicates that controller has been suspended by the user.
This option is used to display the PCI Configuration data stored on the
card. Information is displayed as hexadecimal data.
This option is used to download the MPT SCSI firmware onto the SCSI controller
that has an associated Flash ROM. The controller is specified by the argument. WARNING: This is a DESTRUCTIVE operation.
Active I/Os will be aborted. Should be used by qualified personnel only.
This option is used to perform Task Management commands. The option
specifies the command type. Two types of Task Management commands are currently supported.
Perform a Bus Device Reset on the device specified by the
Perform a SCSI Bus Reset. This will reset all the devices on the SCSI bus.
WARNING: This is a DESTRUCTIVE operation. Active I/Os will be aborted. Should be used by qualified personnel only.
This option is used to upload the currently running firmware image to
file specified by the
Clear Driver and Device Statistics
Display Driver and Device Statistics
Dump the driver trace information onto the console.
Display Port Facts Information. The data is displayed as a series of
hexadecimal words.
EXAMPLES
These examples show an Ultra320 SCSI controller that is associated with a SCSI bus with instance number 5.
Display VPD and other general information stored on the controller
Download Firmware to the controller
Display driver and device statistics
Perform a device reset represented by connected to the controller
AUTHOR
was developed by HP.
FILES
Executable file.
Device files.
SEE ALSO
mptconfig(1M), ioscan(1M), scsictl(1M), privileges(5)
mptutil(1M)