remastered corepure64.gz has extensions & onboot.lst but does not load

[wlarip]

Greetings:

I remastered corepure64.gz with the necessary scsi entensions and some other goodies plus the onboot.lst into the unpacked tmp directory of corepure64.

The repack was successful. The system boots and the extensions are in the booted /tmp/tce/optional directory but they do not load on boot. They will load with tce-load -i 'extension.tcz'.

Any tips?

TIA

[polikuo]

the extensions are in the booted /tmp/tce/optional directory

It would be a better idea to unsquash it along with its dependencies directly to the root of your remastered corepure64.gz
And then create empty files in the /usr/local/tce.installed/ directory to prevent reloading.

Assume that you are talking about scsi-KERNEL.tcz (scsi-4.8.17-tinycore64.tcz)
It does not depend on any other extensions.
So you won't need other extensions copied.
Also, make sure to add an empty file scsi-KERNEL (scsi-4.8.17-tinycore64) to /usr/local/tce.installed/

but they do not load on boot

You'll have to dig into the start-up scripts to get the answers.
My guess is that, by default /tmp/tce/optional is empty, thus the tceonbootload is skipped.

[wlarip]

much obliged.

[wlarip]

I tce-loaded scsi-4.8.17-tinycore64.tcz. After it installed , i copied the /usr/local/lib
directory structure into the extracted usr/local/lib preserving all links and doing a depmod on the extracted core directory.

the core_extract was remastered to corepure64.gz and booted. It looks fine but device discovery never kicks off. I'm guessing the tce-load does a modprobe to get the device to wake up.

if so, what's the method that prevents it from modprobing non-existant devices unless it's a device enumeration request?

If not, how does tce-load do it?

TIA

[wlarip]

unsquashed fs /usr/local/lib/modules from scsi-`uname -r` doesn't work either.

tc-load itself seems to be kicking device discovery.

interesting question.

[Misalf]

What if you add to your  /opt/bootsync.sh

Code: [Select]

/sbin/depmod -a
/sbin/udevadm trigger
?

[Misalf]

Or before repacking

Code: [Select]

sudo ln -s "$INPUT/usr/local/lib/modules/$KERNEL/kernel" "$INPUT/lib/modules/$KERNEL/kernel.tclocal"
sudo depmod -a -b "$INPUT" $KERNEL
where  $INPUT  is the directory you extracted core.gz into (f.e. "/tmp/core") and  $KERNEL  is the kernel version this core.gz is for (f.e. "4.2.9-tinycore").

[wlarip]

Exactly right.

I believe that is the difference between tci-load -wi and -wc.

Well played.

BTW, depmod -a on the extracted initrd doesn't work. Unresolved module symbols until the image is booted.

After that nirvana.

Thank you kindly.

[Misalf]

The  -c  switch makes tce-load copy the files to the filesystem in RAM and un-mounts the extension afterwards, rather than symlinking them and keeping the extension mounted.