intel-microcode not included 20.04 initrd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debian-installer (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
We have several factory-fresh Mitac industrial motherboards (https:/
```
[0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later)
[0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/
```
Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04.
The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place.
I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet).
I have tried the following to modify the Ubuntu Server ISO, without success:
1- Adding the microcode to initrd
-------
I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https:/
2- Using initrd from Ubuntu Desktop 18.04.5
-------
I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again.
The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session.
At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it.
If you need any additional information/
Thanks!
affects: | linux (Ubuntu) → ubuntu-meta (Ubuntu) |
tags: | added: rls-ii-incoming |
tags: | added: fr-1551 |
tags: | removed: rls-ii-incoming |
affects: | ubuntu-meta (Ubuntu) → debian-installer (Ubuntu) |
summary: |
- Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata + intel-microcode not included 20.04 initrd |
Changed in debian-installer (Ubuntu Focal): | |
milestone: | none → ubuntu-20.04.4 |
Changed in debian-installer (Ubuntu Focal): | |
milestone: | ubuntu-20.04.4 → none |
status: | New → Won't Fix |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1938588/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]