Announcement

Collapse
No announcement yet.

booting bootx64.efi, just shows filepath

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • booting bootx64.efi, just shows filepath

    I followed https://www.memtest86.com/tech_configuring-grub.html, in the end when chainloading bootx64.efi, I just get a filepath. Do you have any Idea what that output means?

    grub> insmod fat
    grub> insmod part_gpt
    grub> chainloader (hd0,gpt1)/efi/boot/bootx64.efi
    /EndEntire
    file path: /ACPI(a0341d0,0)/PCI(0,17)/UnknownMessaging(1a)/HD(1,800,7000,ef09d5
    c7dc99cb49,2,2)/File(\efi\boot)/File(bootx64.efi)/EndEntire



    It's a vfat partition:
    bash> lsblk -fm
    NAME FSTYPE LABEL MOUNTPOINT SIZE OWNER GROUP MODE
    mmcblk1 3.6G admin disk brw-rw----
    |-mmcblk1p1 vfat mygrub 14M admin disk brw-rw----
    ...



    Thanks

  • #2
    It seems like you're trying to run boot commands directly via the grub CLI as opposed to saving the boot entry to the grub config, as the guide directs you to do?

    Are you certain your efi boot partition is on hd0 gpt1? Can you please post the output of the $ df command?

    Also tell us what Linux distro and version you are using, and whether it is 32 bit or 64 bit.

    Comment


    • #3
      It seems like you're trying to run boot commands directly via the grub CLI as opposed to saving the boot entry to the grub config, as the guide directs you to do?
      Yes, but it's the same in a bootmenuentry

      Are you certain your efi boot partition is on hd0 gpt1? Can you please post the output of the $ df command?
      It's at least where I copied the memtest file. The Kernel image is on (hd0,gpt2), I copied the memtest file there as well, with the same result

      grub> ls (hd0,gpt1)/efi/boot
      bootx64.efi grub.cfg fonts/


      bash > df
      Filesystem 1K-blocks Used Available Use% Mounted on
      /dev/root 3451024 1494604 1761400 46% /
      devtmpfs 447344 0 447344 0% /dev
      tmpfs 449720 300 449420 0% /run
      tmpfs 233856 760 233096 0% /var/volatile
      /dev/mmcblk1p2 170439 78196 79628 50% /boot
      /dev/mmcblk1p3 13847 2886 9886 23% /etc/custom/share
      /dev/mmcblk1p1 14290 9578 4712 67%



      Also tell us what Linux distro and version you are using, and whether it is 32 bit or 64 bit.
      It's an 64bit yocto based embedded distro

      bash > uname -m
      x86_64

      bash >
      uname -a
      Linux myDistro 4.14.146-rt67-cg-8.5.0f0-x64-32 #1 SMP PREEMPT RT Tue Aug 25 01:58:07 UTC 2020 x86_64 GNU/Linux


      Comment


      • #4
        Are you trying to run this on an embedded device, with external storage? Is this a UEFI system, that contains an EFI boot partition? If not, MemTest won't work - you need a partition of EFI type that will be used to chainload MemTest.

        Originally posted by martiinz View Post
        Yes, but it's the same in a bootmenuentry
        I've found some minor differences in the past, especially with syntax. I'd recommend you try editing the grub file, just to rule this out as a possible cause.

        Originally posted by martiinz View Post
        It's at least where I copied the memtest file. The Kernel image is on (hd0,gpt2), I copied the memtest file there as well, with the same result

        grub> ls (hd0,gpt1)/efi/boot
        bootx64.efi grub.cfg fonts/

        bash > df
        Filesystem 1K-blocks Used Available Use% Mounted on
        /dev/root 3451024 1494604 1761400 46% /
        devtmpfs 447344 0 447344 0% /dev
        tmpfs 449720 300 449420 0% /run
        tmpfs 233856 760 233096 0% /var/volatile
        /dev/mmcblk1p2 170439 78196 79628 50% /boot
        /dev/mmcblk1p3 13847 2886 9886 23% /etc/custom/share
        /dev/mmcblk1p1 14290 9578 4712 67%
        Try to see if you have a /boot/efi partition located on your system somewhere.

        By the way: I don't think /dev/mmcblk1p2 corresponds to hd0/gpt1 or even gpt2 for that matter, you may want to check this.

        Comment


        • #5
          Are you trying to run this on an embedded device, with external storage? Is this a UEFI system, that contains an EFI boot partition? If not, MemTest won't work - you need a partition of EFI type that will be used to chainload MemTest.
          Yes it an EFI Type.
          The (hd0,gpt1) corresponds to /dev/mmcblk1p1, where I've copied the memtest file

          Code:
          bash> fdisk -l /dev/mmcblk1
          Disk /dev/mmcblk1: 3.6 GiB, 3875536896 bytes, 7569408 sectors
          Units: sectors of 1 * 512 = 512 bytes
          Sector size (logical/physical): 512 bytes / 512 bytes
          I/O size (minimum/optimal): 512 bytes / 512 bytes
          Disklabel type: gpt
          Disk identifier: 2720433F-CF21-45B4-9D1C-1A84F209F63F
          
          Device Start End Sectors Size Type
          /dev/mmcblk1p1   2048   30719    28672   14M EFI System
          /dev/mmcblk1p2  30720  391167   360448  176M Linux filesystem
          /dev/mmcblk1p3 391168  421887    30720   15M Linux filesystem
          /dev/mmcblk1p4 421888 7567359  7145472  3.4G Linux filesystem


          I've found some minor differences in the past, especially with syntax. I'd recommend you try editing the grub file, just to rule this out as a possible cause.
          Ok, good to know. I've tried those steps already in a menuentry with the same result
          Last edited by martiinz; Mar-03-2021, 11:21 AM.

          Comment

          Working...
          X