04-15-2009
Well, you have to be sure.
Some CPUs support 64 bit and some other dont. Same for mainboards.
This is not really related to Solaris.
You need to find out your precise CPU reference and check with Intel or AMD.
You need to check the mainboard compatibility with the vendor (Dell).
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Whats the difference between 32bit and 64bit OS's or applications. I understand it a little but its just not clicking the way the teacher explained to me
thanks, any info would be much appreciated (1 Reply)
Discussion started by: eloquent99
1 Replies
2. UNIX for Dummies Questions & Answers
when using the command :
cat /proc/cpuinfo I get some basic info back on the cpu..
but it doesn't tell me if I am using a 64 or 32 bit processor ..
a) is this the right command to find this ?
b) if it is not what is ? and how do I get that information..
thanx moxxx68 (2 Replies)
Discussion started by: moxxx68
2 Replies
3. Solaris
Hi,
We are porting our application from 32bit to 64bit.
We tried -xarch=v9, -xarc=v9a and -xport64=full options so that compiler to issue 64bit porting warnings.
But we are not getting any porting warninings
WE are using CC 5.5 compiler on sparc-solaris m/c.
Please tell us some powerful... (0 Replies)
Discussion started by: shobhah
0 Replies
4. Linux
Hi,
I want to know what is command to know which will tell wheather linux is 32 or 64 bit (5 Replies)
Discussion started by: manoj.solaris
5 Replies
5. Linux
Where can I get a list that maps the each Linux version to corresponding 32/64 bits model?
e.g.
OS -> Model (ILP32, LP64, ...)
RHLE3 -> ?
RHLE4 -> ?
RHLE5 -> ?
...
It would be better if there is such a list that contains most of current UNIX OS versions.
... (1 Reply)
Discussion started by: princelinux
1 Replies
6. Programming
Is there an 'easy' way to convert 32Bit code to 64Bit code. I have this benchmark i need to run on different machines and it would be nice if i could run it on the 64 bit machines ass wel.
The output when compiling(1) and running(2) are the following:
(1)
linux:/home/user1/subbench/heapsort #... (7 Replies)
Discussion started by: demuynckr
7 Replies
7. Red Hat
I have an application which builds and executes without error on a 32bit implementation of Linux. When I transferred the code to a new project on a 64bit implementation, the code will build without error, but the pthread functions, such as pthread_attr_setschedparam() return an 'Invalid Argument'... (3 Replies)
Discussion started by: jpelletier116
3 Replies
8. Solaris
Hi Gurus,
I need to check whether the compiler installed in my system supports 64bit compilation.
Server - Sun fire v490
OS - Solaris 5.9
Processor - Sparcv9 (64bit)
Install Directory - /opt/SUNWSpro
Compiler Model - Sun Forte C Compiler.
My development team is claiming that there... (20 Replies)
Discussion started by: Hari_Ganesh
20 Replies
9. Shell Programming and Scripting
Hi,
I have a C code which builds and works fine on 32bit linux machine.
Now i want to convert that code to build and run on 64 bit linux machine. I dont want to maintain two separate sources for 32 and 64 bit build. Same source should get build on 32 as well as 64 bit machine (when a... (2 Replies)
Discussion started by: bhushan123
2 Replies
10. Red Hat
Hi, I'm using fedora for 5 years. recently i decided to install new version (16). after i reboot the computer and want to boot from dvd nothing happen's and system boot's from hard disk (i have setup the bios to directly boot from dvd-rom and my dvd-rom is ok). i have downloaded (again) fc16 dvd... (3 Replies)
Discussion started by: ba$h
3 Replies
LEARN ABOUT DEBIAN
cpuburn
cpuburn(1) cpuburn(1)
NAME
cpuburn, burnBX, burnK6, burnK7, burnMMX, burnP5, burnP6 - a collection of programs to put heavy load on CPU
SYNOPSIS
burnBX
burnK6
burnK7
burnMMX
burnP5
burnP6
DESCRIPTION
These programs are designed to load x86 CPUs as heavily as possible for the purposes of system testing ("burn in"). They have been opti-
mized for different processors. FPU and ALU instructions are coded in an assembler endless loop. They do not test every instruction. The
goal has been to maximize heat production from the CPU, putting stress on the CPU itself, cooling system, motherboard (especially voltage
regulators) and power supply (likely cause of burnBX/burnMMX errors). The programs produce no output, but signal hardware errors by a
return code or (more likely) your machine locking up.
burnP5 is optimized for Intel Pentium with or without MMX CPUs
burnP6 is optimized for Intel PentiumPro, Pentium II & III CPUs
burnK6 is optimized for AMD K6 CPUs
burnK7 is optimized for AMD Athlon/Duron CPUs
burnMMX tests cache/memory interfaces on all CPUs with MMX
burnBX is an alternate cache/memory test for Intel CPUs
USAGE
Burn testing is designed to make your computer glitch if it has hardware problems, so make sure that nothing critical is running and all
critical data is saved back to the hard-drives. The best is to run it with filesystems mounted read-only. Note that root privileges are
not required.
Run the desired program in the background, checking the error result. You'll may want to repeat this command for every processor you have
in an SMP or HyperThreading system. For example,
burnP6 || echo $? &
Monitor progress of cpuburn by ps. You can monitor CPU temperature and/or system voltages through ACPI or using the lm-sensors package if
you system supports it. When finished, kill the burn* process(es). For example,
killall burnP6
BUGS
Report all bug to submit@bugs.debian.org, for more information visit http://bugs.debian.org
AUTHORS
cpuburn was written by Robert Redelmeier <redelm@ev1.net>
June 04, 2011 cpuburn(1)