| 1 |
On Sat, 13 Jul 2019 18:18:35 +0100, Mick wrote: |
| 2 |
|
| 3 |
> Anyway, if you want to look at the initramfs contents manually, I |
| 4 |
> suppose you will need to decompress your initramfs in a temporary |
| 5 |
> directory to see its contents. First find what archive format has been |
| 6 |
> used. |
| 7 |
> |
| 8 |
> file /boot/EFI/... initramfs-XXX.img |
| 9 |
> |
| 10 |
> will output gzip, bzip2, lzma or similar archive type. Then create a |
| 11 |
> temporary directory to work in and use the corresponding compression |
| 12 |
> type: |
| 13 |
> |
| 14 |
> mkdir ~/tmp_initramfs |
| 15 |
> cd ~/tmp_initramfs |
| 16 |
> |
| 17 |
> zcat /boot/EFI/... initramfs-XXX.img | cpio -idmv |
| 18 |
|
| 19 |
Did you build the initramfs with genkernel or dracut? If the latter, just |
| 20 |
run lsinitrd, which lists the contents of the current kernel's initramfs. |
| 21 |
You can also inspect individual files within the initramfs. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
Your lack of organisation does not represent an |
| 28 |
emergency in my world. |
Archives