Linux EFI stub CMDLINE problem: initrd is ignored

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I have a weird problem with my EFI stub kernel: I'm using the CMDLINE kernel parameter to pass parameters "root=xxx ro rootwait initrd=microcode.img" (microcode.img is an initrd containing the CPU microcode). I compile the kernel as EFI stub, and copy it to EFIBootbootx64.efi on my EFI system partition. The system boots up okay, the "root=" etc. have been recognized, but the microcode update didn't happen (as per /proc/cpuinfo; it shows the microcode version that's built in, not the one in microcode.img). But when I launch the EFI Shell on boot, and boot bootx64.efi manually with exactly the same command line, the microcode gets updated (as per /proc/cpuinfo; it now shows the microcode version in microcode.img). In both cases, /proc/cmdline gives exactly the same, including "... initrd=microcode.img". It's just as if the initrd statement in the kernel CMDLINE is completely ignored. What am I doing wrong?






uefi initrd






share







New contributor




Hans Malissa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.























    up vote
    0
    down vote

    favorite












    I have a weird problem with my EFI stub kernel: I'm using the CMDLINE kernel parameter to pass parameters "root=xxx ro rootwait initrd=microcode.img" (microcode.img is an initrd containing the CPU microcode). I compile the kernel as EFI stub, and copy it to EFIBootbootx64.efi on my EFI system partition. The system boots up okay, the "root=" etc. have been recognized, but the microcode update didn't happen (as per /proc/cpuinfo; it shows the microcode version that's built in, not the one in microcode.img). But when I launch the EFI Shell on boot, and boot bootx64.efi manually with exactly the same command line, the microcode gets updated (as per /proc/cpuinfo; it now shows the microcode version in microcode.img). In both cases, /proc/cmdline gives exactly the same, including "... initrd=microcode.img". It's just as if the initrd statement in the kernel CMDLINE is completely ignored. What am I doing wrong?






    uefi initrd






    share







    New contributor




    Hans Malissa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have a weird problem with my EFI stub kernel: I'm using the CMDLINE kernel parameter to pass parameters "root=xxx ro rootwait initrd=microcode.img" (microcode.img is an initrd containing the CPU microcode). I compile the kernel as EFI stub, and copy it to EFIBootbootx64.efi on my EFI system partition. The system boots up okay, the "root=" etc. have been recognized, but the microcode update didn't happen (as per /proc/cpuinfo; it shows the microcode version that's built in, not the one in microcode.img). But when I launch the EFI Shell on boot, and boot bootx64.efi manually with exactly the same command line, the microcode gets updated (as per /proc/cpuinfo; it now shows the microcode version in microcode.img). In both cases, /proc/cmdline gives exactly the same, including "... initrd=microcode.img". It's just as if the initrd statement in the kernel CMDLINE is completely ignored. What am I doing wrong?






      uefi initrd






      share







      New contributor




      Hans Malissa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I have a weird problem with my EFI stub kernel: I'm using the CMDLINE kernel parameter to pass parameters "root=xxx ro rootwait initrd=microcode.img" (microcode.img is an initrd containing the CPU microcode). I compile the kernel as EFI stub, and copy it to EFIBootbootx64.efi on my EFI system partition. The system boots up okay, the "root=" etc. have been recognized, but the microcode update didn't happen (as per /proc/cpuinfo; it shows the microcode version that's built in, not the one in microcode.img). But when I launch the EFI Shell on boot, and boot bootx64.efi manually with exactly the same command line, the microcode gets updated (as per /proc/cpuinfo; it now shows the microcode version in microcode.img). In both cases, /proc/cmdline gives exactly the same, including "... initrd=microcode.img". It's just as if the initrd statement in the kernel CMDLINE is completely ignored. What am I doing wrong?






      uefi initrd




      uefi initrd





      share







      New contributor




      Hans Malissa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share







      New contributor




      Hans Malissa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share



      share






      New contributor




      Hans Malissa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 11 mins ago









      Hans Malissa

      11




      11




      New contributor




      Hans Malissa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Hans Malissa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Hans Malissa is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.

























          active

          oldest

          votes











          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );






          Hans Malissa is a new contributor. Be nice, and check out our Code of Conduct.









           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f477889%2flinux-efi-stub-cmdline-problem-initrd-is-ignored%23new-answer', 'question_page');

          );

          Post as a guest






















          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Hans Malissa is a new contributor. Be nice, and check out our Code of Conduct.









           

          draft saved


          draft discarded


















          Hans Malissa is a new contributor. Be nice, and check out our Code of Conduct.












          Hans Malissa is a new contributor. Be nice, and check out our Code of Conduct.











          Hans Malissa is a new contributor. Be nice, and check out our Code of Conduct.













           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f477889%2flinux-efi-stub-cmdline-problem-initrd-is-ignored%23new-answer', 'question_page');

          );

          Post as a guest
































































          -

          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
          Read more

          Displaying single band from multi-band raster using QGIS

          Image
          Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
          Read more

          How many registers does an x86_64 CPU actually have?

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
          Read more