Ok so Im trying to sucsessfully boot various linux ISO's with Grub2Win version 0.9.8.4 managed to get Androidx86_CM13_6.01 & CM14 they run silky smooth but after a reboot, it all starts over. I CAN'T figure out how to implement the "persistant" boot parameter so my work is SAVED upon system reboots, here are the strings of param Im using to boot :
set bootdir=/CyanogenMod13
set kernelfile=$bootdir/kernel
getbootpartition file $kernelfile
linux $kernelfile
initrd $bootdir/initrd.img
echo Grub will boot Android 64 Bit
echo Boot disk address is $root/CyanogenMod13/cm13.iso
echo The boot mode is BOOTx64.EFI
Also when it comes to trying to boot Ubuntu14.04, sn3rpOS, BlackARCH, Kali, and BackTrack to name a FEW I always manage to get STUCK halfway through the bootup process @ some BUSYBOX shell were i can ONLY type more parameters/commands and I TRYED just about every command possible and NOTHING I can do there complete's the BOOT, Ive been playing around with ALL type's of Boot Parameters and NO! GO! So Im hoping maybe someone here can point out what I cant figure out. Here is the code im attemping with sn3rpOS and Ubuntu:
UBUNTU:
set bootdir=/Ubuntu
set kernelfile=$bootdir/casper/vmlinuz.efi
getbootpartition file $kernelfile
linux $kernelfile
initrd $bootdir/casper/initrd.lz
echo Grub will boot Ubuntu
echo Boot disk address is $root/Ubuntu/Ubuntu.iso
echo The boot mode is BOOTx64.EFI
set bootparms='boot=casper iso-scan/filename='$isopath' reboot=cold nomodeset noprompt noeject ---'
SN3RPOS:
set partlabel=sn3rpOS
getbootpartition label $partlabel
linux /live/vmlinuz root=LABEL=$partlabel splash=verbose nomodeset
initrd /live/initrd.img
echo Grub is now booting sn3rp
echo Boot disk address is $root/sn3rpOS/sn3rp.iso
echo The boot mode is Partition Search By Label
sleep -v -i 5
Also tryed somthing simular to what makes Androidx86 boot no problrm and it's suprisingly a very simular result to the parameter above infact it gets a little further here it is:
set gfxpayload=1366x768
set isopath='/sn3rpOS/sn3rp.iso'
set kernelpath='/live/vmlinuz'
set initrdpath='/live/initrd.img'
echo Grub will boot sn3rp
echo Boot disk address is $root/sn3rpOS/sn3rp.iso
echo The boot mode is grubx86.cfg
set bootparms='from='$isopath' persistence boot=live ip='$isopath' username=root nomodeset'
Can someone please help me i know it's probley one little line of code that will complete the boot up, but Im completely stuck on what the line is. My laptop is UEFI GPT 500GB dell inspiron11-3168 8GB RAM, Win10 Enterprise 1703 15063.632...
Last edit: Jack Sadowski 2017-10-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Most Linux ISOs are designed to be Live systems. ie Each time you boot you get the exact same system. Some Live ISOs support installs to the disk which when done support changes.
What you have to do with each ISO that you want to save changes is seach thru the files within the ISO for references to persistence and changes and save data. Look for .cfg files, .conf files, .doc and .hlp files and read them to see if they reference saving configuration settings and data files.
Most Linux systems support saving user files onto drives outside the Linux file system, like onto the FAT32 USB flash drive where the ISO is stored. It doesn't work for configuration changes but it does work for downloads and backups.
Good luck.
Ed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ciao, I have added successfully boot for Linux Mint.
I would like to have it in "NO VERBOSE mode.
(Mint display carefully just is Mint logo during the boot process
What can I do ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok so Im trying to sucsessfully boot various linux ISO's with Grub2Win version 0.9.8.4 managed to get Androidx86_CM13_6.01 & CM14 they run silky smooth but after a reboot, it all starts over. I CAN'T figure out how to implement the "persistant" boot parameter so my work is SAVED upon system reboots, here are the strings of param Im using to boot :
Also when it comes to trying to boot Ubuntu14.04, sn3rpOS, BlackARCH, Kali, and BackTrack to name a FEW I always manage to get STUCK halfway through the bootup process @ some BUSYBOX shell were i can ONLY type more parameters/commands and I TRYED just about every command possible and NOTHING I can do there complete's the BOOT, Ive been playing around with ALL type's of Boot Parameters and NO! GO! So Im hoping maybe someone here can point out what I cant figure out. Here is the code im attemping with sn3rpOS and Ubuntu:
UBUNTU:
SN3RPOS:
Also tryed somthing simular to what makes Androidx86 boot no problrm and it's suprisingly a very simular result to the parameter above infact it gets a little further here it is:
Can someone please help me i know it's probley one little line of code that will complete the boot up, but Im completely stuck on what the line is. My laptop is UEFI GPT 500GB dell inspiron11-3168 8GB RAM, Win10 Enterprise 1703 15063.632...
Last edit: Jack Sadowski 2017-10-05
Hello Jack.
Most Linux ISOs are designed to be Live systems. ie Each time you boot you get the exact same system. Some Live ISOs support installs to the disk which when done support changes.
What you have to do with each ISO that you want to save changes is seach thru the files within the ISO for references to persistence and changes and save data. Look for .cfg files, .conf files, .doc and .hlp files and read them to see if they reference saving configuration settings and data files.
Most Linux systems support saving user files onto drives outside the Linux file system, like onto the FAT32 USB flash drive where the ISO is stored. It doesn't work for configuration changes but it does work for downloads and backups.
Good luck.
Ed
Hello again Jack,
In looking at the boot menus in the UBUNTU parms you reference $isopath but I don't see where you set it's value.
And when booting ISOs you need loopback loop $iso and linux (loop)/boot/ and initrd (loop)/ parms either directly or via g2wisoboot.
Check out this thread for some examples. https://sourceforge.net/p/grub2win/discussion/general/thread/1287e15d/
Ed
Last edit: Ed P 2017-10-05
Ciao, I have added successfully boot for Linux Mint.
I would like to have it in "NO VERBOSE mode.
(Mint display carefully just is Mint logo during the boot process
What can I do ?
Hi,
You should update the Mint menu entry.
Run Grub2Win and click the "Manage Boot Menu" button.
Then click the entry for your Linux Mint.
This should take you to an orange edit screen where you can update the Linux boot parms.
Replace the "verbose" parm with "quiet"
Then click OK and run Grub2Win to completion.
Please let me know if this works for you.
Thanks,
Dave
Thanks it's OK:
the boot is quiet ( only 1 nine ) no Mint Graphic logo displayed during the boot ... but it's OK !
Well done !
Hi again,
If you would like the logo to display, add the Linux parameter "splash" along with "quiet".
You should also remove the "nosplash" parameter if it is there.
Please let me know if this works for you.
Thanks,
Dave