intel-microcode initramfs-tools hooks mangle initramfs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
As per summery, I've been trying to get iniitramfs-tools to behave properly on Ubuntu 16.04 for hours and after process of elimination I've found that it's the intel-microcode hooks which are causing problems with update-initramfs, it basically leaves everything else but the microcode update binary and leaves out everything else and causes it to ignore the initramfs compression settings. If you need any more information or logs, please let me know.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2016-06-29 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
MachineType: ASUS All Series
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.157.1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/28/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3003
dmi.board.
dmi.board.name: MAXIMUS VII GENE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: All Series
dmi.product.
dmi.sys.vendor: ASUS
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1597762
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.