Red Hat Bugzilla – Bug 458419
Completely Unuseable with AMD 64 +3000, ECS Motherboard
Last modified: 2010-12-07 13:42:00 EST
Description of problem:
Unstable, unresponsive, inconsistent loading of KDE. Unworkable distro out of the box. CD-ROM runs constantly, KDE does not come up or when and if it does, tried 3 different times, it is unresponsive.
Version-Release number of selected component (if applicable):Rawhide 64bit
How reproducible: ECS Socket 754 Motherboard, AMD64 +3000, 512 ram
Steps to Reproduce:
1.Boot From CD
2.Try toBring up KDE
Actual results: After a very long time, I got KDE up once, Konqueror would start to load and then disappear. Screen froze once.
Expected results: A working distro !
Additional info: Machine runs Live Ubuntu 64 very quickly w /some problems. Machine also runs PCLinuxOS 2007 and Puppy Linux quite well.
As Rex is fond of saying "Rawhide" eats babies and kills kittens so use it at your own risk. Do you have any issues running Fedora 9 on this box? Keep in mind Rawhide is constanly changing and has not yet even reached beta.
I've noticed that the platform is listed as ia64, but the processor you are using is an AMD64/EM64T. Is this a typo? Because IA64 should NOT boot on an AMD64/EM64T processor.
firstname.lastname@example.org did you verify your platform, if so is this still and issue. Please respond within 30 days or this will get closed as INSUFFICIENT DATA.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem.
Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.
Thank you in advance.