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

Microcode



I'm building a live image off debian wheezy and initramfs-compression lzma.

It works fine.

When I enable backports, I hit an issue in chroot_hacks where it tries to un-gzip initrd (to recompress using lzma) because with backports enabled, the initrd consists of a cpio with microcode followed by the regular gzipped initrd (so ungzipping fails).

My questions are:

  1. Should I be including microcode for a live image.
  2. If yes, when I look in the first part of initrd, I see that the intel microcode file is there (GenuineIntel.bin) but not the AMD microcode (AuthenticAMD.bin).  I'm guessing this is because the capability of putting the microcode at the front of the initrd was designed thinking the initrd would only be for the machine it was built on so it doesn't include all possible microcodes that might be needed by a live system?  Do I have to do something to include both?
  3. Is it ok to include the microcode from wheezy rather than wheezy-backports even though I have the wheezy-backports kernel and firmware? The older microcodes don't force depend on iucode-tool and I think that is was causes the "fancy" initrd.
Thanks!
Corey


Reply to: