Red Hat Bugzilla – Bug 55424
Install results in unbootable system on Athlon Thunderbirds
Last modified: 2007-04-18 12:37:54 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (X11; U; Linux 2.2.17 alpha)
Description of problem:
During the install, anaconda apparently attempts to figure out what
processor is in use. For Athlon systems, it installs the Athlon kernel.
The problem is that kernels optimized for Athlon DO NOT WORK on recent
Athlons, in kernel versions earlier than ~ 2.4.12. Since Enigma uses 2.4.7
or 2.4.9 and installs ONLY the athlon kernel, installation completes with
no bootable kernel. This has been known for months, and is not exactly a
Two fixes should be made: anaconda should NOT install the athlon-optimized
kernel on recent Athlons (don't know which ones), and regardless of the
processor in use, anaconda should ALWAYS install a known-good failsafe
kernel (i.e. i386 optimizations.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install RH 7.2 on an Athlon (Thunderbird.)
Actual Results: System doesn't boot. Various random kernel panics.
Expected Results: System should have booted.
I have personally verified that Linux 2.4.10 and earlier fail on 1.33GHz
and 1.2GHz Athlon (Thunderbirds; it doesn't happen with Durons and older
Athlons (< 1GHz?)). This happens even with RH 7.1, if you build your own
kernel with Athlon optimizations. I am now left with an unbootable
system; I can't even reinstall 7.2 fresh (this was an upgrade) because
it'll just crash again.
In this case, I was able to boot off the rescue CD (good thing that came
back), and manually extract the i386 kernel via rpm2cpio. I installed it
manually, and was able to boot. However, I am writing a book on Linux
systems; most casual users are not. This would have been a showstopper
for most people.
katzj, anaconda doesn't do any detection for Athlon that I'm aware of. Should
this problem be reassigned to the kernel?
morrildl, can you try booting the install with 'linux noathlon'? Does that help?
Closing due to inactivity. Please reopen if you have more information.