You are not logged in.
Pages: 1
I have recently (after an update) commenced receiving the message on boot that the module microcode is missing.
EDIT: The actual message is
module microcode not found in modules.dep
The is the first message after boot, before systemd has commenced its fsck'ing (so so speak).
Is this at all meaningful?
I am running an intel core i5 and I am not at all sure what information you may need that will be helpful.
I have noticed that intel-microcode is installed, but so is amd64-microcode.
I am assuming that they would not interfere with each other (if only because I didn't manually install either of these packages.)
Any suggestions? What information do you need?
Last edited by dhalgren (2016-04-05 23:35:20)
Offline
hmm amd64 microcode was indeed recently updated in the 8.4.
output of
dmesg | grep microcode
and
apt-cache policy amd64-microcode
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
bruce@debian:~$ dmesg | grep microcode
[ 0.000000] microcode: CPU0 microcode updated early to revision 0x1c, date = 2015-02-26
[ 0.103096] microcode: CPU1 microcode updated early to revision 0x1c, date = 2015-02-26
[ 1.154018] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x1c
[ 1.154033] microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x1c
[ 1.154057] microcode: CPU2 sig=0x306a9, pf=0x10, revision=0x1c
[ 1.154079] microcode: CPU3 sig=0x306a9, pf=0x10, revision=0x1c
[ 1.154219] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
and
bruce@debian:~$ apt-cache policy amd64-microcode
amd64-microcode:
Installed: 2.20160316.1~deb8u1
Candidate: 2.20160316.1~deb8u1
Version table:
*** 2.20160316.1~deb8u1 0
500 http://ftp.us.debian.org/debian/ jessie/non-free amd64 Packages
100 /var/lib/dpkg/status
Offline
module microcode not found in modules.dep
I think it's a bug in the intel-microcode package.
See https://bugs.debian.org/cgi-bin/bugrepo … bug=814301
I see the same message on my AMD laptop running Debian jessie but everything seems to work fine.
Which kernel are you using?
uname -a
Offline
Ah, now that didn't appear in the first few pages of the searches I did before posting here, or I wouldn't have asked the question. Yes, indeed, I am running the kernel with the problem.
Linux debian 4.4.0-0.bpo.1-amd64 #1 SMP Debian 4.4.6-1~bpo8+1 (2016-03-20) x86_64 GNU/Linux
Something in the upgrade also appears to have broken amule, which worked perfectly prior to the upgrade, but now crashes with a segfault.Ah well...
Offline
I am running the kernel with the problem
Does the system work normally if you boot with the stock jessie kernel?
Offline
Does the system work normally if you boot with the stock jessie kernel?
Ok, this is where you find out just how little I know. How do I boot with the stock jessie kernel?
Once I know how to do that, I'll let you know.
Offline
Show us which kernel packages you have installed.
Here is mine:
dpkg -l | grep linux-image
ii linux-image-3.16.0-4-amd64 3.16.7-ckt25-1 amd64 Linux 3.16 for 64-bit PCs
ii linux-image-amd64 3.16+63 amd64 Linux for 64-bit PCs (meta-package)
/h/me
The first one listed is the stock jessie kernel.
The second one is the kernel metapackage.
With that info you can check /boot/grub/grub.cfg if it - the stock jessie kernel - is in your grub menu. Or you can reboot and see if it is listed in the grub boot menu.
Offline
How do I boot with the stock jessie kernel?
It should be in the "Advanced Options" GRUB sub-menu -- you can press "e" with an entry highlighted to see the name of the kernel image being booted
Offline
@HoaS
Got it, and done. Generally speaking, everything is now working much better, with the older kernel,and no messages about missing microcode. When I say everything is working much better, I mean simple matters, such as: iceweasel loads more quickly, and various other things I do are smoother and quicker. (Mind you, I don't do much except write and edit photos.)
It hasn't helped amule, but I didn't expect it to do so, as libwxgtk was updated, and amule was compiled against an earlier version. I now have both versions, but admit that I am unsure as to whether or not I should uninstall the update ...
I used to be much more courageous about these matters, and I used to know simple things like how to boot a different kernel, but after years of not having to do any of this, all the knowledge has faded away until I am reminded.
Anyway, thank you, problem solved. I'll just boot the standard kernel until there is another update, and then I shall see what happens.
Offline
dhalgren wrote:How do I boot with the stock jessie kernel?
It should be in the "Advanced Options" GRUB sub-menu --
This can be changed right HoaS? If you edit the /etc/grub.d/ directory with a numbered boot entry? Or will it still show up only under the advanced menu?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
@HB -- erm, I'm not sure TBH.
:8
I only use GRUB as a fallback bootloader and I write my own grub.cfg © so I would have to refer you to TFM:
https://www.gnu.org/software/grub/manual/grub.html
The default entry can certainly be changed and with the timeout set to zero who would know the difference?
Offline
@HB -- erm, I'm not sure TBH.
:8I only use GRUB as a fallback bootloader and I write my own grub.cfg © so I would have to refer you to TFM:
https://www.gnu.org/software/grub/manual/grub.htmlThe default entry can certainly be changed and with the timeout set to zero who would know the difference?
Not to get off track, but thanks for this HoaS... I point anyone needing to know about the BIOS to MBR/GPT to GRUB relationship to this specific page of that link you provided:
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
Pages: 1