Your message dated Sat, 6 Aug 2016 22:45:41 -0400
with message-id <20160807024541.GB8317@solydxk>
and subject line Re: Bug#829378: intel-microcode initramfs hook needs to be 
updated
has caused the Debian Bug report #829378,
regarding intel-microcode initramfs hook needs to be updated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
829378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829378
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: intel-microcode
Version: 3.20151106.1~deb8u1

When booting, the error:

    modprobe: "module microcode not found in modules.dep"

is printed to the screen.  If plymouth splash is being used, the
splash screen is dropped to display this error.

I believe that this behaviour began in linux >= 4.0, because if I
remember correctly, that was when the microcode module ceased to be a
module and became a boolean disabled|built-in.  Would it be sufficient
to delete L115-to-L123 in
/usr/share/initramfs-tools/hooks/intel_microcode?

If this behaviour is not present in the version in jessie-backport, or
the version in sid, please close this bug with "fixed in version" and
additionally refer me to the location of the documentation that needs
to be updated to prevent further bug reports such as these.  I would
write a line like:

"If you are running linux <= 4.0, which includes linux-image from
jessie-backports, please use intel-microcode from jessie-backports,
because linux-4.0 changed the default microcode loading behaviour."

Thank you,
Nicholas

--- End Message ---
--- Begin Message ---
Control: fixed -1 intel-microcode/3.20160714.1~bpo8+1

Closing because this has been fixed :-)

Thank you,
Nicholas

--- End Message ---

Reply via email to