Hot answers tagged 64bit
18
Because AMD was the first one to release 64-bit x86 (x86-64) CPUs.
the AMD64 architecture was positioned by AMD from the beginning as an evolutionary way to add 64-bit computing capabilities to the existing x86 architecture, as opposed to Intel's approach of creating an entirely new 64-bit architecture with IA-64.
The first AMD64-based processor, ...
10
AMD intially implemented x86-64, before Intel. For this reason, most distros (and other OSs such as OpenBSD) did a first release when it was still AMD only, or renaming to x86-64 wasn't considered worth the effort.
I think one of the another contributing factors to this naming confusion was a conflict between Intel and AMD over naming. Intel had an identity ...
9
32-bit x86 CPUs (since the Pentuim Pro) support up to 64 GiB RAM (using PAE). (The "CONFIG_HIGHMEM64G" kernel option needs to be set to actually use it). Each application can only see 4 GiB at a time (and some of that 4GiB must be used for other things, the exact amount depending on the "Memory split" kernel setting)
64-bit operating systems have some other ...
6
All your ram is accessible even with a 32bit kernel. The main difference is probably that any application cannot address more than 3gb of memory. I don't know if you really use such applications (usually databases, or graphics applications), otherwise you may ignore the problem. Please note that 64bits applications requires more memory (because registers and ...
6
The -march flag permits the compiler to use instructions that are not supported by other CPUs. There are a few instructions that are legal to use with -march=athlon64 that your i7 does not support. These are the 3DNow! and Enhanced 3DNow! instructions that weren't included in MMX or integer SSE. If the code uses instructions like PFPNACC it will fault on ...
6
Set multilib_policy=best in your yum.conf, it defaults to 'all' so it installs both i386 and x86_64 packages. When you set it to 'best' it will only install i386 if there is no x86_64 version.
From the CentOS 5 yum.conf man page:
multilib_policy - Can be set to ’all’ or ’best’. All means
install all possible arches for any package you want to
install. ...
5
The main benefit to 64-bit systems is the increased memory address space which is limited to 4GB with 32-bit systems.
This question on the Superuser SE might be helpful: 32-bit vs. 64-bit systems.
Also, here's an informal exploration of 32-vs-64 bit OSes on LifeHacker (though it focuses on Windows, much of it applies I think)
5
Debian and Ubuntu are moving to a new multiarch implementation (spec). Among other things, this involves moving arch-specific libraries into /usr/lib/<triplet>, dropping the limitations of lib32 and lib64 (where will the new x32 ABI go? where do qemulated binaries live? etc.) as well as extending the package manager to handle mixed-architecture ...
4
Since Ubuntu 11.04 (natty) and Debian 7.0 (wheezy) introduced multiarch support, 32-bit and 64-bit libraries can coexist on one system. To install a 32-bit library libXX:
apt-get install libXX:i386
The ia32-libs package. As of Ubuntu 12.04 precise, it no longer contains any libraries, it only pulls in libXX:i386 packages as dependencies.
The compile part ...
4
Main advantages amd64 over i386
64-bit integer capability
additional registers
additional XMM (SSE) registers
larger physical address space in legacy mode
SSE/SSE2
for more details look at wiki page.
What about performance?
Actually performance will grow up to 20-30% in general case. Its mainly due to intelligent compilers that can optimize even ...
4
With regard to eclipse not being able to find adb, etc, this because without the 32-bit shared libraries needed to run them on the system, they are not executable.
With regard to 32-bit libraries, the situation is fairly simple: you just need to install the appropriate 32-bit libs. On the 64-bit fedora 17 install I have here, the primary 64-bit libraries ...
3
Modern versions of 64bit Ubuntu have dpkg multi-arch enabled by default. You can install 32bit packages by adding :i386 to the end of the package name. You can find more information on multi-arch in Ubuntu here.
3
RAID1 is mirroring, not striping. Furthermore, using BIOS fakeraid is not recommended - Linux software RAID (mdraid) will be more reliable, and will help you to avoid issues like this.
If you are absolutely sure you want to installing GRUB on fakeraid, you must follow a quite complicated procedure, that is described here:
...
3
Compatibility.
First, note that Sun's 64-bit support goes back to 1998, with Solaris 7, well before AMD64 and even Itanium had OS support. By supporting both 32-bit and 64-bit in userland, you could let the vast majority of software run completely unchanged.
Check out the Solaris 64-bit Developer's guide (dated 2005). First, it notes that there are ...
3
Answering the revised question: Why does Linux on sparc64 architecture use 32-bit pointers in user-space and 64-bit pointers in kernel-space?
This was probably done to reduce the size of code both binaries and run time as pointers use half the size in memory while keeping other advantages 64-bit mode has. Of course the drawback is a virtual memory size ...
2
Like Renan said, this is the result of a 32/64 bit mismatch. On OpenSUSE, try zypper in Mesa-32bit to install the 32 bit version of the library. In general, if you have the 64 bit version, you can use rpm -qf to find the package containing the library:
% rpm -qf /usr/lib64/libGLU.so.1
Mesa-7.11-11.4.2.x86_64
On OpenSUSE, the naming convention for ...
2
It is in theory possible, but likely treacherous. Debian multiarch at current supports multiarch libs, but not binaries. So there's that.
The system primarily understands its own architecture from dpkg-architecture (which is actually a perl script, but it extracts the arch info and displays it), which also claims to be able to set the architecture.
...
2
Well, first, mplayer believes this to be mpeg1, which ffmpeg can handle just fine. Or at least, is supposed to be able to handle just fine, and normally mplayer prefers ffmpeg. You could attempt to force it to use a different decoder with -vfm or -vc options (pass "help" to either to get a list). You could also try a different -demuxer (also takes "help" for ...
2
You are probably missing the i386 libc, try installing it with apt-get install libc6-i386.
You can also add multiarch support to your system by running:
dpkg --add-architecture i386
apt-get update
Afterwards you can install a package for i386 with apt-get install package-name:i386 if it supports multiarch.
For more information have a look at the ...
2
You have to install the 32 bit glibc:
# yum install glibc.i686
This removes the misleading 'no such file or directory' message when trying to execute a 32 bit binary. With that the 64 bit Fedora system is capable of executing 64 bit binaries.
This also removes the misleading 'not a dynamic executable' message of ldd when calling ldd on a 32 bit dynamic ...
1
From my shaky understanding: the compilation script is passing the -mcmodel=large option to GCC. This option is only supported since GCC 4.3 (or perhaps 4.4). You seem to have an older version where the option is recognized on the command line but not implemented under the hood.
This option produces an executable running in the large model, which consumes ...
1
The initial port of Linux for amd64 only supported a 40-bit virtual address space, divided in 512GB for the process and 512GB for the kernel. Current versions support 48 bits of virtual address space, divided in 128TB/128TB. This last limitation is intrinsic in the current version of the amd64 architecture: there is simply no way to configure the MMU to make ...
1
My guess is that your /etc/X11/xorg.conf is configured to load the "nvidia" driver but as there's no longer an nvidia card in the system, X fails to start and you get the standard debian "X failed to start" screen (can't remember the exact text but it does have a blue background).
Unless you need particular options in X, your best bet is just to rename ...
1
I've never found one. I use clonezilla as a rescue CD (and network-boot image), and that DOES have a 64-bit version.
If you want 64-bit gparted live, you'll have to make your own, just replacing the kernel with a 64-bit kernel will be enough - it will be able to run the 32-bit userland on the gparted ISO.
BTW, when you do manage to chroot into your system ...
1
Thanks to this page, I got the solution.
Using the JRE x64 rpm mentioned in the question, without icedtea plugin, all you need to do is linking the JRE library to firefox this way :
ln -s /usr/java/jre1.7.0_05/lib/amd64/libnpjp2.so ~/.mozilla/plugins/
In fact I just copied it the first time this is why it crashed. After that you can verify the plugin is ...
1
Not an answer to the question, but it may be difficult to upgrade all packages from x86 to amd64, but you can at least easily install the amd64 kernel package, which will at least allow you to run 64 bit applications and virtual machines and containers (which may be enough for what you need).
Just install the amd64 linux-image package with dpkg -i ...
1
According to the document you posted a link to, the Solaris x86_64 architecture does not use 32-bit pointers in user-space and 64-bit pointers in kernel-space.
Anyway, this document is either incorrect, incomplete/missing to explain what Solaris release is used and what compiler version and options are used or just simply doesn't apply to Solaris but Linux ...
Only top voted, non community-wiki answers of a minimum length are eligible
