Hello community,

here is the log from the commit of package microcode_ctl for openSUSE:Factory
checked in at Tue May 10 09:15:04 CEST 2011.



--------
--- microcode_ctl/microcode_ctl.changes 2011-01-18 15:20:00.000000000 +0100
+++ /mounts/work_src_done/STABLE/microcode_ctl/microcode_ctl.changes    
2011-05-10 04:05:58.000000000 +0200
@@ -1,0 +2,6 @@
+Tue May 10 02:04:01 UTC 2011 - [email protected]
+
+- microcode.init, do not load microcode on Virtual Machines
+  ugly error messages shown in syslog otherwise.
+
+-------------------------------------------------------------------

calling whatdependson for head-i586


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ microcode_ctl.spec ++++++
--- /var/tmp/diff_new_pack.UfsFyT/_old  2011-05-10 09:14:47.000000000 +0200
+++ /var/tmp/diff_new_pack.UfsFyT/_new  2011-05-10 09:14:47.000000000 +0200
@@ -27,7 +27,7 @@
 Group:          Hardware/Other
 Summary:        Microcode Updates for Intel CPUs
 Version:        1.17
-Release:        117
+Release:        123
 Source0:        microcode_ctl-%{version}.tar.bz2
 Source1:        microcode.init
 Source2:        microcode-%{intel_version}.dat.bz2


++++++ microcode.init ++++++
--- /var/tmp/diff_new_pack.UfsFyT/_old  2011-05-10 09:14:48.000000000 +0200
+++ /var/tmp/diff_new_pack.UfsFyT/_new  2011-05-10 09:14:48.000000000 +0200
@@ -24,7 +24,12 @@
 do_start()
 {
     echo -n "Checking/updating CPU microcode "
-    if grep -q -i intel /proc/cpuinfo \
+
+    if test -x /usr/sbin/dmidecode \
+        && /usr/sbin/dmidecode -s system-product-name \
+        | grep -q -i -P "\b(?:VirtualBox|VMware|Bochs|Parallels|Qemu)\b"; then
+        rc_status -u
+    elif grep -q -i intel /proc/cpuinfo \
             && /sbin/modinfo microcode >& /dev/null; then
         /sbin/modprobe -q microcode
         /sbin/microcode_ctl -Qu


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



Remember to have fun...

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to