Bug 12537 - Core 153 next/6cab8977: modprobe: FATAL: Module microcode not found in directory /lib/modules/4.14.198-ipfire
Summary: Core 153 next/6cab8977: modprobe: FATAL: Module microcode not found in direct...
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - - Unknown -
Assignee: Michael Tremer
QA Contact: Peter Müller
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-20 15:52 UTC by Peter Müller
Modified: 2020-12-22 10:22 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Müller 2020-11-20 15:52:57 UTC 
While upgrading to the "next" version of Core Update 153 (next/6cab8977, see below), the error message above came to my eyes while watching the update log file:

[root@maverick ~]# tail -f /opt/pakfire/logs/update-core-upgrade-153.log
[... irrelevant log lines omitted ...]
Generating grub configuration file ...
Found background: /boot/grub/splash.png
Found linux image: /boot/vmlinuz-4.14.207-ipfire
Found initrd image: /boot/initramfs-4.14.207-ipfire.img
done
modprobe: FATAL: Module microcode not found in directory /lib/modules/4.14.198-ipfire

[root@maverick ~]# cat /etc/os-release 
NAME="IPFire"
VERSION="2.25"
ID=ipfire
VERSION_ID=2
PRETTY_NAME="IPFire 2.25 (x86_64) - core153 Development Build: next/6cab8977"
ANSI_COLOR="0:31"

This raises two questions from my point of view:

(a) Should this (looking for a module in the 4.14.198 directory for kernel 4.14.207) happen? If yes, why?
(b) Why are we writing this log file into /opt/, and not into /var/log/?