While investigating a problem, I decided to look in my initramfs to see what modules it loaded.
There ain't anything there any longer! How does this stuff work these days?
[root@tomh boot]# cpio -it < initramfs-5.3.7-200.fc30.x86_64.img . early_cpio kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/GenuineIntel.bin 26 blocks
That early_cpio file is a text file with nothing but a line that says "1" in it.
There used to be kernel modules and scripts and stuff. I'm so confused now.
Tom Horsley, 01.11.19, 18:47 CET:
While investigating a problem, I decided to look in my initramfs to see what modules it loaded.
There ain't anything there any longer! How does this stuff work these days?
[root@tomh boot]# cpio -it < initramfs-5.3.7-200.fc30.x86_64.img . early_cpio kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/GenuineIntel.bin 26 blocks
That early_cpio file is a text file with nothing but a line that says "1" in it.
There used to be kernel modules and scripts and stuff. I'm so confused now.
They're probably still there. I don't know how the initramfs' format may have changed but [root@ddt-f30 boot]# lsinitrd initramfs-5.3.7-200.fc30.x86_64.img still shows that there's lots of modules in my initramfs.
On Fri, 1 Nov 2019 18:57:43 +0100 Markus Schönhaber wrote:
They're probably still there. I don't know how the initramfs' format may have changed but [root@ddt-f30 boot]# lsinitrd initramfs-5.3.7-200.fc30.x86_64.img still shows that there's lots of modules in my initramfs.
Yep, I see lots of stuff with lsinitrd (which I never heard of before :-). Are there two archives concatenated together now or something? I see there is an unpack option, so I guess that's what I need to use to poke around now.
they are now putting an early cpio in the intramfs that includes intel/amd firmware that will load before linux.
If you want to use cpio to see the 2nd part you will have to use a dd if=initnam bs=512 skip=<blocksinthefirstsection> | zcat | cpio cmd
The first part is uncompressed the 2nd part is compressed, the microcode stuff is in front of the "normal" cpio. lsinitrd correctly deals with it on most oses (not all hence me knowing how to look at it on the oses that lsinitrd does not work on).
On Fri, Nov 1, 2019 at 5:17 PM Tom Horsley horsley1953@gmail.com wrote:
On Fri, 1 Nov 2019 18:57:43 +0100 Markus Schönhaber wrote:
They're probably still there. I don't know how the initramfs' format may have changed but [root@ddt-f30 boot]# lsinitrd initramfs-5.3.7-200.fc30.x86_64.img still shows that there's lots of modules in my initramfs.
Yep, I see lots of stuff with lsinitrd (which I never heard of before :-). Are there two archives concatenated together now or something? I see there is an unpack option, so I guess that's what I need to use to poke around now. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 11/2/19 1:12 AM, Roger Heflin wrote:
they are now putting an early cpio in the intramfs that includes intel/amd firmware that will load before linux.
If you want to use cpio to see the 2nd part you will have to use a dd if=initnam bs=512 skip=<blocksinthefirstsection> | zcat | cpio cmd
More easily,
/usr/lib/dracut/skipcpio $initramfs >$initramfs.cpio.gz
-
Markus Schönhaber -
Roberto Ragusa -
Roger Heflin -
Tom Horsley