Bug 129437 - I need to change install arch for amd 1800 system
Summary: I need to change install arch for amd 1800 system
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 1
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-09 03:01 UTC by jzeiger
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-10 19:49:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jzeiger 2004-08-09 03:01:17 UTC
Description of problem:
The installer thinks my amd 1800 duron system is an athlon.  After
install, the system is very unstable and experiences frequent
segmentation errors in a wide variety program.  I was able to fix this
problem on rh9 a while back by installing a 586 kernel instead of the
default one.

Two questions:  

Is there a way I can override/specify the install architecture on a
fedora core install? 

On an already installed FC1/FC2 system is there a way to override the
 install architecture so that when I upgrade the kernel (and other
platform specific packages) with up2date/apt/yum, i586 will be used
instead of athalon. Is it as simple as changing /etc/rpm/platform from
athlon-redhat-linux to i586-redhat-linux?

Version-Release number of selected component (if applicable):

How reproducible:
easy.  problem intermittent but occurs approximately once every 5
minutes using gnome or kde file managers navigating through
directories.  Other programs as well. doesn't occur using terminal. 
Occurs everytime doing kernel build. some services also have problems
(not as frequently).

Steps to Reproduce: see above
  
Actual results:


Expected results:


Additional info:

Comment 1 Jeremy Katz 2004-08-10 19:49:02 UTC
Yes, you can change /etc/rpm/platform like that.  Note that you
probably want to look more closely at your hardware, though, as this
is usually caused by bad hardware.


Note You need to log in before you can comment on or make changes to this bug.