Red Hat Bugzilla – Bug 186378
FC5 clean install fails on Transmeta Crusoe processor system
Last modified: 2008-03-10 22:38:40 EDT
Description of problem:
I have FC4 installed on my Fujitsu P2120 notebook with Transmeta Crusoe
processor. However, upgrading to FC5 was not possible due to insufficient disk
space. Subsequently I performed a clean install of FC5.
Version-Release number of selected component (if applicable):
FC5 i386 installer CD
Steps to Reproduce:
1. Clean install of FC5 i386 architecture
2. Go through installation dialogs, start installation process
3. Anaconda will crash with "Error running transaction: package *** is intended
for a i686 architecture" error
Anaconda will crash with "Error running transaction: package *** is intended for
a i686 architecture" error (3 packages are listed in the error: kernel is one)
Able to clean install FC5 (with i686 kernel package) on Transmeta Crusoe
FC4 installer works fine, will clean install FC4 and kernel*i686.rpm correctly.
Finally I ended up doing a clean reinstall of FC4, and performed an upgrade
using FC5 install disc and it proceeded without crashing.
If you switch to tty3 can you cat /etc/rpm/platform please
*** Bug 189865 has been marked as a duplicate of this bug. ***
I've replicated here and can see what is going on.
*** Bug 188417 has been marked as a duplicate of this bug. ***
Sorry to nag, but is there any progress on this issue? I understand shipping an
actual boot errata will take time, but if there's a rawhide/testing boot kernel,
anaconda package or patch I can apply to just get this one laptop installed it
would be helpful. Thanks in advance
This is in one of the duplicate bugs, but I wanted to make sure it was noticed:
on my machines, the i586 kernel installs when the i686 or i686-smp kernel should
be installed. Five installs so far, all with this issue. I am capable of
patching anaconda and rebuilding the boot media if it would help in testing; I
just don't know where to look.
*** Bug 190829 has been marked as a duplicate of this bug. ***
> Comment #4 From Paul Nasrat (email@example.com) on 2006-04-25 10:09 EST
> I've replicated here and can see what is going on.
Any progress on this? I've encountered this bug as well (Fujitsu Lifebook
P2120, Transmeta Crusoe TM5800 CPU), and it's keeping me from installing Fedora
Core 5. I'd be happy to make a new installation CD if necessary. Even a dirty
workaround for Transmeta users would be useful in the interim....
I'm hoping to fix this for FC6 - however I'm working on larger anaconda changes
first (eg multiple repository support).
An upntested work around may be when the installer boots up and is on the
welcome screen switch to tty2 and mkdir -p /mnt/sysimage/etc/rpm and then echo
i686-redhat-linux > /mnt/sysimage/etc/rpm/platform. If you have time to try
that out, and let me know if it works for you. I can probably provide an
updates.img to do the same.
I'm reluctant to reformat my FC5 install to test this. Perhaps one of the other
interested parties who haven't installed FC5 yet can try this.
I'd be happy to test; probably won't get to it until early morning on 2006-05-11
I also have a Fujitsu P2120. I tried switching to tty2 from the welcome screen,
# mkdir -p /mnt/sysimage/etc/rpm
# echo i686-redhat-linux > /mnt/sysimage/etc/rpm/platform
I then did:
# cat /mnt/sysimage/etc/rpm/platform
to make sure everything looked okay. It did. However, when I tried to switch
back to tty7 where the installer was running, everything locked solid with a
blank screen. I was unable to switch back to any other tty (1-5), nor did the
three-finger salute reboot the system. I retried several times, including
switching from tty7 to tty1 and tty2 a few times before making the platform
file. After making the file, I can freely switch between any of the text ttys,
but as soon as I return to the graphical installer, it freezes with a black screen.
Perhaps tonight I'll trying doing a text-based install.
I see this same problem on my Sony Picturebook with the Crusoe processor.
the file /mnt/sysimage/etc/rpm/platform already contains the string
i686-redhat-linux so the cpu seems to be detected correctly.
To get FC5 going I had to install a clean FC4 minimal setup and do a yum
I see the same freezing behavior and reported this as bug 191887.
The proposed workaround does not work. First of all /mnt/sysimage is
not even mounted till just before the packages start installing. So
doing what you propose above will be "overmounted" anyway. Also, once
I get the 'incorrect arch' error, I can go to tty2 and look at the
/mnt/sysimage/etc/rpm/platform file and it has i686-redhat-linux
in it anyway.
However, I found a workaround. At the welcome screen, to to tty2
and change /etc/rpm/platform to read 'i586-redhat-linux'.
Then later, when it is transferring the install image to your / partition
quickly go to tty2 and change /mnt/sysimage/etc/rpm/platform to
Then it seems to install okay (thought it is still going now and
has not rebooted yet)
Can you attach /proc/cpuinfo from the machine.
You should also be able to install with passing rpmarch=i586 to the syslinux
> linux rpmarch=i586
great! this solved my problems.
Here's the cpuinfo on my box:
processor : 0
vendor_id : GenuineTMx86
cpu family : 6
model : 4
model name : Transmeta(tm) Crusoe(tm) Processor TM5800
stepping : 3
cpu MHz : 867.000
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr cx8 cmov mmx longrun lrti
bogomips : 1724.49
This bug is STILL PRESENT in FC6
I am testing if the rpmarch=i586 workaround works now, but since it has already
vapourised my machine it'll be a little while before I can update. In addition,
it is not exactly easy to test that workaround on PXE installs.
rpmarch=i586 still works as a workaround for FC6
F7 anaconda appears to work correctly on P2120. However, there are other issues
with respect to actually getting the installed F7 distribution booted, which is
tracked under https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242472
This issue should be closed since it has a workaround in F6 and solved in F7.
The pata_ali IDE kernel panic Bug #242472 has been solved with post-F7 updated
User firstname.lastname@example.org's account has been closed