Bug 144915 - don't know how to make device "cpu/microcode"
Summary: don't know how to make device "cpu/microcode"
Keywords:
Status: CLOSED DUPLICATE of bug 63928
Alias: None
Product: Fedora
Classification: Fedora
Component: MAKEDEV
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-12 18:34 UTC by Bernard Johnson
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:07:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bernard Johnson 2005-01-12 18:34:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
When starting, udev prints out:

Starting udev:  don't know how to make device "cpu/microcode"

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

How reproducible:
Always

Steps to Reproduce:
1. Boot system
2.
3.
    

Actual Results:  Starting udev:  don't know how to make device
"cpu/microcode"

Expected Results:  No extraneous messages

Additional info:

Seems to have no adverse effects

Comment 1 Mickey Stein 2005-01-12 19:27:05 UTC
I just noticed this as well. Bug search brought me to this one:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=63928

Where I commented on a possible solution. 

It's an older bug report about microcode being split into multiple cpu
paths in /dev/cpu/$i/microcode and might explain this particular problem. 

The only part I'm not sure I get is how in bug 63928, a new
microcode_ctl package is mentioned and in fact, is out, but that the
same init.d files are in initscripts, which would overwrite them
(unless I've missed something that is occuring in rawhide, which is
absolultely likely ;) )  Seems as if the microcode files should be in
one package or the other.

Comment 2 Michal Jaegermann 2005-01-13 19:13:06 UTC
This is not limited to x86 architectures.  I see the same on x86_64.

Comment 3 Harald Hoyer 2005-01-20 16:17:28 UTC

*** This bug has been marked as a duplicate of 63928 ***

Comment 4 Red Hat Bugzilla 2006-02-21 19:07:54 UTC
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.