| Re: [SliTaz] VDI? |
[ Thread Index | Date Index | More lists.tuxfamily.org/slitaz Archives ]
| You are on the early side of uefi bios that support what we are trying to do so please absorb two methods knowing one may work better than the other. Secure boot, if enabled within bios is an absolute showstopper as far as I know. This may be the source of the problem. I have no windows hardware to simulate on and I can not find enough documentation that is readable to point of understanding slitaz hybrid iso to exe file enough to support. However this is one of many methods to boot slitaz. If you want to try this it will be non invasive and very temporary. Everything is easy to set back. This method will make it so you can put usb in and it will boot to slitaz and without usb it will boot to windows with no intervention needed like selecting one or the other at boot. You can eject medium after boot on slitaz making it so you could take usb out after boot. If it was me I would prefer to test drive, noon invasively, before committing to an installation. First step is disable secure boot. We will try efi first as any os that is uefi capable is meant to be boot this way... If we disable uefi by enabling legacy boot in bios and go to legacy boot you wont boot the os in gpt mode and it will boot in bios mode. This may not work as developers intended. If you can get rufus fired up and set your partition type to gpt. The incorrect setting is bios. This will tell rufus to put a 500mb partition on the front of the volume that will hold the boot loader in efi executable format. Use rufus in dd mode and with gpt and let it write. Usually grub-efi makes a particuar structure here in that fat32 partition that we will look at in a moment. Plug usb in to computer and reboot to bios. You may have to enact this through settings. Using the below manual link start on page 91 and once you have your usb made with rufus and you have it plugged in when accessing bios. Go to efi boot order and entry screen and make new boot entry. First step is to title it. If you clik on 3 dots for where to find file to boot to click it opens primitive browser. Look at the addresses that are available. If you have one hard drive there should be two. Once for a device on .../pci/... and another on .../usb/..... Aim for the line with usb in the line. Go in to that line and look for a boot folder and look for a bootx.xx. UEFI is a mess. If you have a 32 bit bios you may need to aim at a 32 bit file. If you have a 64 bit bios aim for the BOOTX64.efi file. You may have to use process of elimination and find the correct one the hard way but it will be worth it. I understand why developers would try to make a way to jump over the uefi mess of possibility but I am sorry that I just cant understand what the exe is supposed to do. If you dont mind an experiment try this. If it fails you can go back in and re-enable secure boot and delete the boot item and its back to normal but I feel that you have one of 4 possibilities between two “boot shims” aka the bootx32.efu or bootx64.efi and grubx32.efi and grubx64.efi. And thats even if they used grub but there should be something similar there in the efi partition. It may be within a DSO/boot/grubx64.efi with dso or similar at top level. Very few standards at windows 8 time on efi partitons. Especially with windows only vendors. If none of that worked you could go back in to bios and enable legacy boot but I do not know if this is a good idea. I had an early 2020 dell g7 a little less than a year ago and was first on internet to install linux on to. Even ubuntu used wrong file in efi partition to boot to. I had to manually make boot entry like instructed above and aim it at the other efi file to choose from and it worked as designed. Until then it would boot but install would fail at bootloader saying no efi partitions were available. For the age of the hardware and what efi was like then (mostly implemented by MS to make sure it was almost impossible to boot anything else) I would expect to make another boot entry in bios. Your manual is here: Starting on page 91 Please write back if you get hung up on anything Sent from my iPad On May 11, 2020, at 8:10 PM, Phoenix Soul <phoenixlight101@xxxxxxxxx> wrote:
|
| Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |