Sun Blade T6320 memory configuration

 
Thread Tools Search this Thread
Special Forums Hardware Sun Blade T6320 memory configuration
# 1  
Old 07-08-2010
Sun Blade T6320 memory configuration

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 total of 16GB of RAM?

Thanks!
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Free Sun Blade 2k, Ultra 2, Ross Hyperstation 30, cards, memory- Baltimore, MD

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

2. UNIX for Dummies Questions & Answers

SUN BLADE T6340 - which OS ?

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

3. Solaris

Memory problems in Blade 6340

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

4. Solaris

Hardware RAID not recognize the new disk [Sun T6320]

We have hardware RAID configured on Sun-Blade-T6320 and one of the disk got failed. Hence we replaced the failed disk. But the hot swapped disk not recognized by RAID. Kindly help on fixing this issue. We have 2 LDOM configured on this server and this server running on single disk. #... (8 Replies)
Discussion started by: rock123
8 Replies

5. Solaris

Sun Blade 150 not a Sun?

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

6. Solaris

how to get cpu and memory configuration on sun

Hi folks, can you please help to print cpu and memory configuration on sun host. (4 Replies)
Discussion started by: ggolub
4 Replies

7. Solaris

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... (5 Replies)
Discussion started by: netshu
5 Replies

8. Solaris

Sun Blade 100 Memory Upgrade

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

9. Solaris

sun Blade 2000 and XVR100

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

10. UNIX for Dummies Questions & Answers

Memory upgrade Sun Blade 150

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
Login or Register to Ask a Question
ODINRECO(1)							   User Commands						       ODINRECO(1)

NAME
odinreco - Automatic reconstruction for ODIN sequences SYNOPSIS
odinreco [ options ] -r <input-file-to-be-read> DESCRIPTION
odinreco: Automatic reconstruction for ODIN sequences odinreco provides a generic reconstruction for imaging sequences (spin-warp, EPI, RARE, ...). It retrieves the information about the acquired signal from the file 'recoInfo' which is stored on disk together with the raw data. The recoInfo file contains information about the k-space position of each acquisition windows (ADC). As output, odinreco generates a bunch of files with different image formats (depending on the option -f and third-party libraries available to ODIN). The filename of each file starts with the given output prefix. OPTIONS
-bcw: Correlation weighting of all blades against the mean of all blades (in image space) -bf: Filter function for blade phase correction (options=Gauss NoFilter Triangle Hann Hamming CosSq Blackman BlackmanNuttall Exp , default=NoFilter) -bfw: Width of the filter function used for blade phase correction.[0.0 (0%) ... 1.0 (100%) of blade width; -1.0 (100%) ... 0.0 (0%) of center width] (default=1.0) -bkf: Blade-keyhole filter function (and its arguments) (options=Gauss NoFilter Triangle Hann Hamming CosSq Blackman BlackmanNuttall Exp , default=CosSq) -bkt: Blade-keyhole transition width (fraction of oversampled k-space center) (default=0.20) -bwf: Window/Filter function for kspace weighting of each blade (options=Gauss NoFilter Triangle Hann Hamming CosSq Blackman BlackmanNut- tall Exp , default=Triangle) -bww: Window/Filter width for kspace weighting of each blade (default=1.0) -cp: Use direct Fourier transform with conjugate-phase correction instead of gridding -dcr: Load field drift from this file -dcw: Calculate and store field drift to file with this prefix -df: Output format (file extension) of dump files (default=nii) -dg: Disable GRAPPA interpolation -dh: Disable homodyne reconstruction -dm: Disable fieldmap-based multi-frequency reconstruction -dp: Prefix of dump files (default=./dump) -ds: Disable slice-time correction -el: Level relative to mean value of first echo for setting mask of exponential decay fit (default=0.50) -f: Space sepapared list of output formats (file extensions), possible formats are '3db asc coi dat dcm double float gz hdr idx ima jdx mag mhd nii ph png pos pro reg s16bit s32bit s8bit smp u16bit u32bit u8bit vtk ' (default=nii) -ff: k-space filter function (and its arguments) (options=Gauss NoFilter Triangle Hann Hamming CosSq Blackman BlackmanNuttall Exp , default=NoFilter) -fm: Load fieldmap data from this file -fp: Filter plateau width (0=no plateau, 1=full plateau) (default=0.0) -gd: Fraction of k-psace points to discard in auto-calibration lines because of high residuals (default=0.010) -gp: Number of neigbouring measured k-space lines used for GRAPPA interpolation (default=2) -gr: Number of neigbours in read direction used for GRAPPA interpolation (default=5) -gs: Scale Factor for the grid used for gridding (default=1.0) -ip: Command line args for extra processing of final images (default=none) -j: Number of concurrent jobs(threads) in reco (default=4) -kg1d: Kernel function for 1d k-space gridding (options=Gauss NoFilter Triangle Hann Hamming CosSq Blackman BlackmanNuttall Exp , default=Gauss(0.36169)) -kg2d: Kernel function for 2d k-space gridding (options=Gauss NoFilter Triangle Hann Hamming CosSq Blackman BlackmanNuttall Exp , default=Gauss(0.36169)) -kh: Keyhole reconstruction, e.g. for PROPELLER -ks: Store k-space data -kw1d: Kernel width for 1d k-space gridding [Pixel] (default=4.24264Pixel) -kw2d: Kernel width for 2d k-space gridding [Pixel] (default=3.0Pixel) -mf: Maximum number of frequencies for multi-frequency reconstruction (default=256) -mn: In sliding-window maximum-intensity projection, use this number of neighbors in each direction (default=4) -mr: Maximum recursion of reconstruction when waiting for blackboard data, zero means no recursion (default=100) -o: Prefix of output files (default=./image) -pc: Combine phase of channels using a phase correction -pe: Exponent for magnitude weighting when calculating combined phase of all channels (default=0.0) -pf: File name of FIFO (named pipe) to obtain the raw data from -pop: Recipe for post processing of 3D volume after channel combining (default=null) -prp: Recipe for post processing of 3D volume before channel combining (default=null) -pt: Combine and store phase timecourse from all channels -pz: Pad missing raw data (of interrupted measurement) with zeroes -qs: Quality control: Check for spikes in data -rd: Dump signal data and its protocol to files with this prefix, do not reconstruct images -rf: Read reco recipe (pipeline layout) from this file -rp: Reco recipe (pipeline layout) -s: Select certain dimensions ranges (space separated list of 'dim=selection', e.g. slice=3) -sc: Store images from channels separately instead of combining them -sp: Store phase in addition to magnitude -sw: Sliding window reconstruction, e.g. for Spiral/PROPELLER -t1f: Use this type of T1 fit, can be one of 'simple', 'magnitude' (default=simple) -t1l: Level relative to mean value of first echo for setting mask of T1 fit (default=0.50) -t1m: Upper limit for T1 fit [ms] (default=3000.0ms) -to: Timeout for reco in seconds, 0=inifinite (default=0) -type: Image representation type (options=automatic float double s32bit u32bit s16bit u16bit s8bit u8bit , default=automatic) -wdialect: Write data using given dialect of the format. (default is no dialect) -wp: Store the protocol separately to this file. -zp: Minimum size of final image in phase direction obtained zero filling (default=0) -zr: Minimum size of final image in read direction obtained zero filling (default=0) -zs: Minimum size of final image in slice direction obtained zero filling (default=0) -v <loglevel> or <component:loglevel> for debugging/tracing all components or a single component, respectively. Possible values for loglevel are: 0(noLog), 1(errorLog), 2(warningLog), 3(infoLog). -h, --help, -help, --version : Print help text or version information odinreco 1.8.5 March 2012 ODINRECO(1)