TinyCorePlus not loading and gets stuck on the “ABSOLUTELY NO WARRANTY” screen.

[Oarin]

It says it’s about to load extensions and then it just gets stuck. I’m booting from a usb stick on a UEFI computer running windows 11 so I changed it to boot in csm mode which seemed to work because the iso actually loaded. Every time I try to do this with TinyCorePure64 on Ventoy or the same with Plus and also with Rufus or with Balena Etcher or anything it always gets stuck this same way. I have no idea why and I’m not that good at Linux so don’t just say dd or something like I see in other posts and think that I know what you mean. :(

[Oarin]

I think I’m going to use puppy Linux instead because I’m not on a 1998 PC and I is easier to set up for noobs like me. Maybe I’ll try tiny core in the future. So long…

[PDP-8]

Consider giving it another try with this method with the ultra-moderm uefi only machine:  (with secure boot off of course).

For lurkers too..

Juanito has kindly provided the necessary uefi boot image with ONLY TinyCorePure64. You can find it in the "Other Ports" download area. 32-bit versions, and CorePure64 will not work, ONLY TinyCorePure64 has the uefi support baked in.

However, this does not mean that "dd" or any other dd-like utility (Rufus, etcher, etc) will create a bootable TC stick, even if they don't complain about the process.  This is not a bug.  Let's move on.

What WILL work is to take the heat off the devs, and use *the latest* Ventoy to create a bootable uefi stick, and then you copy the TinyCorePure64 iso onto that.  Do not use a crusty old version of Ventoy.

When you have successfully booted, we do what we used to do in the bootable-cdrom days of running

Code: [Select]

tce-setdrive
in the terminal, and point it to a writable store.  Works as expected.  This can be your existing distro's hard drive, another usb stick, whatever.  I do not recommend pointing to the Ventoy stick itself unless you are absolutely sure of what you are doing, and prepared to play with permissions and all that.

RUFUS note!  Even as much as I like Rufus for more than just Linux, we know that the the dd or iso mode of burning it presents, won't actually work with super modern 64-bit uefi TC.  Let's use it for something else!

If you have Rufus on board, one really neat thing it can do is create ext2 / ext3 filesystems on a stick, even though that is of no use to Windows.  This makes a great "data drive" stick for you to point the tce-setdrive to!  If you have a blank stick you want to make the data-disk inserted, don't mess around with burning.  Use the drop down for "NON BOOTABLE".  Further down, you can pick the ext2 or ext3 filesystem.  See bikesheds about it elsewhere, I use ext2.

So there you go - if you are coming from ultra-modern uefi-only Windows machine, having both the *latest* of Ventoy (for the TinyCorePure64 iso only!) and Rufus (not for the burn, but for the handy way to make an ext2 data stick - the so-called "non bootable" option), is a load of fun to get you started.

Hope this helps.

[gadget42]

with reference to "secure boot" i was reminded of a relatively recent liveslak post by AlienBob(Eric Hameleers) that is worthly of sharing:

https://alien.slackbook.org/blog/liveslak-1-8-2-re-adds-secure-boot-support/

also for the convenience of future readers and with respect to PDP-8 note regarding using a "recent Ventoy" the current version at post time is ventoy-1.1.05 released 20250224 as per:

https://www.ventoy.net/en/index.html

and while i still have time to modify this post, here is another by AlienBob that may interest some:

https://alien.slackbook.org/blog/migrating-my-infrastructure/

hey, the more you know!

20250620-0405am-cdt-usa-modified: added content and link

[PDP-8]

Without getting too far off track - Porteus (and PorteuX and Nemesis) is a small distro based on slackware current and/or release, but has a similar issue.  People have been raised on "burning the iso with dd", do that, and fail to boot Porteus.

The actual installation is very simple, but nobody reads the README.  (mount the iso, (simple double or right-click these days), copy the folders to the target drive.  From the target drive, run either the windows exe or the linux sh file as root to install the bootloader and you have your writable stick.  Done.  In some uefi cases, even that is not always necessary.

In fact, Gparted Live offers both an iso AND a zip file.  I use the zip file method (similar to above) to make those.  The docs make it seem harder than it needs to be, so those raised on dd-burning only, don't even know that this can be done.

Anyway, just a way of saying not to blame TC for the way things are done.