How to extract modern Ubuntu initramfs
Just to remember, there is an explanation here, from which the following directive can be taken:
(cpio -id; zcat | cpio -id) < /path/to/initrd.img
If you’ve ever tried to run modern versions of ssh, rsync, or other essential tools on an old Linux system, you know the pain. OpenSSL errors, OpenSSL support, or even library dependency hell. The Problem With Old Linux Systems Sometimes, you’re stuck with an old Linux system that you can’t update, and you need these…
Recently, bonding module requires IPv6 module. There are two possible solutions. The first is to define zeroconf to off, by adding the following line to /etc/sysconfig/network : NOZEROCONF=yes The other method, which actually disables IPv6 is to insert into /etc/modprobe.conf the following line: options ipv6 disable=1 That should do the trick. You will need to…
GRUB2 password protection, secure Ubuntu boot loader, prevent unauthorised boot menu changes, enhance system security. In previous posts in this blog I have explained how to protect the system by disk encryption with a password retrial from the TPM. In another post, I have given some wider overview of system security and protection, but there…
Weird behavior of my Orinoco_pci wireless network interface. On my home 802.11b network, I get performance of about 600KB/s, instead of 1.1MB/s, which should be the approximate speed to expect to. Not only that, but browsing to external websites and the likes (I compare using wget), I get speeds of <7KB/s, and sometimes decreasing to…
I have had a problem with my IBM X41 – ever since I have started using Ubuntu 7.10 (after a nice upgrade from 7.04), whenever the lid was closed, and reopened – the display would have flickered for a short while (while the lid is up) and then blank completely. My (ugly) workaround was to…
This was a tricky action. Assume I have a list of variables, obtained by an external source: var1=a var2=b var3=c I cannot use loop and in it the phrase ${var$i} (where i is the integer counter). It just doesn’t work. I used this instead to assign the values to an array: var[$i]=$(eval echo "${var${i}}") That…
This site uses Akismet to reduce spam. Learn how your comment data is processed.
I am working on Lubuntu 22.04, and either the lubuntu team creates the ramdisk differently, or the command is now out of date.
This works for me:
(cpio -id; cpio -id; zstdcat | cpio -id) < /path/to/initrd.img The ramdisk I am working with now has 2x uncompressed CPIO archives, prepending a "Z Standard" compressed main ramdisk.
They can modify it, however – how? Can you run the command ‘file’ on the initrd file? Or ‘lsinitrd’? It will give you a lot of details and insights.
In any case, on Ubuntu 22.0.4 my command works, and there is no reason to assume that this mechanism has changed. Just to be clear – your command failed on my test with the following output:
cpio: Malformed number
and
cpio: premature end of archive
Hi etzion, while I was initially confused by your response, I think I understand where the difference comes from. With my initrd I have 3 CPIO archives, the first 2 being microcode for AMD and Intel CPUs respectively – they each have their own CPIO archive. Then the third archive is the main initial ramdisk, encrypted Z standard encryption.
My ramdisk comes from the Lubuntu ISO. It is the ramdisk used to load the live environment. I assume the ramdisk you are using is for Ubuntu, installed on your computer? It would make sense to me that they would drop one of the first two microcode ramdisks, depending on what is applicable to the machine’s processor.
Thanks for your response, by the way you have some great info on your website. Thanks for what you do!
I understand. You were using the special LiveCD initrd. On systems which are on-disk, the initrd is created per the hardware configuration and layout of the system. Your note is good and important – and it exposes a structure including both microcodes as the same time, for both types of CPUs. When the system is installed on disk, it will integrate only the CPIO image for the relevant microcode. Makes a lot of sense.
I really appreciate the feedback. I have been collecting and sharing (and using it as an extended memory) for a long while. Some of it is still relevant even today 🙂
Thanks!