Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 476208 - sys-apps/microcode-ctl version bump request
Summary: sys-apps/microcode-ctl version bump request
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-08 17:57 UTC by Pacho Ramos
Modified: 2013-09-14 22:56 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pacho Ramos gentoo-dev 2013-07-08 17:57:47 UTC
https://fedorahosted.org/microcode_ctl/

Looks to be a 2.0_3 release... not sure if still needed, microcode kernel module is supposed to load the firmware, but I remember I needed to run it :|

Reproducible: Always
Comment 1 Markos Chandras (RETIRED) gentoo-dev 2013-09-14 16:25:12 UTC
I am not sure what's the difference between 1.23 and 2.1.2.
Comment 2 Pacho Ramos gentoo-dev 2013-09-14 16:30:18 UTC
Yeah, I had a similar problem. Anyway, it doesn't seem to be really needed -> what you need to do is to compile the microcode stuff as a module (not *into* the kernel) and, then, it will load the microcode
Comment 3 Markos Chandras (RETIRED) gentoo-dev 2013-09-14 16:40:47 UTC
What's wrong with compiling the microcode in the kernel? the AMD wiki page suggests otherwise.

I bumped it to 1.23 anyway
Comment 4 Markos Chandras (RETIRED) gentoo-dev 2013-09-14 16:52:26 UTC
(In reply to Markos Chandras from comment #3)
> What's wrong with compiling the microcode in the kernel? the AMD wiki page
> suggests otherwise.
> 
> I bumped it to 1.23 anyway

The init script will only load the module if the /dev/cpu/microcode device is not present which can only happen if the microcode support was built in the kernel. In any case, it does not make much difference. Lets close this bug for now unless of course you want to investigate what v2.1.2 is for :)
Comment 5 Pacho Ramos gentoo-dev 2013-09-14 20:50:24 UTC
I can simply remove microcode-ctl if I build it as a module because, that way, the module will load the proper microcode when it's loaded. On the other hand, if I build microcode built in the kernel, it won't load the updated microcode ever :(
Comment 6 Markos Chandras (RETIRED) gentoo-dev 2013-09-14 22:56:37 UTC
(In reply to Pacho Ramos from comment #5)
> I can simply remove microcode-ctl if I build it as a module because, that
> way, the module will load the proper microcode when it's loaded. On the
> other hand, if I build microcode built in the kernel, it won't load the
> updated microcode ever :(

ah you mean because the firmware will be built-in in the kernel as well. Yes, I was referring to the /dev/cpu/microcode code which can be either be a module or built-in not to the actual microcode-data. Yes, in that case you need to use microcode_ctl but i see no problem with that.