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

          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

          Running qemu-guest-agent on windows server 2008

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I know how I need to configure any linux guestvm in order to make qemu-guest-agent work. This is because there is a lot of documentation on it available, this is not the same with a windows guest. I wanted to know what steps I need to take to make qemu-GA work with a windows guest. I know I need to specify a channel type in the xml file of my windows vm, but further than that?? Does somebody has some more experience with this? Thanks. Running system: Debian 9 (on VMware) 3GB ram & 100GB DISK Running libvirt Daemon Several other guest vms running in background Windows guest: Windows server 2012 512MB RAM & 32GB DISK Virtio drivers working windows virtual-machine kvm qemu libvirtd share | improve this question asked Jan 13 at 0:02 codenerd123 1 1 add a comment  |  up vote 0 down vote favorite I know how I need to configure any linux guestvm in...
          Read more