Fedora

Fedora Core 2 for x86_64 Release FAQ

What is the current state of a Fedora Core for x86_64 release?
The x86_64 port of  Fedora Core 2 is now a tier 1 architecture, and the x86_64 release for Core 2 was concurrent with i386. This release should support most AMD64 platforms out of the box and the upcoming Intel ia32e/EM64T. The eMachines laptops (m6805/m6807/6809) are not officially supported, but can be made to work with minimal effort.

Where can I get this release?
This release is currently available from the standard Fedora Mirrors under the "2" tree as the x86_64 release.  It is also available via torrent.

This release does not boot on my system, what should I do?
The first thing to do is try appending acpi=off to the kernel (grub boot line). Feedback if this fixed your problem so that we may look into the cause. If this did not fix your problem, you might run a memtest or try a BIOS update as this will point to the issue in most boot problems..

I notice some RPMS are installed twice, how do I handle multilib?
A few things of note here:
* rpm and yum both support name-version-release.arch so for installing foo-1.1-1 RPMs, you can explicitly call rpm -ivh foo-1.1-1.i386 foo-1.1-1.x86_64. You can also query and remove with this method. yum will default to the system architecture if given a choice, so to install say 32bit firefox where you have both 32bit and 64bit available in your repositories, you can call 'yum install firefox.i386' and it should do the right thing.

* At this time, apt is *not* biarch compatible, but I am told this is being addressed.

* libtool in Fedora releases is patched to handle multilib systems appropriatelyr. While this patch has been pushed upstream, it may not be in all distributions yet. If you are building an rpm or a tarball you may need to libtoolize, even if the libtool scripts are already there. Try without first, but if the build is looking for things in /*lib you might try the following before running configure (in %prep for rpm specs) as the easy fix:

libtoolize --force
aclocal --force
automake --add-missing
autoconf
autoheader

What can I do for Mozilla Plug-ins?
Mozilla is 64bit in the Core 2 release,  and as a result all of the standard 32bit plug-ins will not work.  I would recommend users who require 32bit plugins install the 32bit firefox browser from the x86_64 Extras repository, or fedora.us Firefox is generally stable, speedy, and has no dependencies outside of Fedora Core. Note that mozplugger calls external applications, so it is bit neutral and can call 32bit and 64bit helpers. You might want to start putting in requests for 64bit builds of your favorite binary only plugin providers

Where can I get additional software for this release?
As x86_64 is a relatively new platform, many of the repositories available do not have a tree for x86_64 64bit 3rd party apps and utilities. The x86_64 builds of most of ifedora.us against FC2 are available from the x86_64 Extras repository and I am working on filling in what is not already there. You will want to add my gpg key with 'rpm --import http://www.linuxtx.org/jmforbes_pubkey.asc' before you use this repository. I have also heard that someone is working on x86_64 builds of the livna repositories but I do not know the details yet.
If your preferred application is not available in a 64bit repository, the best recommendation is to download source rpms and rebuild them. 'rpmbuild --rebuild --target x86_64 foo.3rdparty-1.src.rpm' will attempt a 64bit rebuild. Some packages still have errors due to poor assumptions as to linked library locations, etc. Let the RPM maintainers know. Of note, if you need a plug-in for an existing application, you will need to make sure your plugin is the same arch as the app it is for. IE the xmms FLAC plugin would have to be 64bit as xmms is 64bit, mozilla plugins would have to be 64bit, mozplugger helpers are the exception as they are not actual plugins, but external applications called by the actual plugin, if they execute on the system, they should be able to execute as a call from mozplugger.

Can I develop for both x86_64 and i386 on the same machine?
Generally speaking, this should not be a problem just build with '-m32'. The way biarch works in theory, means that both 32bit and 64bit libs are installed concurrently (/lib and /lib64), and libtool helps to ensure that the right thing is done behind the scenes. In practice however this can get a bit messy, with some lib packages including arch specific bits in /etc or /usr/bin, resulting in rpm conflicts, and unexpected behavior. If you plan on doing a reasonable amount of biarch development, one solution I have been fairly happy with is setting up a dual boot. Once both arch are installed as listed, you can remain running in 64bit, and simply build in a chroot/setarch to your 32bit root. This also holds the advantage of having an option for playing 32bit 3D games when you need to blow off steam and 64bit versions are not available. In practice I really do not boot into 32bit mode, but the chroot does ensure I have everything I need for building 32bit packages if one of my 32bit machines are not available

Does this release support SATA?
I am pleased to say that Fedora Core 2 includes enhanced SATA support, and most controllers from Promise, Via, and Silicon Image should work for installation. Sil was not supported with FC1

What do I do if I run into issues?
As this is an official Fedora release, the best thing would be to log a ticket with Red Hat Bugzilla, but if you do, please specify x86_64 as the platform, and if you could add 64bit_fedora@comcast.net to the CC list I would appreciate it.

How do I make my eMachines m680x work with Fedora Core 2?
Unfortunately these machines do not work "out of the box" I am happy to report that Chris Kloiber has created a nice page on setting these laptops up I am currently using his kernel with success. You will want to make sure that yum updates are done with '--exclude kernel*' to avoid reverting to a non functional kernel.

How can I help?
Testing and providing feedback is of great value, individual hardware configurations vary quite a bit. Individual use patterns will not catch all bugs. Testing and providing feedback can help find bugs that are not visible with other's hardware or use patterns. Patches are appreciated as well, send 'em if you've got 'em



This page was last updated on Wednesday, May 19th, 2004
Fedora and Red Hat are registered trademarks of Red Hat Inc.