module load order

wombat23 · 2012-06-17 10:02:14

Since kernel 3.4 I get this error at boot time:

Errata AE18 not fixed, update BIOS or microcode of the CPU!

the microcode update module is listed in /etc/rc.conf but it is loaded *after* coretemp. How do I change the order modules get loaded?

tomk · 2012-06-17 10:05:42

modprobe.conf - read the man page for details.

wombat23 · 2012-06-17 10:34:55

Oh dear, I had not found the manpage for modprobe.conf, because it is under

man modprobe.d

Now, I get this:

Jun 17 12:34:46 localhost kernel: [    2.630305] microcode: CPU0 sig=0x6e8, pf=0x20, revision=0x0
Jun 17 12:34:46 localhost kernel: [    2.801118] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU!
Jun 17 12:34:46 localhost kernel: [    2.801202] coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU!
Jun 17 12:34:46 localhost kernel: [    2.853903] microcode: CPU0 updated to revision 0x39, date = 2005-11-15
Jun 17 12:34:46 localhost kernel: [    2.853919] microcode: CPU1 sig=0x6e8, pf=0x20, revision=0x0
Jun 17 12:34:46 localhost kernel: [    2.869176] microcode: CPU1 updated to revision 0x39, date = 2005-11-15
Jun 17 12:34:46 localhost kernel: [    2.869245] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

not quite solved...

Last edited by wombat23 (2012-06-17 10:38:31)

tomk · 2012-06-17 11:00:51

The only conclusion I can draw from that is that you read the man page. What did you actually do to make this attempt any better than your last attempt?

wombat23 · 2012-06-17 15:45:24

I'm sorry, I made microcode load before coretemp:

softdep coretemp pre: microcode

in modprobe.conf
which seems to work, but coretemp starts at 2.8, at which time microcode is not yet updated (2.85) obviously

tomk · 2012-06-17 19:46:26

OK.. I had forgotten about 'softdep', I was thinking of the 'install' directive. There's an example in the man page about fred and barney, see if that works any better.

falconindy · 2012-06-17 20:07:24

Softdeps are preferred for this sort of thing. An install directive is going to accomplish the same, just less eloquently. The problem is likely that you can't, in userspace, know when a module has finished its initialization. modprobe only blocks and waits for module_init() to return, which isn't necessarily the same.

Arch Linux

#1 2012-06-17 10:02:14

module load order

#2 2012-06-17 10:05:42

Re: module load order

#3 2012-06-17 10:34:55

Re: module load order

#4 2012-06-17 11:00:51

Re: module load order

#5 2012-06-17 15:45:24

Re: module load order

#6 2012-06-17 19:46:26

Re: module load order

#7 2012-06-17 20:07:24

Re: module load order

Board footer