Tiny Core Base > Corepure64

Bootx64.efi missing?

<< < (5/7) > >>

nick65go:
PS: sorry, correction for FAT12 tool in linux, it is in tcz;
You can build the floppy, lucky is does not need to be MS-DOS bootable, floppy is just a container / image for /EFI/BOOT/BOOTx64.EFI

--- Code: ---tce-load -iw dosfstools.tcz
dd if=/dev/zero of=fat12.img bs=160K count=1
mkfs.fat -F12 fat12.img
mount -o loop fat12.img /mnt/
--- End code ---
The rest for UEFI64 (and even for UEFI32 with small logical changes) still stands up true!

PDP-8:
Wow Nick, thanks for the research.  I must admit it's a bit over my head, so it will take some extensive study.

Going OT now, but I'm pursuing the ability to simply archive an image, (say zip / gzip etc), and merely unarchive it to a fat32  drive and have it be bootable without any special handling in regards to "making it bootable" for modern uefi-only machines.

Its what I'm replying on now.  I'm puzzled because it seems only Gparted Live and Porteus have this ability to just unarchive and go afaik. Intriguing, but thanks for all your hard work anyway.  Very useful.
 

nick65go:
@PDP-8: it is ZERO work to do what you want. Just extract ANY archive you have (tar, gzip, blah bla) into ANY FAT-compatible partition (FAT12/16/32) you already have on a HDD/SDD/USB.

The tricks are:
1. The FAT-compatible partition must have "label" as ESP type. Warning: It is NOT the fdisk "label", neither the UUID. It is another marker (gpart can write it).

2. - your archive must have a /EFI/BOOT/BOOTX64.EFI (to auto boot); or else from FIRMWARE menu of the PC/machine just select the EFI file you want to boot from. This EFI can be anywhere into an ESP partition. BTW: you ca have (and boot from) many ESP partitions on the same HDD. [ignore MS-windows how say just one ESP and to be the first one on HDD, or to be only FAT32).

3. [Optional] You need a "good" FIRMWARE, obeying the UEFI standard, aka: can boot from MBR and GPT disks. Most UEFI64 today take short-cuts, meaning they wrongly see only FAT32 and only GPT disks (blame stupid/ cheap vendors).

FYI: my demo was about ISO (from qemu), or burn ISO on a DVD/CDROM to boot UEFI64 from eltorito standard.

PDP-8:
I get it, but Gparted Live and Porteus don't use those flags at all. :)

Getting philosophical here - while we know that TC is not a turnkey-solution, TC -at least for 64 bit intended for modern machines (post 2011 or so), the message that the unbootable iso on modern machines says is that if one is not smart enough to figure it out, or build it yourself from distribution files, your kind is not welcome.  Kind of a convenient barrier to restrict all same old questions from distro-hoppers.  I get it.

What I propose is for 64 bit, is to be kind to the newcomers and remove the iso completely, rather than let less-knowledgeable /users/ who want to follow the true TC way, not beat their heads against the wall trying to make it work on machines that are in the majority now.

Being dramatic, if that is the goal - to raise the bar to just devs, developers, or highly advanced users who could quote the El-Torito and boot specs from the back of their hands, then remove even the 32-bit iso's from being downloaded as well, because we certainly don't want anyone burning an iso from old Windows-For-Workgroups vintage computer with Roxio-cd-deluxe and asking further questions.

See the mixed message here?

Obviously, I love TC.  I have a plethora of ways to run it from the classic diy method to relying on 3rd party front ends.

I'm just worried that unless we acknowledge that uefi machines are here to stay, and make it easier to boot - just as doing so blindly with say the Roxio burner of the long past, it will just become a vintage-computer distribution, with vintage users like myself being the only ones who like it.

/rant over/ Nobody should be offended.  I'm just worried.

gadget42:
for reference see previous post:
http://forum.tinycorelinux.net/index.php/topic,24873.msg162202.html#msg162202

i am most worried about the forum vanishing /forever/

seems like losing this vast store of knowledge might/should be paramount?

again. not. pointing. fingers.

no. offense. intended.

not. a. rant.

peace.

Navigation

[0] Message Index

[#] Next page

[*] Previous page