Difference between pages "Install/Network" and "Corei7"

(Difference between pages)
(Created page with "<noinclude> {{Note|This is a template that is used as part of the Installation instructions, to describe the process of configuring the network. Templates are being used to al...")
 
 
Line 1: Line 1:
<noinclude>
+
{{Subarch
{{Note|This is a template that is used as part of the Installation instructions, to describe the process of configuring the network. Templates are being used to allow multiple variant install guides that use most of the same re-usable parts.}}
+
|CPU Family=64-bit Intel Processors
</noinclude>
+
|subarch=corei7
=== Configuring your network ===
+
|CHOST=x86_64-pc-linux-gnu
 +
|CFLAGS=-march=corei7 -O2 -pipe
 +
|USE=mmx sse sse2 sse3 ssse3 sse4
 +
|Description=The '''corei7''' subarch supports the Nehalem, Westmere, Sandy_Bridge,  Ivy Bridge, and Haswel microarchitecture-based Intel Pentium/Celeron, Intel Core i3, i5, i7 and Xeon Processors.
 +
}}
 +
Beginning in November 2008, Intel launched the first Core i7 processor, codenamed [[Wikipedia:Bloomfield_(microprocessor)|Bloomfield]], based on the [[Wikipedia:Nehalem_(microarchitecture)|Nehalem]] microarchitecture. With this launch, they also added to and modified the conventions used in their [[Wikipedia:Intel_Core|Intel Core]] branding scheme. '''(Not to be confused with the [[Wikipedia:Intel Core (microarchitecture)|Intel Core microarchitecture]]. See [[core2_64]].)'''. This new naming scheme distinguishes between grades of processors rather than microarchitectures or design. Therefore, the '''corei7''' subarch supports the [[Wikipedia:Nehalem_(microarchitecture)|Nehalem]], [[Wikipedia:Westmere_(microarchitecture)|Westmere]], [[Wikipedia:Sandy_Bridge_(microarchitecture)|Sandy Bridge]],  [[Wikipedia:Ivy_Bridge_(microarchitecture)|Ivy Bridge]], and [[Wikipedia:Haswell_(microarchitecture)|Haswell]] microarchitectures under the following brand names:
  
It's important to ensure that you will be able to connect to your local-area network after you reboot into Funtoo Linux. There are three approaches you can use for configuring your network: NetworkManager, dhcpcd, and the [[Funtoo Linux Networking]] scripts. Here's how to choose which one to use based on the type of network you want to set up.
+
* Intel Pentium/Celeron (low-level consumer)
 +
* Intel Core i3 (entry-level consumer)
 +
* Intel Core i5 (mainstream consumer)
 +
* Intel Core i7 (high-end consumer/business)
 +
* Intel Xeon (business server/workstation)
  
==== Wi-Fi ====
+
See the following links for a list of supported [[Wikipedia:Celeron|Celeron]], [[Wikipedia:Pentium|Pentium]], [[Wikipedia:Intel_Core#Nehalem_microarchitecture_based|Nehalem]], [[Wikipedia:Westmere_(microarchitecture)|Westmere]], [[Wikipedia:Intel_Core#Sandy_Bridge_microarchitecture_based|Sandy Bridge]], [[Wikipedia:Intel_Core#Ivy_Bridge_microarchitecture_based|Ivy Bridge]], and [[Wikipedia:Intel_Core#Haswell_microarchitecture_based|Haswell]] processors.
===== Using NetworkManager =====
+
For laptop/mobile systems where you will be using Wi-Fi and connecting to various networks, NetworkManager is strongly recommended. The Funtoo version of NetworkManager is fully functional even from the command-line, so you can use it even without X or without the Network Manager applet. Here are the steps involved in setting up NetworkManager:
+
 
+
<console>
+
(chroot) # ##i##emerge linux-firmware
+
(chroot) # ##i##emerge networkmanager
+
(chroot) # ##i##rc-update add NetworkManager default
+
</console>
+
 
+
Above, we installed linux-firmware which contains a complete collection of available firmware for many hardware devices including Wi-Fi adapters, plus NetworkManager to manage our network connection. Then we added NetworkManager to the <code>default</code> runlevel so it will start when Funtoo Linux boots.
+
 
+
After you reboot into Funtoo Linux, you will be able to add a Wi-Fi connection this way:
+
 
+
<console>
+
# ##i##addwifi -S wpa -K 'wifipassword' mywifinetwork
+
</console>
+
 
+
The <code>addwifi</code> command is used to configure and connect to a WPA/WPA2 Wi-Fi network named <code>mywifinetwork</code> with the password <code>wifipassword</code>. This network configuration entry is stored in <code>/etc/NetworkManager/system-connections</code> so that it will be remembered in the future. You should only need to enter this command once for each Wi-Fi network you connect to.
+
 
+
===== Using wpa_supplicant =====
+
If for some reason you don't want to use a tool such as NetworkManager or <code>wicd</code>, you can use wpa_supplicant for wireless network connections.
+
 
+
First, emerge wpa_supplicant:
+
 
+
<console>
+
(chroot) ###i## emerge -a wpa_supplicant
+
</console>
+
 
+
Now, edit the wpa_supplicant configuration file, located at /etc/wpa_supplicant.conf.
+
The syntax is very easy:
+
<pre>
+
network={
+
ssid="MyWifiName"
+
psk="lol42-wifi"
+
}
+
 
+
network={
+
ssid="Other Network"
+
psk="6d96270004515a0486bb7f76196a72b40c55a47f"
+
}
+
</pre>
+
 
+
You will need to add both <code>wpa_supplicant</code> and <code>dhcpcd</code> to the default runlevel. <code>wpa_supplicant</code> will connect to your access point, and <code>dhcpcd</code> will acquire an IP address via DHCP:
+
 
+
<console>
+
(chroot) # ##i##rc-update add dhcpcd default
+
(chroot) # ##i##rc-update add wpa_supplicant default
+
</console>
+
 
+
==== Desktop (Wired Ethernet) ====
+
 
+
For a home desktop or workstation with wired Ethernet that will use DHCP, the simplest and most effective option to enable network connectivity is to simply add <code>dhcpcd</code> to the default runlevel:
+
 
+
<console>
+
(chroot) # ##i##rc-update add dhcpcd default
+
</console>
+
 
+
When you reboot, <code>dhcpcd</code> will run in the background and manage all network interfaces and use DHCP to acquire network addresses from a DHCP server.
+
 
+
==== Server (Static IP) ====
+
 
+
For servers, the [[Funtoo Linux Networking]] scripts are recommended. They are optimized for static configurations and things like virtual ethernet bridging for virtualization setups. See [[Funtoo Linux Networking]] for information on how to use Funtoo Linux's template-based network configuration system.
+

Latest revision as of 10:02, December 20, 2014

corei7 (Sub-architecture)

Note

This page describes a sub-architecture for Funtoo Linux, which is a particular set of optimizations that is used for a Funtoo Linux build.

CPU Family64-bit Intel Processors
CHOSTx86_64-pc-linux-gnu
CFLAGS-march=corei7 -O2 -pipe
USEmmx sse sse2 sse3 ssse3 sse4
SummaryThe corei7 subarch supports the Nehalem, Westmere, Sandy_Bridge, Ivy Bridge, and Haswel microarchitecture-based Intel Pentium/Celeron, Intel Core i3, i5, i7 and Xeon Processors.


Beginning in November 2008, Intel launched the first Core i7 processor, codenamed Bloomfield, based on the Nehalem microarchitecture. With this launch, they also added to and modified the conventions used in their Intel Core branding scheme. (Not to be confused with the Intel Core microarchitecture. See core2_64.). This new naming scheme distinguishes between grades of processors rather than microarchitectures or design. Therefore, the corei7 subarch supports the Nehalem, Westmere, Sandy Bridge, Ivy Bridge, and Haswell microarchitectures under the following brand names:

  • Intel Pentium/Celeron (low-level consumer)
  • Intel Core i3 (entry-level consumer)
  • Intel Core i5 (mainstream consumer)
  • Intel Core i7 (high-end consumer/business)
  • Intel Xeon (business server/workstation)

See the following links for a list of supported Celeron, Pentium, Nehalem, Westmere, Sandy Bridge, Ivy Bridge, and Haswell processors.