microcode_ctl vs udev
Hi...
I have a little problem with microcode_ctl and udev. Mandrake 10.1 Cooker has switched fully to udev, and microcode_ctl fails to open the 'microcode' device.
It looks like udev creates /dev/microcode, but microcode_ctl looks for /dev/cpu/microcode.
Which is the right location ?
Versions:
werewolf:~# rpm -q udev microcode_ctl udev-030-10mdk microcode_ctl-1.08-1mdk
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.1 (Beta 1) for i586
Linux 2.6.8.1 (gcc 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) #1
Quoted 4 lines · J.A. Magallon
It looks like udev creates
/dev/microcode, butmicrocode_ctllooks for/dev/cpu/microcode.Which is the right location ?
/dev/cpu/microcode according to the LANANA registration table
Quoted 8 lines · Alan Cox
Quoted 4 lines · J.A. Magallon
It looks like udev creates
/dev/microcode, butmicrocode_ctllooks for/dev/cpu/microcode.Which is the right location ?
/dev/cpu/microcodeaccording to the LANANA registration table
I solved this with a rule in rules.d:
KERNEL="microcode", NAME="cpu/microcode"
But where is the default ? Kernel or userspace ? And why is it not created in the right place ?
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.1 (Beta 1) for i586
Linux 2.6.8.1-mm2 (gcc 3.4.1 (Mandrakelinux (Alpha 3.4.1-3mdk)) #3