Jump to content











Photo

a1ive's GRUB 2

grub2 uefi mbr

  • Please log in to reply
29 replies to this topic

#26 alacran

alacran

    Gold Member

  • .script developer
  • 2230 posts
  •  
    Mexico

Posted 02 January 2021 - 08:26 PM

Tested following menuentries:

menuentry "Boot /VHD/Mini-10-UEFI.vhd -l (NTFS) UEFI RAMDISK 2 GB" "/VHD/Mini-10-UEFI.vhd" {
  efiload /EFI/grub/ntfs_x64.efi
  search --no-floppy --set --file $2
  map --mem --rt -l $2
}

menuentry "Boot /VHD/Mini-10-UEFI.vhd (NTFS) UEFI RAMDISK 2 GB" "/VHD/Mini-10-UEFI.vhd" {
  efiload /EFI/grub/ntfs_x64.efi
  search --no-floppy --set --file $2
  map --mem --rt $2
}

First with -l do not work

 

Second without -l works fine

 

EDIT: The VHD file has a single NTFS partition, and was installed on Compact mode (LZX compressed), and it is located on a standard MBR uncompressed NTFS partition.

 

alacran


Edited by alacran, 02 January 2021 - 09:11 PM.


#27 alacran

alacran

    Gold Member

  • .script developer
  • 2230 posts
  •  
    Mexico

Posted 03 January 2021 - 01:47 AM

Also tested following menuentries:

menuentry "Boot /VHD/10x64-38.vhd - UEFI Grub2  SVBus  RAMDISK  - 3.8 GB" {
  efiload /EFI/grub/ntfs_x64.efi
  search --file --set=vhd_drive --no-floppy /VHD/10x64-38.vhd
  map --mem --rt ($vhd_drive)/VHD/10x64-38.vhd
  boot
}

menuentry "Boot /VHD/10x64-38.vhd -l UEFI Grub2 SVBus  RAMDISK  - 3.8 GB" {
  efiload /EFI/grub/ntfs_x64.efi
  search --file --set=vhd_drive --no-floppy /VHD/10x64-38.vhd
  map --mem --rt -l ($vhd_drive)/VHD/10x64-38.vhd
  boot
}

In this case this is a normal (uncompressed) install on a 3.8 GB VHD, single NTFS partition VHD.

 

The first menuentry without -l booted fine.

 

The second menuentry with -l do not load to Ram.

 

alacran



#28 alacran

alacran

    Gold Member

  • .script developer
  • 2230 posts
  •  
    Mexico

Posted 03 January 2021 - 08:04 AM

Test booting a RamOS on a 4000 MB (3.9 GB) VHD (Not compressed):

 

Just saw on a1ive's grub2 official releases page there is a new version, released a few hours ago, I decided to download it and after create the respective x86 and x64 efi versions and the core.img file, I used it for this test.

 

Only to test the limits I ran this test.

 

I was able to Ramboot a 4000 MB VHD NTFS single partition, on same PC with 8 GB of Ram, in this case this is same normal (uncompressed) installation, and it booted fine.

 

To test this, I increased the VHD size in command line and latter just expanded the single NTFS partition and edited the grub.cfg,  the VHD was not fragmented when cheked with Winconting.

menuentry "Boot /VHD/10x64-39.vhd - UEFI Grub2  SVBus  RAMDISK  - 3.9 GB" {
  efiload /EFI/grub/ntfs_x64.efi
  search --file --set=vhd_drive --no-floppy /VHD/10x64-39.vhd
  map --mem --rt ($vhd_drive)/VHD/10x64-39.vhd
  boot
}

menuentry "Boot /VHD/10x64-39.vhd -l UEFI Grub2 SVBus  RAMDISK  - 3.9 GB" {
  efiload /EFI/grub/ntfs_x64.efi
  search --file --set=vhd_drive --no-floppy /VHD/10x64-39.vhd
  map --mem --rt -l ($vhd_drive)/VHD/10x64-39.vhd
  boot
}

The first menuentry without -l booted fine.

 

The second menuentry with -l do not load to Ram.

 

I don't think it is a good idea to go further as the memory above 4 GB available on this PC, is 4 GB or 4096 MB.

 

Then I can conclude using a1ive's Grub 2 we can make use of all the memory available on the PC above 4 GB, without any issue.

 

alacran


  • liuzhaoyzz likes this

#29 zammibro

zammibro

    Member

  • Members
  • 59 posts
  •  
    United States

Posted 13 May 2021 - 07:37 PM

Sorry for interrupting this interesting conversation with a stupid question: how to add  a1ive's GRUB2 to a Windows 10 PC SSD in a way, so it can be called from a Grub4DOS entry chosen in Windows Boot Manager menu? Its interesting that practical usage instructions by regular folks are near always missed in such smart exchange.  :)


Edited by zammibro, 13 May 2021 - 07:39 PM.


#30 alacran

alacran

    Gold Member

  • .script developer
  • 2230 posts
  •  
    Mexico

Posted 14 May 2021 - 04:36 AM

Please read this post, it may clarify some things for you: http://reboot.pro/in...400#entry218202

 

alacran







Also tagged with one or more of these keywords: grub2, uefi, mbr

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users