search for: iucode

...14-05/msg00053.html says > that I have to use ?cpio -H newc? not ?cpio -o c?, but I don?t know how > the Debian tools create the initrd. The intel-microcode package contains: /usr/share/initramfs-tools/hooks/intel_microcode which will be called during initamfs generation. It seems to call iucode_tool, from the iucode-tool package. That's a binary tool which seems to include its own cpio writer implementation, I've no idea if that is like a 'newc' or not. However: ijc at dagon:tmp$ find iucode-tool/ | cpio -o > normal.cpio 828 blocks ijc at dagon:tmp$ find iucode-tool/ |...

> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory structure

...ld.so.conf.d/fakeroot-x86_64-linux-gnu.conf > etc/ld.so.conf.d/x86_64-linux-gnu.conf > >Now you can experiment with regenerating the ucode bit with whatever >commands are recommended and reconcatenating the two. If that works then >we know there is some incompatibility between iucode-tools's output and >Xen's cpio reader (could be a bug in either or both I think). All right. Can you please provide some commands how to create and reconcatenate the two initrds? I don?t have any experience with cpio. Shade and sweet water! Stephan -- | Stephan Seitz E-Ma...

..._64-linux-gnu.conf > > etc/ld.so.conf.d/x86_64-linux-gnu.conf > > > >Now you can experiment with regenerating the ucode bit with whatever > >commands are recommended and reconcatenating the two. If that works then > >we know there is some incompatibility between iucode-tools's output and > >Xen's cpio reader (could be a bug in either or both I think). > > All right. Can you please provide some commands how to create and > reconcatenate the two initrds? I don?t have any experience with cpio. The reconcatenate bit is easy, just: $ cat i...