I guess this link

http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Hybrid_Iso

did not pan out for you?

Unfortunately, no. In fact, following that approach gave me a boot media that was not even recognized by my asus (This is despite it functioning perfectly well on another computer).


I am going to continue looking into this(how to get a live distro to boot). I

I do have another question though. Is there anything I can check with gparted to make sure that nothing is seriously amiss here? You mentioned before that you suspect something might be wrong, based on the output of those commands. Can we check to make sure that I haven't wrecked something?

I have used rufus with Mint with success. Are you sure you checked all of the options the same? All I needed was Partition for GPT, IIRC. Rufus does not rely on the image itself to be compatible, as it installs its own bootloader (syslinux), So as long as you configured everything properly, it should boot.

Unfortunately my Windows VM doesn't want to boot right now, so I can't play with rufus, I'll give a shot later.

Being that you are unsure of what you are doing, it's probably one small thing you're missing that's causing the other images not to work.

Were you dealing with the UEFI problem? Keep in mind that none of these boot media were strictly speaking dysfunctional- they all booted when plugged into another computer. I don't think rufus is at fault here. When I attempted to select GPT, it would give me an error message(except with stretch debian or gparted). I will try mint.

Thanks for all of the help!

EDIT:

Mint does not work either. GPT is not allowed.

Do you remember the error message?

Certainly, here it is:

Now that I think about it, I was using x64 images, and modifying to boot on ia32. You could do the same as well, you're not stuck with a 32 bit OS on that hardware as I'm pretty sure that's a 64 bit chip. However it's a bit of work. Not terrible, but more than a simple write and install.

Another thought as far as using dd and other programs that write the data to the USB drive directly, I've found that some devices may want a specific block size when written. Some sticks I made without specifying this would work on some machines, while others needed it.

If using a 64 bit ISO, or if you wish to try these settings with your current ISOs, maybe the cluster size for you will make the difference. Use these settings with Rufus:

- Partition for GPT
- Filesystem FAT32
- Cluster size: 64K

Now, only if you're going to attempt using a 64 bit ISO, download

https://github.com/jfwells/linux-asu...t/bootia32.efi

and place that in the /EFI/BOOT directory on the newly created stick. Otherwise the correct file should have been installed.

Unfortunately, playing with these settings did not seem to change anything. I am still getting that error message. Regardless of 32 v. 64 bit, 64k, etc. Should I attempt to use another program to create the USB?

I experimented earlier with adding the booita32.efi file to some of the boot media. It usually made a difference: it would usually give me a usb that would boot to the GRUB, where before it would usually just flash and go back to the BIOS. I didn't know what to do at the GRUB to take me in the right direction.

So, I am going to say(provisionally) that I have made some progress. I made an ARCH usb with gpt, and found a bootia32.efi file(that I modified so that the iso labels were correct). I have been able to boot into this and configure my tethered android properly.

I think at this point I am going to attempt to follow the detailed arch wiki beginner's guide, and hopefully get this working!

Thanks for all of the help everyone! I will ensure that I mark this solved if I don't hit any suspicious snags.

1 members found this post helpful.

Well, I think I'm home free! Wifi is up and running, so now all that's left is configuring my system(the fun part). Thanks again for all of the help.