On Wednesday 05 March 2008 18:08:33 Neil Bothwick wrote:
> Run lshw and look at the width value for the CPU.
I'd forgotten about lshw - thanks for the reminder.
At the risk of a thread hijack, what should I do about this, which is shown
for both CPU's:
*-cache:2 DISABLED
Does that mean the ha
well said ...
Alan McKinnon wrote:
On Wednesday 05 March 2008, Chris Brennan wrote:
from what you pasted, you have a 32bit cpu. But you have a flag I do
as well, and that is 'ht'. Hyper-Threading is a whole different beast
I know very little about, it's more of an Intel thing for there first
ge
On Wednesday 05 March 2008, Chris Brennan wrote:
> from what you pasted, you have a 32bit cpu. But you have a flag I do
> as well, and that is 'ht'. Hyper-Threading is a whole different beast
> I know very little about, it's more of an Intel thing for there first
> generation dual-core cpu's.
HT i
from what you pasted, you have a 32bit cpu. But you have a flag I do as
well, and that is 'ht'. Hyper-Threading is a whole different beast I
know very little about, it's more of an Intel thing for there first
generation dual-core cpu's.
Uwe Thiem wrote:
On Wednesday 05 March 2008, Chris Brenn
On Wednesday 05 March 2008, Chris Brennan wrote:
> Here is the output of my cpuinfo, I'll point out where it will mean
> 64bit. For the sake of this demonstration, I have only pasted one (1)
> CPU.
>
> model name: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ <-- Here
> will be your first indi
On Wednesday 05 March 2008, Neil Bothwick wrote:
> On Wed, 5 Mar 2008 15:23:55 +0200, Alan McKinnon wrote:
> > Could that same kind soul please repost the info? And if possible
> > the same for AMD?
>
> Run lshw and look at the width value for the CPU.
Aaaahhh. That has to be the most usef
On Wednesday 05 March 2008, cypherstrong wrote:
> Of course :)
>
> the test for amd64 could be fast with a livecd
That might suit someone who's sitting with a new and unknown box on the
desk in front of them. I usually have to discover this for machines
that are in some unknown location and to
On Wednesday 05 March 2008, Stratos Psomadakis wrote:
> O/H cypherstrong έγραψε:
> > another way to test is to run a livecd in amd64 mode on new intel
> > chips if it doesn't work, try the ia64 version
> >
> > if it doesn't work ... your intel is a 32 bits version :)
>
> no need for the ia64...
> i
On Wed, 5 Mar 2008 15:23:55 +0200, Alan McKinnon wrote:
> Could that same kind soul please repost the info? And if possible the
> same for AMD?
Run lshw and look at the width value for the CPU.
--
Neil Bothwick
If all the world is a stage, where is the audience sitting?
signature.asc
Desc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stratos Psomadakis wrote:
| O/H cypherstrong έγραψε:
|> another way to test is to run a livecd in amd64 mode on new intel chips
|> if it doesn't work, try the ia64 version
|>
|> if it doesn't work ... your intel is a 32 bits version :)
|>
| no ne
On 3/5/08, Uwe Thiem <[EMAIL PROTECTED]> wrote:
>
> I am a bit confused now. I always thought my CPU was 32bit. Here are
> the relevant two lines from my /proc/cpuinfo:
> So the model name does not indicate anything 64bit while the flags
> contain lm, nx and lahf_lm.
Like I said, take the family
On Wednesday 05 March 2008, Chris Brennan wrote:
> Here is the output of my cpuinfo, I'll point out where it will mean
> 64bit. For the sake of this demonstration, I have only pasted one
> (1) CPU.
>
> [EMAIL PROTECTED] ~ $ cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu
On 3/5/08, Andrew MacKenzie <[EMAIL PROTECTED]> wrote:
>
> They do identify themselves, but they may not indicate 64 vs. 32 bit.
>
Something one can always do is "cat /proc/cpuinfo" and then check the family
and model at http://gentoo-wiki.com/Safe_Cflags .
If it indicates 64-bit profile and Cflag
+++ Chris Brennan [gentoo-user] [Wed, Mar 05, 2008 at 11:36:47AM -0500]:
> Here is the output of my cpuinfo, I'll point out where it will mean
> 64bit. For the sake of this demonstration, I have only pasted one (1) CPU.
>
> [EMAIL PROTECTED] ~ $ cat /proc/cpuinfo
> processor : 0
> vendor_id
Of course :)
the test for amd64 could be fast with a livecd ... or with cpuinfo and good
knowledge of flags
Le Wednesday 05 March 2008 17:45:16 Stratos Psomadakis, vous avez écrit :
> O/H cypherstrong έγραψε:
> > another way to test is to run a livecd in amd64 mode on new intel chips
> > if it d
O/H cypherstrong έγραψε:
another way to test is to run a livecd in amd64 mode on new intel chips
if it doesn't work, try the ia64 version
if it doesn't work ... your intel is a 32 bits version :)
no need for the ia64...
it's for intel's itanium cpus...
ia64 is not compatible with x86...
if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is the output of my cpuinfo, I'll point out where it will mean
64bit. For the sake of this demonstration, I have only pasted one (1) CPU.
[EMAIL PROTECTED] ~ $ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family
another way to test is to run a livecd in amd64 mode on new intel chips
if it doesn't work, try the ia64 version
if it doesn't work ... your intel is a 32 bits version :)
Le Wednesday 05 March 2008 16:47:10 kashani, vous avez écrit :
> Alan McKinnon wrote:
> > Hi all,
> >
> > Sometime in the la
Alan McKinnon wrote:
Hi all,
Sometime in the last month someone posted (in a thread that went wildly
OT) a definite way to determine if an Intel cpu is 32 or 64 bit.
Unfortunately I can't find the post anymore.
It involved checking the cpu-family, model and flags fields in cpuinfo.
Could th
O/H Alan McKinnon έγραψε:
Hi all,
Sometime in the last month someone posted (in a thread that went wildly
OT) a definite way to determine if an Intel cpu is 32 or 64 bit.
Unfortunately I can't find the post anymore.
It involved checking the cpu-family, model and flags fields in cpuinfo.
Cou
Hi all,
Sometime in the last month someone posted (in a thread that went wildly
OT) a definite way to determine if an Intel cpu is 32 or 64 bit.
Unfortunately I can't find the post anymore.
It involved checking the cpu-family, model and flags fields in cpuinfo.
Could that same kind soul please
21 matches
Mail list logo
