[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: initrd sizes mushroomed several months ago



On 2023-02-03 at 01:45, Felix Miata wrote:

> David Wright composed on 2023-02-01 22:39 (UTC-0600):


>> FTR, I reinstalled 5.10.0-21-amd64 on another machine with MODULES=dep
>> and for comparison (initrd only):
>  
>> $ unmkinitramfs /boot/initrd.img-5.10.0-21-amd64 /tmp/unpacked10-21
>> cpio: etc/console-setup/null: Cannot mknod: Operation not permitted
>> $ du -sh /tmp/unpacked10-21/main/lib/modules/5.10.0-21-amd64/kernel/   # modules
>> 5.6M    /tmp/unpacked10-21/main/lib/modules/5.10.0-21-amd64/kernel/
>> $ du -sh /tmp/unpacked10-21/main/lib/firmware
>> du: cannot access '/tmp/unpacked10-21/main/lib/firmware': No such file or directory
>> $ 
>  
>> … so zero firmware is required to boot this machine (and the
>> same is true for my production machine).
> 
> That's how it is here on PCs with Intel or NVidia graphics, but apparently
> not so AMD/ATI, going by what's now being packed into initrds.

FTLIW, my own primary desktop has an AMD graphics card (and has since
before the initial Debian install), and doesn't have these large
initrds:

$ lh /boot/initrd.img-*
-rw-r--r-- 1 root root 36M Sep  2 08:27 /boot/initrd.img-5.18.0-4-amd64
-rw-r--r-- 1 root root 36M Dec  9 07:53 /boot/initrd.img-6.0.0-4-amd64

I haven't dug into them any deeper than this, but it may be worth having
the confirmation that it's not something common to all machines with AMD
graphics cards.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: