Hi, Sorry for kind of spam. When corrected depmod usage then it started to work. Issue solved so the handover scenario from "legacy PXE boot driver" to "RHEL6 i40e driver" in PXE network RHEL installation may be tested. However "getNetConfig" is failing to configure i40e network interface. It will be addressed in separate thread. Thanks and sorry for bothering. krzysztof
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>.. From: Wisniewski, Krzysztof Sent: Thursday, May 08, 2014 12:19 PM To: '[email protected]'; '[email protected]' Cc: Kepczynski, Tomasz; Gafka, Aleksander; Morgan, Jack; Lawton, Shanon R; Ronciak, John; Kulkarni, Suyog D; Wallace, Andrew; Ciesielski, Dariusz K Subject: [how to] modify initrd.img from RHEL6.5_tftpboot to include i40e module Hi, Looking for help with RHEL 6.5 initrd.img modification to include i40e module for 40G adapter to perform legacy PXE boot on it. What I try to acomplish: 40G PXE boot of RHEL 6.5 on 40G NIC with PCI ID x1572. What I do: -install RHEL 6.5 with kernel 2.6.32-431.el6.x86_64, retrieve tftpboot initrd.img and make o copy of it in /tmp -build i40e module and test that it works correctly -exctract the content of initrd.img in /tmp with xz and cpio -> mv initrd.img initrd.img.xz xz -d -F lzma initrd.img.xz mkdir initrd cd initrd-new cpio -ivdum < ../initrd.img -add i40e module into initrd -> copy i40e.ko into /tmp/initrd/modules/2.6.32-431.el6.x86_64/kernel/drivers/net/i40e/ gzip i40e.ko modify files: module-info, modules.alias, modules.dep, modules.networking, modules.pcimap run: depmod -b initrd -a and verify with: modinfo -b initrd i40e -build initrd into initrd.img -> find . -print |cpio -o -H newc | xz -F lzma > ../initrd.img -copy generated initrd.img into PXE linux server into tftpboot data -reboot platform, select PXE boot on 40G NIC and RHEL 6.5 tftpboot initrd.img is loaded and fails to find 40G networking interface... with info as in attached file: module i40e not found..... I would appreciate any hints or links on how to incorporate i40e module into tftpboot initrd.img in RHEL6 ? Thanks a lot, regards, krzysztof wisniewski -------------------------------------------------------------------- Intel Technology Poland sp. z o.o. ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN. Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited. ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
