Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 123831 - VIA C3 (Ezra-T core) crashes on install.
VIA C3 (Ezra-T core) crashes on install.
Status: CLOSED DUPLICATE of bug 123935
Product: Fedora
Classification: Fedora
Component: distribution (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2004-05-20 16:54 EDT by John Eckerdal
Modified: 2014-03-16 22:45 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:03:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Eckerdal 2004-05-20 16:54:29 EDT
From Bugzilla Helper:
User-Agent: Opera/7.50 (X11; Linux i686; U)  [en]

Description of problem:
When trying to install Fedora Core 2 on a VIA C3 CPU (Mini-ITX board) 
the install will reboot the system just after this:

loading vmlinuz......
loading initrd.img.............


I have also tried various boot options but all it always fails in the 
same way.

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

How reproducible:

Steps to Reproduce:
1. At install screen, press Enter
2. Reboot

Actual Results:  Reboot

Expected Results:  The install should continue.

Additional info:

CPU information:
vendor_id       : CentaurHauls
cpu family      : 6
model           : 7
model name      : VIA Ezra
stepping        : 8
cpu MHz         : 800.091
Comment 1 Bert Van Cleemput 2004-05-21 13:23:25 EDT
I've the very same problem. Same hardware. Also tried some different
boot-options. But all had the same problem.
Comment 2 Alan Cox 2004-05-21 19:05:58 EDT

*** This bug has been marked as a duplicate of 123935 ***
Comment 3 Red Hat Bugzilla 2006-02-21 14:03:23 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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