Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 118001 - failure to update IA32 microcode on boot
Summary: failure to update IA32 microcode on boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-utils
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: FC2Target FC3Target FC4Target
TreeView+ depends on / blocked
 
Reported: 2004-03-10 22:27 UTC by Patrick Oberli
Modified: 2015-01-04 22:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-01-18 20:52:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Patrick Oberli 2004-03-10 22:27:14 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; 
Q312461; .NET CLR 1.0.3705; .NET CLR 1.1.4322)

Description of problem:
Hi

I get the message:

Applying Intel IA32 Microcode update:                      [FAILED]

while I boot Fedora Core 2 test1.
I've seen in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?
id=71918 that you've allready once fixed this message, but now it 
appears again. 
I have a Celeron 4 2,4GHz in use on this pc.

As far I've read this doesn't really affect system performance, but 
it's quite confusing for beginners.

pato

Version-Release number of selected component (if applicable):
kernel-utils-2.4-9.1.115

How reproducible:
Always

Steps to Reproduce:
1. boot
    

Actual Results:  I got the failure message mentioned above.

Expected Results:  Don't get this message, or get a [OK].

Additional info:
Comment 1 Dave Jones 2004-10-26 03:09:16 UTC 
did this get fixed in an update ?
Note You need to log in before you can comment on or make changes to this bug.