Below is a list of frequently asked questions about Arch Linux on 64-bit. When all else fails, use the "dual" version of the ISO of choice.

+

[[el:Arch64 FAQ]]

+

[[es:Arch64 FAQ]]

+

[[it:Arch64 FAQ]]

+

[[ru:Arch64 FAQ]]

+

[[sr:Arch64 FAQ]]

+

[[uk:Arch64 FAQ]]

+

[[zh-CN:Arch64 FAQ]]

+

Below is a list of frequently asked questions about Arch Linux on 64-bit.

== How do I determine if my processor is x86_64 compatible? ==

== How do I determine if my processor is x86_64 compatible? ==

Line 17:

Line 24:

=== Windows users ===

=== Windows users ===

Using the freeware [http://www.cpuid.com/cpuz.php CPU-Z] you can determine whether your CPU is 64-bit compatible.

Using the freeware [http://www.cpuid.com/cpuz.php CPU-Z] you can determine whether your CPU is 64-bit compatible.

−

CPUs with AMD's instructional set "AMD64" or Intel's solution "EM64T" should be compatible with the x86_64 releases and binary packages.

+

CPUs with AMD's instruction set "AMD64" or Intel's solution "EM64T" should be compatible with the x86_64 releases and binary packages.

== Should I use the 32 or 64 bit version of Arch? ==

== Should I use the 32 or 64 bit version of Arch? ==

−

If your processor is [[wikipedia:X86-64|x86_64]] compatible you should use Arch64.

+

If your processor is [[wikipedia:X86-64|x86_64]] compatible, you should use Arch64.

== How can I install Arch64? ==

== How can I install Arch64? ==

−

Just use our [https://www.archlinux.org/download/ official install ISO CD].

+

Just use our [https://www.archlinux.org/download/ official installation ISO CD].

== How complete is the port? ==

== How complete is the port? ==

Line 29:

Line 36:

== Will I have all the packages from my 32-bit Arch I am used to? ==

== Will I have all the packages from my 32-bit Arch I am used to? ==

−

The Repositories are ported and pretty much everything should work as expected.

+

The repositories are ported and pretty much everything should work as expected.

−

Rarely an old package in [[AUR]] will only have {{ic|'i686'}} listed, but typically they work for 64-bit too, just try adding {{ic|'x86_64'}}.

+

Rarely, an old package in the [[Arch User Repository|AUR]] will only have {{ic|'i686'}} listed, but typically they work for 64-bit too. Just try adding {{ic|'x86_64'}}.

== Why 64-bit? ==

== Why 64-bit? ==

−

It is (under most circumstances) faster and as an added bonus also inherently more secure due to the nature of [[wikipedia:Address space layout randomization|Address space layout randomization (ASLR)]] in combination with [[wikipedia:Position-independent code|Position-independent code (PIC)]] and the [[wikipedia:NX Bit|NX Bit]] which is not available in the stock i686 Kernel due to disabled PAE. If your computer is running 4GB or over of usable RAM, 64-bit should be considered as any additional ram cannot be allocated by an 32-bit OS.

+

It is faster under most circumstances and as an added bonus also inherently more secure due to the nature of [[wikipedia:Address space layout randomization|Address space layout randomization (ASLR)]] in combination with [[wikipedia:Position-independent code|Position-independent code (PIC)]] and the [[wikipedia:NX Bit|NX Bit]] which is not available in the stock i686 kernel due to disabled PAE. If your computer is running 4 GB or more of usable RAM, 64-bit should be strongly considered as any additional RAM cannot be allocated by a 32-bit OS.

Programmers also increasingly tend to care less about 32-bit ("legacy") as "new" x86 CPUs typically support the 64-bit extensions.

Programmers also increasingly tend to care less about 32-bit ("legacy") as "new" x86 CPUs typically support the 64-bit extensions.

−

There are many more reasons we could list here to tell you to avoid 32-bit, but between the kernel, userspace and individual programs its simply not viable to list every last thing that 64-bit does much better these days.

+

There are many more reasons we could list here to tell you to avoid 32-bit, but between the kernel, userspace and individual programs it is simply not viable to list every last thing that 64-bit does much better these days.

For further details watch our [https://www.archlinux.org/packages/differences/ differences reports]. There you will find a list comparing 32-/64-bit package versions.

For further details watch our [https://www.archlinux.org/packages/differences/ differences reports]. There you will find a list comparing 32-/64-bit package versions.

== How can I file bugs? ==

== How can I file bugs? ==

−

Simply use Arch's [https://bugs.archlinux.org/ flyspray] but select x86_64 in the Architecture field if you think it is a port-related problem!

+

Simply use Arch's [https://bugs.archlinux.org/ Flyspray] but select x86_64 in the Architecture field if you think it is a port-related problem!

== What repositories should I set up for pacman to use? ==

== What repositories should I set up for pacman to use? ==

Line 65:

Line 72:

Nothing, really. Almost all applications support 64-bit by now or are in the transition to become 64-bit compatible.

Nothing, really. Almost all applications support 64-bit by now or are in the transition to become 64-bit compatible.

−

The biggest problem are packages that are either '''closed source''' or contains x86-specific assembly that is cumbersome to port to 64-bit (typical for emulators).

+

The biggest problem are packages that are either '''closed source''' or contain x86-specific assembly that is cumbersome to port to 64-bit (typical for emulators).

−

These applications were previously problematic, but are now available in the [[AUR]] and work fine:

+

These applications were previously problematic but are now available in the [[Arch User Repository|AUR]] and work fine:

* Acrobat Reader is not available in 64-bit, but you can run the 32-bit version in compatibility mode. There are also many other open source alternatives that can be used to read PDF files.

* Acrobat Reader is not available in 64-bit, but you can run the 32-bit version in compatibility mode. There are also many other open source alternatives that can be used to read PDF files.

Line 75:

Line 82:

Yes!

Yes!

−

* You can install {{ic|1=lib32-*}} libraries from the multilib repository. To use this repository, you should add the following lines to your {{ic|/etc/pacman.conf}}:

+

* You can install {{ic|1=lib32-*}} libraries from the [multilib] repository. To use this repository, you should add the following lines to your {{ic|/etc/pacman.conf}}:

[multilib]

[multilib]

+

SigLevel = PackageRequired

Include = /etc/pacman.d/mirrorlist

Include = /etc/pacman.d/mirrorlist

−

At this time (December 2011), it contains wine and skype. Furthermore, a multilib compiler is available.

+

At this time (December 2011), [multilib] contains wine and Skype. Furthermore, a multilib compiler is available.

* Or you can create another chroot with 32-bit system (refer to [[Arch64 Install bundled 32bit system]]):

* Or you can create another chroot with 32-bit system (refer to [[Arch64 Install bundled 32bit system]]):

−

Boot into Arch64, startx, open a term.

+

Boot into Arch64, startx, open a terminal.

$ xhost +local:

$ xhost +local:

$ su

$ su

Line 93:

Line 101:

$ /usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox

$ /usr/bin/command-you want # or eg: /opt/mozilla/bin/firefox

−

Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in rc.local to ensure you get all you need for the 32-bit apps (assuming {{ic|/mnt/arch32}} is mounted in fstab):

+

Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in {{ic|/etc/rc.local}} to ensure you get all you need for the 32-bit apps (assuming {{ic|/mnt/arch32}} is mounted in {{ic|/etc/fstab}}):

{{Note|If the system has the {{ic|base-devel}} package installed, users must replace the [extra] versions with the [mutlilib] versions as shown below.}}

−

{{Note|1= {{pkg|gcc-multilib}} is capable of building 32-bit and 64-bit code. You can safely install {{ic|multilib-devel}} and remove {{ic|base-devel}} on x86_64. See https://bbs.archlinux.org/viewtopic.php?id=102828 for more information.}}

+

{{Note|

+

*If the system has the {{ic|base-devel}} package group installed, users must replace the [extra] versions with the [mutlilib] versions as shown below.

+

* {{Pkg|gcc-multilib}} is capable of building 32-bit and 64-bit code. You can safely install {{ic|multilib-devel}} to replace the packages shown below, but you still need {{ic|base-devel}} for the other packages it includes. See <nowiki>https://bbs.archlinux.org/viewtopic.php?id=102828</nowiki> for more information.

Compile packages on x86_64 for i686 is as easy as adding the following lines to alternate config file, e.g. {{ic|~/.makepkg.i686.conf}}

+

Compiling packages on x86_64 for i686 is as easy as adding the following lines to an alternate configuration file (e.g. {{ic|~/.makepkg.i686.conf}})

CARCH="i686"

CARCH="i686"

CHOST="i686-pc-linux-gnu"

CHOST="i686-pc-linux-gnu"

Line 164:

Line 168:

=== Chroot ===

=== Chroot ===

−

To use a i686 chroot (installation with i686 iso "quickinstall" is recommended for the quick way to install it inside Arch64 or see [[Arch64 Install bundled 32bit system]]), install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:

+

{{out of date|This sections mentions the "linux32" package which does not exist.}}

+

To use an i686 chroot (installation with i686 ISO "quickinstall" is recommended for the quick way to install it inside Arch64 or see [[Arch64 Install bundled 32bit system]]), install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:

to share sources from host to chroot system for pkg building used in {{ic|/etc/makepkg.conf}}.

to share sources from host to chroot system for pkg building used in {{ic|/etc/makepkg.conf}}.

== Can I upgrade/switch my system from i686 to x86_64 without reinstalling? ==

== Can I upgrade/switch my system from i686 to x86_64 without reinstalling? ==

−

Yes. A forum thread has been created [https://bbs.archlinux.org/viewtopic.php?id=64485 here] which outlines steps taken to successfully migrate an install from 32 to 64 bit without losing any configs/settings/data. Note: A large external drive was used for the transfer.

+

No. However a forum thread has been created [https://bbs.archlinux.org/viewtopic.php?id=64485 here] which outlines steps taken to successfully migrate an install from 32 to 64 bit without losing any configs/settings/data. Note: A large external hard drive was used for the transfer.

−

However, you can also start the system with the Arch64 install CD, mount the disk, backup anything you may want to keep that is not a 32-bit binary (e.g: {{ic|/home}} & {{ic|/etc}}), and install.

+

However, you can also start the system with the Arch64 installation CD, mount the disk, backup anything you may want to keep that is not a 32-bit binary (e.g: {{ic|/home}} & {{ic|/etc}}), and install.

You may also want to read [[Migrating Between Architectures Without Reinstalling]].

You may also want to read [[Migrating Between Architectures Without Reinstalling]].

Revision as of 12:58, 5 June 2013

zh-CN:Arch64 FAQ
Below is a list of frequently asked questions about Arch Linux on 64-bit.

Windows users

Using the freeware CPU-Z you can determine whether your CPU is 64-bit compatible.
CPUs with AMD's instruction set "AMD64" or Intel's solution "EM64T" should be compatible with the x86_64 releases and binary packages.

How can I install Arch64?

How complete is the port?

Will I have all the packages from my 32-bit Arch I am used to?

The repositories are ported and pretty much everything should work as expected.

Rarely, an old package in the AUR will only have 'i686' listed, but typically they work for 64-bit too. Just try adding 'x86_64'.

Why 64-bit?

It is faster under most circumstances and as an added bonus also inherently more secure due to the nature of Address space layout randomization (ASLR) in combination with Position-independent code (PIC) and the NX Bit which is not available in the stock i686 kernel due to disabled PAE. If your computer is running 4 GB or more of usable RAM, 64-bit should be strongly considered as any additional RAM cannot be allocated by a 32-bit OS.

Programmers also increasingly tend to care less about 32-bit ("legacy") as "new" x86 CPUs typically support the 64-bit extensions.

There are many more reasons we could list here to tell you to avoid 32-bit, but between the kernel, userspace and individual programs it is simply not viable to list every last thing that 64-bit does much better these days.

For further details watch our differences reports. There you will find a list comparing 32-/64-bit package versions.

How can I file bugs?

Simply use Arch's Flyspray but select x86_64 in the Architecture field if you think it is a port-related problem!

What repositories should I set up for pacman to use?

All repositories are supported for the port.

How can I patch existing PKGBUILDs for use with Arch64?

Add the following variable to all ported packages:

arch=('i686' 'x86_64')

Add small patches directly to the sources and md5sums area but use for complete different sources:

What will I miss in Arch64?

Nothing, really. Almost all applications support 64-bit by now or are in the transition to become 64-bit compatible.

The biggest problem are packages that are either closed source or contain x86-specific assembly that is cumbersome to port to 64-bit (typical for emulators).

These applications were previously problematic but are now available in the AUR and work fine:

Acrobat Reader is not available in 64-bit, but you can run the 32-bit version in compatibility mode. There are also many other open source alternatives that can be used to read PDF files.

Everything else should work perfectly fine. If you miss any Arch32 package in our port and you know that it will compile on x86_64 (perhaps you have found it as native packages in another 64-bit distribution), just contact the developers or request a new package in the forums.

Can I run 32-bit apps inside Arch64?

Yes!

You can install lib32-* libraries from the [multilib] repository. To use this repository, you should add the following lines to your /etc/pacman.conf:

Some 32-bit apps (like OpenOffice) may require additional bindings. The following lines can be placed in /etc/rc.local to ensure you get all you need for the 32-bit apps (assuming /mnt/arch32 is mounted in /etc/fstab):

upgrade your system with pacman -Syu and install the gcc-multilib package.

Note:

If the system has the base-devel package group installed, users must replace the [extra] versions with the [mutlilib] versions as shown below.

gcc-multilib is capable of building 32-bit and 64-bit code. You can safely install multilib-devel to replace the packages shown below, but you still need base-devel for the other packages it includes. See https://bbs.archlinux.org/viewtopic.php?id=102828 for more information.

Chroot

This article or section is out of date.

Reason: This sections mentions the "linux32" package which does not exist. (Discuss in Talk:64-bit FAQ#)

To use an i686 chroot (installation with i686 ISO "quickinstall" is recommended for the quick way to install it inside Arch64 or see Arch64 Install bundled 32bit system), install "linux32" wrapper pkg from current to make the chroot behave like a real i686 system. Then use this script to login into the chroot environment as root:

to share sources from host to chroot system for pkg building used in /etc/makepkg.conf.

Can I upgrade/switch my system from i686 to x86_64 without reinstalling?

No. However a forum thread has been created here which outlines steps taken to successfully migrate an install from 32 to 64 bit without losing any configs/settings/data. Note: A large external hard drive was used for the transfer.

However, you can also start the system with the Arch64 installation CD, mount the disk, backup anything you may want to keep that is not a 32-bit binary (e.g: /home & /etc), and install.