| View previous topic :: View next topic |
| Author |
Message |
peshwengi
n00b
Joined: 01 Aug 2003
Posts: 66
Location: London, UK
|
 Posted: Mon Feb 23, 2004 3:24 pm Post subject: microcode_ctl error |
 |
|
Hello,
I am having a strange problem with microcode_ctl. If I run it by hand:
| Code: | | microcode_ctl -iud /dev/microcode |
it works fine, but if I run it in the init script (modified slightly to point to the correct files):
| Code: | start() {
ebegin "Updating Intel Microcode"
if [ -f "/dev/misc/microcode" ]
then
microcode_ctl -iu -d /dev/misc/microcode
eend $? "Failed to update microcode"
else
eend 1 "/dev/misc/microcode not found! Please check your kernel config."
fi
}
|
Then it comes back with
| Code: |
* /dev/microcode not found! Please check your kernel config. [ !! ]
|
Any ideas anyone? |
|
| Back to top |
|
 |
mirekm
Apprentice
Joined: 12 Feb 2004
Posts: 219
Location: Gliwice
|
| Posted: Mon Feb 23, 2004 11:05 pm Post subject: |
|
|
Try to change in ini script from :
| Code: |
start() {
ebegin "Updating Intel Microcode"
if [ -f "/dev/misc/microcode" ]
then
|
to:
| Code: |
start() {
ebegin "Updating Intel Microcode"
if [ -e "/dev/misc/microcode" ]
then
|
|
|
| Back to top |
|
|
peshwengi
n00b
Joined: 01 Aug 2003
Posts: 66
Location: London, UK
|
| Posted: Tue Feb 24, 2004 10:16 am Post subject: |
|
|
Thanks, that worked great!
Having now read through the bash docs to find out why, I understand it now. Would you say this is an error in the script? |
|
| Back to top |
|
|
BikingDuck2
n00b
Joined: 13 Apr 2003
Posts: 4
Location: Southeast US
|
| Posted: Wed Apr 21, 2004 4:04 am Post subject: not fixed yet? |
|
|
Not sure if any of the developers know about this or not...maybe this will get somebody's attention.
I am running linux 2.6 w/ udev and I had to modify the init script to make this work (just like peshwengi had to). I'm not sure if this device relocation is a result of 2.6 or udev. If anybody knows, I'll be happy to make a patch to the init script and submit it  |
|
| Back to top |
|
|
MickKi
Veteran
Joined: 08 Feb 2004
Posts: 1179
|
| Posted: Sat Jul 24, 2004 5:43 pm Post subject: |
|
|
Hi All,
I can see that the script has been patched in the latest version, but this is what I'm getting: | Code: | # microcode_ctl -iud /dev/microcode
microcode_ctl: writing microcode (length: 141312)
microcode_ctl: cannot open /dev/microcode for writing errno=21 (Is a directory) |
I'm sure that there must be a simple answer to this, which I do not yet know . . .
Can you please help!
PS. I'm running 2.6.7-gentoo-r11, on a PIII Coppermine.
_________________
Regards,
Mick |
|
| Back to top |
|
|
MickKi
Veteran
Joined: 08 Feb 2004
Posts: 1179
|
| Posted: Wed Jul 28, 2004 6:52 pm Post subject: |
|
|
Hi All,
Thanks to the helpful suggestions I received off line from mrekm and BikingDuck2 I have made some progress, but like my understanding it is rather limited. I ran: | Code: | # rm -R /dev/microcode
# mknod /dev/microcode c 10 184
# microcode_ctl -iu
microcode_ctl: writing microcode (length: 141312)
microcode_ctl: cannot open /dev/cpu/microcode for writing errno=2 (No such file or directory)
# microcode_ctl -iud /dev/microcode
microcode_ctl: writing microcode (length: 141312)
microcode_ctl: microcode successfuly written to /dev/microcode
microcode_ctl: microcode buffers released |
Good stuff! Then to make sure that it reloads when I boot: | Code: | | rc-update add microcode_ctl default |
To test that it works: | Code: | # /etc/init.d/microcode_ctl restart
* Updating Intel Microcode...
microcode_ctl: writing microcode (length: 141312)
microcode_ctl: microcode successfuly written to /dev/microcode
microcode_ctl: microcode buffers released [ ok ] |
However, as soon as I reboot the same old problem comes up: | Code: | * Updating Intel Microcode
microcode_ctl: writing microcode (length: 141314)
microcode_ctl: cannot open /dev/microcode for writing errno=21 (Is directory)
* Failed to update microcode [!!] |
It seems to me that when the kernel boots up it creates /dev/microcode as a directory and thereafter the microcode_ctl utility cannot write to it 
I have no idea how to fix it. Any suggestions please?
_________________
Regards,
Mick |
|
| Back to top |
|
|
MickKi
Veteran
Joined: 08 Feb 2004
Posts: 1179
|
| Posted: Fri Jul 30, 2004 10:57 am Post subject: |
|
|
Hi All,
Am I the only 2.6.7-gentoo-r11 user who's having trouble with microcode_ctl?
Would anyone know which process/script at bootup overwrites the node I create under /dev/microcode? (see previous post)
Any ideas please?
_________________
Regards,
Mick |
|
| Back to top |
|
|
MickKi
Veteran
Joined: 08 Feb 2004
Posts: 1179
|
| Posted: Sat Aug 07, 2004 7:33 pm Post subject: |
|
|
FIXED!
Thank goodness! I managed to fix it by accident: I switched to using udev instead of devfs and now it loads nicely and updates without any problems. 
That said, I wouldn't know how to make it work with devfs. 
_________________
Regards,
Mick |
|
| Back to top |
|
|
Chris-P
n00b
Joined: 30 Jan 2004
Posts: 62
Location: South West United Kingdom
|
| Posted: Mon Sep 20, 2004 6:34 pm Post subject: |
|
|
| MickKi wrote: | | ... That said, I wouldn't know how to make it work with devfs. |
I had the same error as the original poster, the way I got it to work with devfs was by editing the /etc/conf.d/microcode_ctl file. The original - after the emerge - read:
| Code: | | MICROCODE_DEV="/dev/microcode" |
Which I changed to:
| Code: | | MICROCODE_DEV="/dev/cpu/microcode" |
That solved the problem! |
|
| Back to top |
|
|
sysprog
n00b
Joined: 13 Sep 2004
Posts: 2
|
| Posted: Sun Oct 31, 2004 11:56 pm Post subject: |
|
|
Chris-P, I have the same problem and I had already used the same fix as you:
| Code: | | MICROCODE_DEV="/dev/cpu/microcode" |
However, even the latest updates (as of just a couple of days ago), still ship with config files that point to "/dev/microcode".
I'm wondering if this is a kernel 2.4 vs. kernel 2.6 issue? And what would be the appropriate group to post the bug to (assuming, of course, that it's actually a bug)? I usually cheat in this regard by finding what groups previously handled bugs for a particular package, but in this case there are none...
-Mike |
|
| Back to top |
|
|
MickKi
Veteran
Joined: 08 Feb 2004
Posts: 1179
|
| Posted: Mon Nov 01, 2004 7:39 am Post subject: |
|
|
I don't seem to be getting this error anymore - so I assume that latest updates fixed it? However, upon bootup I do not get the old verbose message like: | Code: | microcode_ctl: writing microcode (length: 141312)
microcode_ctl: microcode successfuly written to /dev/microcode
microcode_ctl: microcode buffers released |
but just get: | Code: | | * Updating microcode ... [ ok ] |
So I assume that all is fine?
_________________
Regards,
Mick |
|
| Back to top |
|
|
|
Kernel & Hardware
