Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Which installation medium do I use?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
static_k
n00b
n00b


Joined: 10 Oct 2005
Posts: 73
Location: NY

PostPosted: Wed Feb 10, 2010 7:13 am    Post subject: Which installation medium do I use? Reply with quote

Hi Everyone,

It's been a long time since I setup gentoo and I just got a new laptop I want to put it on. It's a dell e6400 and I'm a bit confused on which iso and stage 3 to download. I believe it is a 64bit processor according to the Intel site.
http://ark.intel.com/Product.aspx?id=37006

Should I be downloading the x86 iso's or the amd64 iso's?

Here is my /proc/cpuinfo:
Code:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz
stepping        : 10
cpu MHz         : 2526.982
cache size      : 3072 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl
vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida tpr_shadow vnmi
flexpriority
bogomips        : 5053.96
clflush size    : 64
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz
stepping        : 10
cpu MHz         : 2526.982
cache size      : 3072 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl
vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida tpr_shadow vnmi
flexpriority
bogomips        : 5054.09
clflush size    : 64
power management:


Then I was going to setup the make.conf as follows:
Code:

CFLAGS="-march=core2 -msse4.1 -O2 -pipe"
CXXFLAGS="${CFLAGS}"
CHOST="x86_64-pc-linux-gnu"
MAKEOPTS="-j3"


Thanks in advance for the help :)
Back to top
View user's profile Send private message
bombcar
Guru
Guru


Joined: 08 Apr 2003
Posts: 446
Location: Lincoln Acres, CA

PostPosted: Wed Feb 10, 2010 7:16 am    Post subject: Reply with quote

amd64 = x86-64.

You have a core2duo, so you want x86-64 almost certainly. Your make.conf looks decent, but you might want to check. I couldn't your CPU on the Safe CFLAGS wiki page.
Back to top
View user's profile Send private message
NathanZachary
Moderator
Moderator


Joined: 30 Jan 2007
Posts: 2281
Location: /home/zach

PostPosted: Wed Feb 10, 2010 7:35 am    Post subject: Reply with quote

Are you going to be using the stable or the testing branch? Your CFLAGS might be better off as -march=native. You might also want to put in -fomit-frame-pointer to free up a register. Lastly, you might want to check out Diego Petteno's article on using the LDFLAG --as-needed:

http://www.gentoo.org/proj/en/qa/asneeded.xml

I have been using it for quite some time now, and have been pleased with the results.
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---
Back to top
View user's profile Send private message
d2_racing
Moderator
Moderator


Joined: 25 Apr 2005
Posts: 12867
Location: Ste-Foy,Canada

PostPosted: Wed Feb 10, 2010 1:13 pm    Post subject: Reply with quote

I'm not sure, but I think that with native, it will add automagically -fomit-frame-pointer .
_________________
Sysadmin of Funtoo-Québec.org
Wiki
Signature
IRC on Freenode : #funtoo-quebec
Back to top
View user's profile Send private message
Jaglover
Advocate
Advocate


Joined: 29 May 2005
Posts: 3404
Location: Saint Amant, Acadiana

PostPosted: Wed Feb 10, 2010 1:39 pm    Post subject: Reply with quote

Not sure, but isn't -fomit-frame-pointer default with 64bit anyhow?
Back to top
View user's profile Send private message
Mike Hunt
Watchman
Watchman


Joined: 19 Jul 2009
Posts: 5287

PostPosted: Wed Feb 10, 2010 1:45 pm    Post subject: Reply with quote

On x86 it must be explicitely activated...
Quote:
-fomit-frame-pointer

This is a very common flag designed to reduce generated code size. It is turned on at all levels of -O (except -O0) on architectures where doing so does not interfere with debugging (such as x86-64), but you may need to activate it yourself by adding it to your flags. Though the GNU gcc manual does not specify all architectures it is turned on by using -O, you will need to explicitly activate it on x86. However, using this flag will make debugging hard to impossible.

From: http://www.gentoo.org/doc/en/gcc-optimization.xml
Back to top
View user's profile Send private message
yngwin
Developer
Developer


Joined: 19 Dec 2002
Posts: 4219
Location: Suzhou, China

PostPosted: Wed Feb 10, 2010 2:05 pm    Post subject: Reply with quote

Quote:
It is turned on at all levels of -O (except -O0) on architectures where doing so does not interfere with debugging (such as x86-64)

_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF
Back to top
View user's profile Send private message
static_k
n00b
n00b


Joined: 10 Oct 2005
Posts: 73
Location: NY

PostPosted: Wed Feb 10, 2010 2:51 pm    Post subject: Reply with quote

bombcar wrote:
amd64 = x86-64.

You have a core2duo, so you want x86-64 almost certainly. Your make.conf looks decent, but you might want to check. I couldn't your CPU on the Safe CFLAGS wiki page.


Thanks. I guess I was just confused on the naming. I thought amd64 thought that you had to have an AMD brand processor.
Back to top
View user's profile Send private message
NathanZachary
Moderator
Moderator


Joined: 30 Jan 2007
Posts: 2281
Location: /home/zach

PostPosted: Wed Feb 10, 2010 8:08 pm    Post subject: Reply with quote

That is a point that causes confusion often. It was named that way originally, and the naming scheme has been kept for consistency.
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---
Back to top
View user's profile Send private message
d2_racing
Moderator
Moderator


Joined: 25 Apr 2005
Posts: 12867
Location: Ste-Foy,Canada

PostPosted: Thu Feb 11, 2010 3:45 am    Post subject: Reply with quote

In fact, back in 2003 I think or even earlier, Gentoo or maybe the first GCC 64 bits release created the AMD64 profile, because AMD was the first one to introduce 64 bits CPU.
_________________
Sysadmin of Funtoo-Québec.org
Wiki
Signature
IRC on Freenode : #funtoo-quebec
Back to top
View user's profile Send private message
rtomek
Apprentice
Apprentice


Joined: 05 Jan 2007
Posts: 209
Location: Chicago

PostPosted: Thu Feb 11, 2010 5:46 am    Post subject: Reply with quote

d2_racing wrote:
In fact, back in 2003 I think or even earlier, Gentoo or maybe the first GCC 64 bits release created the AMD64 profile, because AMD was the first one to introduce 64 bits CPU.


I do believe that Itanium (IA64) came first though. Then AMD came out with operon/Athlon64 so Intel licensed the AMD64 instruction set from AMD or something along those lines so technically it is an AMD-developed instruction set and they were the first to introduce what is known now as an x86_64 CPU.
Back to top
View user's profile Send private message
fangorn
Veteran
Veteran


Joined: 31 Jul 2004
Posts: 1872

PostPosted: Thu Feb 11, 2010 10:59 am    Post subject: Reply with quote

amd64 is as ia64 (Itanium) named after the company that invented it.

Where ia64 is a completely new architecture widely independent from ia32 (x86 - in other distributions called i386, i486, i586 (Pentium), i686 (Pentium Pro, Pentium 4 AFAIK)). The i stands for intel. Main concern in design was 64bit performance, so running 32bit programs on ia64 one was and is a major PITA.

amd64 came later and is an extension of the 32bit x86 architecture. One major goal in design was that running existing 32bit programs should be at least as fast as on the processors recent at the time. Actually it was first called x86_64, but it seems some AMD marketing guy thought it would be better to call it amd64.

Through the patent exchange deal between Intel and AMD, Intel has the right to build own processors using the amd64 architecture. Then the name confusion started, as Intel called their version EM64T, some still call it x86_64 (which is the most precise naming IMHO) and later on Microsoft called it x64.

As I had 64bit Linux on more than 10 machines before Intel thought about building own processors using it, I tend to call it amd64. :wink:
_________________
Video Encoding scripts collection | Project page
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum