Install instructions are bad

[Scorp1us]

After downloading, writing and booting from CorePlus-current.iso,

Following along at:
https://distro.ibiblio.org/tinycorelinux/install.html
0. I boot to tinycore with install
1. I choose to download the 64 bit version.
And it goes fine until step 5.
Sometimes I see step 5, sometimes I don't - despite always using the CorePlus image.  It seems to vary on if I download the core or if I select it off the stick.
Of note, there is no 64bit kernel on the image.

6. I set the directory to /mnt/sdb/cde
7. This goes well, when I have network, otherwise it fails and I can't next, back or retry and I have to start from 1 again in a new invocation.
Also, it seems the primary mirror is down ( get a MD5 validation error) , I have to launch Apps and select fastest mirror, then go through the whole process again.

Then when I reboot off the HD (64bit) I get:
/usr/bin/startx: line 12 mcookie: not found
failed in wairforX
tc@bocx:~$

But it seems to work in 32bit.

How is this supposed to work? I used TCE like 10 years ago and it was wonderful. This is... not working as wonderfully.

How can I get a 64it TCE install?

[Scorp1us]

UPDATE:

in TinyCorePure64-8.0.iso,

the mcookie error is happening because /usr/bin/mcookie links to /tmp/tcloop/Xlibs/usr/bin/mcookie

but that is not a valid binary. the `file` command is missing, but when I run ldd on it I get:
$ldd mcookie
/mcookie: error while loading shared libraries: ./mcookie: wrong elf class: ELFCLASS32

Update, I also tried v9.0...

I'm on a Intel® Celeron® Processor G3900, so it is 64bit.

[Juanito]

You need a separate set of extensions for CorePure64 - are you sure that you're not loading the 32-bit Xlibs extension instead of the 64-bit Xlibs extension?

[Scorp1us]

Absolutely. The TinyCorePure64 boot iso won't even start X.

[Juanito]

My point was that having used the 32-bit CorePlus to install the 64-bit CorePure64 - once you've booted CorePure64, you will need to ensure that you are using a /tce folder containing 64-bit extensions, which is usually done (for example) by having a /tce and a /tce64 folder.

The fact that ldd showed mcookie was 32-bit means that you have the 32-bit Xlibs extension loaded instead of the 64-bit Xlibs extension

Note also that TinyCorePure64 uses Xfbdev by default, but it might be easier to use Xorg-7.7

[polikuo]

The "Download From Internet" checkbox is a test function,
which downloads the latest kernel & initrd (vmlinuz{64}, core{pure64}.gz)

Since you cross install a different architecture, you'll need a different set of extensions.
The "Install Extensions from this TCE/CDE Directory" options is for those people, who have many different installations on their hard drive, to choose their local source.

BTW, most extensions in the iso are usually outdated, it's best to run "tce-update" right after an installation.

[Scorp1us]

Thanks all! I'm still at a loss though why the TinyCorePure64 iso image (that I downloaded to install with) won't boot into X. Version 8 and 9 didn't work so I am wondering what is going on?

Also, it is confusing to in one instance, select a tgz for the core, and then a directory for extensions. I think I'm thrown off by two things:
1) why the cde directory does not list files as confirmation that I'm in the right forectory or
2) whyt he cde directory is empty?

If someone could tell me how to get Pure64 working (burn XXX.iso, boot off it, installer boot menu item, etc) That'd be great. as it stands now the Pure64 iso doesn't go into X and crashes with the mcookie error. Since versions 8 and 9 do this, I'm left to assume something is wrong with either the images or my system?

[NewUser]

When you boot CorePlus do you choose the waitusb=5 entry?

[curaga]

If you have an installation on a disk or usb stick, the CD will find it and use it over the extensions on the CD.

[Scorp1us]

When you boot CorePlus do you choose the waitusb=5 entry?

No, but per http://forum.tinycorelinux.net/index.php?topic=20984.0 I shouldn't have to?

[coreplayer2]

Thanks all! I'm still at a loss though why the TinyCorePure64 iso image (that I downloaded to install with) won't boot into X. Version 8 and 9 didn't work so I am wondering what is going on?

More likely the issue stems from a misunderstanding and technique.
As explained earlier “TinyCorePure64” when booted from a CD will boot into Xfbdev not not Xvesa, if for some rare reason Xfbdev will not perform as expected try installing to a USB thumb drive and don’t forget to use the waitusb boot code or some variation of this boot code (see the Core Book fir more info).

Also, it is confusing to in one instance, select a tgz for the core, and then a directory for extensions. I think I'm thrown off by two things:
1) why the cde directory does not list files as confirmation that I'm in the right forectory or
2) why the cde directory is empty?

CDE directory is used only when booting from a CD.  TCE directory is used for all other installations.  If (as Curaga has suggested earlier) you have installed TinyCore to a USB be absolutely sure the CD player draw is empty when booting from another source like a USB, otherwise the extensions from the CD will be found and used regardless of a TCE directory installed on your USB thumb drive or HDD.

...as it stands now the Pure64 iso doesn't go into X and crashes with the mcookie error. Since versions 8 and 9 do this, I'm left to assume something is wrong with either the images or my system?

You know...   the system will never boot as expected if you continue to mix up x86 & x86_64 directories and/or files incorrectly.





Sent from my iPhone using Tapatalk

[coreplayer2]

When you boot CorePlus do you choose the waitusb=5 entry?

No, but per http://forum.tinycorelinux.net/index.php?topic=20984.0 I shouldn't have to?

Please understand this, all USB installations should use the waitusb bootcode or some variation of this depending on your specific setup.   To be sure your system is booting using the correct TCE directory I would use the drive's UUID code and specify the TCE directory path as well.  see http://tinycorelinux.net/book.html for more..

[Scorp1us]

Thanks for that info.

So I was going to video my process, in that, I got a different result today than previously, but I'm still lost.

1. I used Etcher to write TinyCorePure64-9.0.iso to a USB stick
2. It actually booted into X GUI time. (previously I would get an mcookie error)
3. I loaded the GUI installer and installed TCE. (See Screenshots)
4. I rebooted off the HD.
5. I only got a command line.

Which still leaves me with the question: How do I get a 64bit version of TinyCoreLinux to boot into X after installation?

I *think* my problem with mcookie previously was because I originally installed a 32 bit version of TCL. What I did differently was that I formatted I for ubuntu for the weekend, and when I installed it this morning, it had no TCL directories? Could that be it? Why wouldn't the 64 installer overwrite the 32 stuff?

[coreplayer2]

Thanks for that info.

So I was going to video my process, in that, I got a different result today than previously, but I'm still lost.

No need..  But allow me to remind you to please read the Corebook so you have a better understanding of Tinycore's features, I guarantee you'll learn a lot and find answers to most of your questions..  http://tinycorelinux.net/book.html   

reading the book might also help learning the appropriate nomenclature, just saying as it might be easier to help you when correct terms are used is all..

1. I used Etcher to write TinyCorePure64-9.0.iso to a USB stick

What is Etcher?

2. It actually booted into X GUI time. (previously I would get an mcookie error)

Of course..

3. I loaded the GUI installer and installed TCE. (See Screenshots)

By TCE I assume you mean tinycore x86_64.  Because TCE means Tiny Core Extensions

4. I rebooted off the HD.

HD. Do you mean new USB install ?

5. I only got a command line.

Which still leaves me with the question: How do I get a 64bit version of TinyCoreLinux to boot into X after installation?

First, show here output of

Code: [Select]

showbootcodes

I *think* my problem with mcookie previously was because I originally installed a 32 bit version of TCL. What I did differently was that I formatted I for ubuntu for the weekend, and when I installed it this morning, it had no TCL directories? Could that be it? Why wouldn't the 64 installer overwrite the 32 stuff?

This is common problem not using proper boot codes and having various installations present on same pc.  eg: booting USB install with a tinycore cd in the cd drive, etc. etc.

[polikuo]

Which still leaves me with the question: How do I get a 64bit version of TinyCoreLinux to boot into X after installation?

The latest version is 9.0
Downloading corepure64.gz
Downloading vmlinuz64
...

You choose to download the latest build from the internet.
By default, that means you'll get a KERNEL (vmlinuz64) and an INITRD (corepure64.gz).
You have to choose a path to a TCE/CDE directory if you want to copy the packages.
Otherwise you get a "base" installation.
Since you somehow set your CDE directory to /mnt/sdb/cde/..,
which actually points to /mnt/sdb/
The installer couldn't find any tczs there, thus ignoring the request.