Microcore extensions do not get loaded

[hunter.seeker]

I'm using the latest microcore release (2.11.2) and have found that any extensions I place in the /tce/optional directory do not get loaded at startup. It seems that autoscan() takes too long to find and mount the partition so the rcS script cannot find the tcz files to mount them. Once booted, I can run the tce-setup command and it has no problem mounting the partition and find the tcz files. I've also found that pausing the rcS script just before the extensions part of the script runs (using read -p) works as well.

For my purpose, I require the tcz files to be automatically loaded at startup and cannot use the read -p command.

Ideally this should be fixed such that a pause is not required as well. Any thoughts? suggestions?

[maro]

I assume you are using a USB pendrive and as the FAQ indicates you will have to use a boot code like "waitusb=5". This is to ensure that the system waits long enough for the auto-detection of the 'tce' directory.

I give you full credits for your "detective work" on the system WRT finding the function and the use of 'read -p'. But this issue has come up so often in the forum that you could have saved yourself some time by doing a search here.

BTW there was an enhancement included in TC 2.11 that makes this process even more efficient (when using a LABEL). Have a read at this thread and the one it references to find out more.

[hunter.seeker]

I am experimenting with using it as an embedded x86 system with minimal storage; its being used on a hdd, not a pendrive. Right now I'm using a vm to remaster, so when I make an 'image', I create a partition on a small VM disk, copy the necessary files (kernel and filesytem gz after remastering), create a bootloader on the image and dump the image to the target system.

In this mode (using an hdd) do I still have to use the waitusb command or is there something funny going on here?

[batnas]

I am experimenting with using it as an embedded x86 system with minimal storage

Cool. Me too. Actually I am running a wabserver on TC eith only 300 MHz,....

In this mode (using an hdd) do I still have to use the waitusb command or is there something funny going on here?

no

[curaga]

Despite its name waitusb can be used to wait for any other slow devices as well. If your hdd spins up slow, using waitusb=5 is worth a try.

[hunter.seeker]

Thanks for the help everyone. The waitusb does work and LABEL is even better. There might be something with the system that causes a slow mount, but this works for me.