Tiny Core Base > CorePlus

Installing CorePlusOS is not working? Need help. (I am New to this distro)

<< < (2/2)

Sashank999:
Once have a look at this : https://www.zdnet.com/article/installing-linux-on-a-pc-with-uefi-firmware-a-refresher/
I used YUMI on my USB and it worked both on BIOS Laptop and UEFI Laptop.
TL;DR
1. Disable Secure Boot
2. Use YUMI and flash tinycore ISO with "TinyCore Option in the menu". Change to UEFI Boot.
3. Plugin and boot.

NewUser:
On Win10 you should be able to extract the core2usb zip file. What error do you get when extracting the zip? If your Asus laptop is 64-bit try CorePure64 instead of Coreplus.

PDP-8:
@NewUser - sorry, that won't work.  It is not a simple matter of being able to unarchive the burner tool.

The matter is that these tools, along with a simple unix "dd", will dutifully produce what looks like a CD onto a usb stick based upon the release iso.

The result is that modern uefi-only hardware, with secure-boot disabled of course, simply will not recognize or allow a CD - in whatever form - to boot.

The only recourse is to trick the iso into being a hybrid - using isohybrid upon the iso before using the tools, or dd.

@Sashank:
That article is more confusing than helpful.

I've documented using Yumi-UEFI here in the forum.  To recap:  the ops uefi *ONLY* hardware would need tinycore64.  Yumi-uefi, unlike simple burners totally rewrites the iso onto a fat32 formatted stick.

But it still won't boot.  Why?  Because YUMI-UEFI introduces an error into the grub.cfg file.  It is up to the user to spot not only the proper grub.cfg amongst a forest of multiboot bootloader chains on the new stick, but correct the glaring error introduced in the filepath and fix that first.

But wait - there's more!

Once that error is fixed, one STILL needs to do things to make the stick usable.  Like move the CDE directory to the root directory of the stick, and rename it TCE.

(If you don't, then the stick will boot, but with a totally foreign filesystem structure, it can't find the CDE directory and you end up at the cli every time.)

Ideally, one should then follow up by doing a blkid of the stick, and putting that UUID back into the TC grub.cfg file.  If you know where it is in the first place.

Oh but did I mention that the Intel-NUC can stay in uefi-only mode, but has an option to enable "optical boot" without having to resort to legacy/csm?  That's not the ops machine.

This is what the op with his current laptop would have to do.  If one is not familiar with linux, and TC in general, there are plenty of opportunities to shoot oneself in the foot.

With the variety of hardware out there, and the plethora of blogs and articles that are lengthy, but leave out important details, one can see why supporting modern machines with hybrid iso's by devs would be a total nightmare.  If one knows what they are doing - fine.  If not, I think a different distro is called for.

Basically, TinyCore being a toolkit, rather than a distribution, is not something someone new can TL;DR and wing it.

Navigation

[0] Message Index

[*] Previous page