Tiny Core Extensions > TCE Tips & Tricks
How to make a legacy bios/uefi dual boot usb stick with syslinux
gwalther:
I am going to try and create a dual boot USB stick following your instructions. What size do you recommend making the three partions, especially partition one and two?
coreplayer2:
Hello
My whole point about dual EFI/MBR boot loaders is their performance hit is considerable. So, unless the dual boot is really necessary to boot some old device i'd go all out with EFI install ONLY! The performance boost with GPT/EFI in my test environment is substantial.
PDP-8:
I'll second what coreplayer2 says - UEFI only (no csm) is a vast speedup.
BUT, the catch is that on another UEFI-only machine I have (Intel Computesticks and now my 2 year old Acer Aspire 1 netbook/laptop chromebook wannabe) may be playing with the UEFI specs as seen above. I haven't figured out where that one is going wrong.
I haven't tested as thoroughly with the Acer like Hamak and others have, but in the interest of time I can bring TC up immediately on both of these, with the YUMI-UEFI burner and it's bootloader.
Kind of a bummer - by the time many might figure out that their own machine is not following specs, they may just lose interest in getting TC running. Or resort to using a "fat" bootloader (well compared to TC's one) to get the job done.
I mean figuring out all this bootloading quirks to get TC running might be fun, but for me, that fun has waned - hency my reliance on 3rd party bootloaders now. Maybe I'm just in a bad mood, but I wouldn't mind a plump TC bootloader. :)
polikuo:
--- Quote from: gwalther on June 28, 2019, 12:53:08 PM ---I am going to try and create a dual boot USB stick following your instructions. What size do you recommend making the three partions, especially partition one and two?
--- End quote ---
Hi, sorry for the late reply. :P
It depends on your habits.
FYI, in my case above, I used an old 8G pendrive.
The sizes are roughly 4G, 512M, 3.5G in order.
4G for file sharing, FAT32.
512M for bootloader, FAT32 EFI.
3.5G for TC stuffs, ext4.
Note that, the first M$ partition is totally optional. ;)
It's for file sharing between the operating systems.
Since M$ only accept one partition for an USB flash drive,
you can't access files in other partitions.
The M$ policy usually assign a letter to the first partition on the USB.
Thus, the first partition exist.
If you don't need to share files between the systems,
then you could omit the first partition and merge partition 1 and 2.
About the file sharing, here's a brief example.
Say, I'm learning C language.
I'm currently working with it under linux system.
In order to test it out on M$ system,
I can just put it in the first partition of the USB,
and reboot my PC.
When the system comes up,
I can load and edit the file normally.
labeas:
This looks interesting.
I've had problems trying to install <grub2-forUEFI>.
Since I'm still using Ver7.2 of TC64: I thought to update to ver10,
while installing for the newProblematic UEFI laptop.
Since oldLaptop:V7.2 boots with no problems, and good font-size etc. I
thought to start from a known good state.
Could I use these existing partitions of my "Ver7.2 of TC64 BakUpStik",
and just loses the "MBR",
and rename the dirs which I want to keep for BakUps?
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 2048 4689547 4687500 2.2G c W95 FAT32 (LBA)
/dev/sdc2 4689548 15630335 10940788 5.2G 83 Linux
--------------
So far I've had no explanation of how syslinux & grub can have different
"kernel and initrd" files: eg: isolinux.cfg = 2 files:
KERNEL /boot/vmlinuz64
INITRD /boot/corepure64.gz
but, *2/EFI/BOOT/grub/grub.cfg = 3 files ?! :
linux /boot/vmlinuz64v10 ...
initrd /boot/corepure64v10.gz /boot/modules64.gz
What is the modules*.gz which syslinux doesn't need ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version