Tiny Core Base > Corepure64
GRUB 2 always starts in command line - can't proceed - EFI Boot
coreplayer2:
--- Quote from: PDP-8 on July 27, 2019, 04:48:14 PM ---I just find it interesting that using fat32 for the uefi partition is not actually mandatory - one can use any filesystem they want as long as it is driven properly. But this seems to have been repeated so often that it is taken for truth.
Wait - what? My entire stick can be ext2, or xfs or whatever I like - including the efi partition? Truth.
--- End quote ---
Not exactly true, firmware capacity has traditionally been limited. Therefore manufacturers will likely provide support only for intended Operating Systems.
For compatibility FAT support on all machines is provided for sure, NTFS is often provided to support Windows installs on drives without an ESP.
Apple products support FAT and AppleFS on recent mac’s
I could be wrong here but even with recent increases of bios/firmware memory only pc’s destined for linux or sold without an OS might provide support for ext
Maybe one day, Right?
Sent from my iPhone using Tapatalk
nick65go:
grub-mkimage is the key central for grub to build all other stuffs when needed.
For example, grub-[install,mkstandalone,mkrescue] all refer to the use of grub-mkimage, so once grub-mkimage is understood, everything looks easy to do.
grub-mkimage has 2 ways to "attach" a config file to its image :
option -c,--config=File (embed FILE as an early config)
option -m,--memdisk=file (embed FILE as a memdisk containing eventually config file)
Example of an embedded configuration for a UEFI boot from "ISO-type" inside:
--- Code: ---set pager=1
root=(cd)
configfile (cd)/boot/grub/grub.cfg
--- End code ---
The memdisk is a virtual disk device viewed by grub, having a tarfs filesystem; the various modules sitting there are "ready for use", meaning they can be loaded by insmod directly. But they are not directly call-abled as "preloaded modules" as those in the options --modules="blah blah...:" (the last ones are similar to drivers loaded in initramfs in Linux OS)
sample Optional miniHDD GrubBIOS
--- Code: ---grub-mkimage.exe -v -o grubBIOS-core.img --format=i386-pc --prefix="(hd0,msdos1)/boot/grub" biosdisk iso9660 part_msdos fat
--- End code ---
or the equivalent for UEFI64:
--- Code: ---grub-mkimage.exe -v -o grub_x64.efi --format=x86_64-efi --prefix="(hd0,gpt1)/boot/grub" part_gpt fat
--- End code ---
EDIT: FYI, my UEFI-HDD bootloader [1grubx64-gpt.efi] has 118 KB (121,344 bytes) ;)
EDIT2: my BIOS boot (for Virtual machine) with almost all modules included (grub202-i386-cdrom.core) has 376 KB (385,024 bytes).
These are to prove that we DO NOT necesary need the folders i386-pc, neither the x86_64-efi; we need just the main bootloader and eventualy a configuration file (grub.cfg), and even the configutarion file can have an arbitrary name, because we will ask for it using grub-directive "configfile bla-bla-file".
PDP-8:
Ah, interesting!
Leaning forward from my rocking chair and shaking my fists, I'll go OT for a sec and stop. :)
This is all great stuff - but I think loses many, even the TC diehards, if the uefi-only stuff doesn't boot straight away and you have to mess around with custom grubs.
Two analogies - in the old days, one just popped their DSL cd into the machine, booted and went to town for the most part.
Prior to that, one used kermit to download binaries, and used an ms-dos utility, RAWRITE.EXE to create boot/root/userland floppies.
But they didn't have to get their dos C-compiler out, and create rawrite.exe on their own.
Ok, bad analogy perhaps, so I'll duck out for awhile...
labeas:
The forum statistics confirm the wave of <anti-M$-lockout> needs.
My recent attempt, based on the 2015 article:
"Howto make a legacy bios/uefi dual boot usb stick with grub2"
worked for the TC64 grub-entry, but not for the <core32bit>.
While searching for the Wifi hardware/firmware I destroyed one
partition, and before reinstalling, I need to install Ver10.x
on this laptop, currently runing Ver7.2.
This: in order to better fetch the Ver10.x files for the.
<uefi laptop>.
I can't remember how I initially installed Ver7.2 TC64 ?
The online "Installation" instructions are confusing !!.
> "The guide assumes you've either booted the CorePlus CD, or have
> installed the tc-install extension (tc-install.tcz)"
No! No CD hardware available.
How can tc-install.tcz be used *BEFORE* TC is installed & running ?!
It was quiet a problem to get Wifi working on the TC64:Ver7.2.
If I have the URLs:
then ver7.2 can fetch the required files for installing Ver10.1.
Perhaps I used YUMI...rufus...to install vers7.2 ?
Please advise howto:
1. install current TC64.
2. are instructions of <2015 article> still valid?
PS..
I appreciate the <tabulated, instead of chatty-format: instruction-list>
given earlier in this thread.
PDP-8:
labeas - I really think you are a candidate for using YUMI-UEFI multiboot for your project. There is the original YUMI, and the more recent YUMI-UEFI. I would choose the newer version for your Aptio.
You've already paid your Microsoft-tax, perhaps many times over your lifetime like all of us purchasing computers with dos or windows pre-installed. What better way to get back some of your investment by using a GPL'ed windows tool to get your troublesome setup going.
I've gone into depth about it here:
http://forum.tinycorelinux.net/index.php/topic,23010.msg143982.html#msg143982
But if you want the checklist approach, here it is.
1) Download the Tinycore iso(s) you want to boot from the Windows box.
2) Use YUMI-UEFI to burn the iso(s) to your usb stick.
3) Copy and paste the cde directory to the root directory of your usb stick.
4) Rename this cde directory in the root, to tce.
5) Find the grub.cfg file in the TinyCorepure64 directory. Don't mess with other grub files earlier in the path, as they pertain to YUMI itself.
It can be found here:
/mnt/sdaX/multiboot/TinyCorePure64-10.1/EFI/BOOT/grub/grub.cfg
6) Change the reference in the TC and TCW subsections from "cde" to
tce=LABEL=MULTIBOOT
This should serve as a guideline if you want to run the 32 bit version, although I have not done so.
Note that I don't use the multiboot feature. But if you do, you may not want to share a tce directory. In the case you are multibooting say 64 bit and 32 bit, you might want to have tce64 and tce32 directories in the root. Change your grub.cfg to point to those accordingly.
Of course, the stick is fat32. NOT exFAT, but fat32. Maybe you are ok with that. If not, then you'll have to dig harder with a manual install.
Maybe this will relieve some of the problems. And don't forget - back in 1992, I had already purchased MS-DOS many times over retail, and used RAWRITE.EXE inside dos to create the boot/root/userland floppies for Slackware. Trying to remember if I paid for mbasic-80 on my CP/M machine or if it was part of the "tax" even back then. :)
So I'm not defending Microsoft and their actions, but I am merely saying, you like most of us, have already paid $$$ in ms taxes. Maybe make use of it with a clearer conciousness with YUMI?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version