So I made a super basic installation (with tc-install from within TinyCore). Basically it's only Core + some extensions that I wish to use, which are supposed to be loaded at boot time. If I boot up the resulting image in VirtualBox, it works just fine, it loads my extensions on boot. But if I boot from
the exact same image on my target hardware, it simply doesn't load my extensions. But the strangest thing is that if I manually load the extensions with "tce-load -i <filename>" after the OS has booted up, they work! They get loaded no problem. They only fail to load automatically at boot time. But again, they do load at boot time if I use the same image file to boot in VirtualBox, which I don't understand. My "onboot.lst" file contains the list of extensions to load, and I specified the "tce" switch correctly when using "tc-install". I uploaded the image files to Google Drive, so you can take a look yourself:
https://drive.google.com/file/d/0ByZv2ebI0aO4aF9fdWU5c0htVWc/view?usp=sharingThere are two files inside:
"tc_vbox.vdi" is a VirtualBox-ready hard disk image. Just attach it to a VirtualBox machine, and boot from it.
"tc_raw.img" has the exact same contents, but instead of a VirtualBox image, it's a
raw image file. Copy it with a tool like "dd" to any storage device, and you should be able to boot from it. Note: you might have to run "sudo fsck.ext4 /dev/sda1" after the first boot on an actual machine to fix the partition.
As you can see it loads my extensions without any problem at boot time (you can test if they were loaded by trying to launch nano, as it's one of the extensions). Everything seems to work nicely in VB, but whenever I boot the same thing on my actual target machine, it fails to load my extensions.
But again, I AM able to load them manually after the OS has booted. This is the strange part
Btw, my target machine is a 266Mhz embedded x86 board, with 128MB of ram, so it's not the fastest thing in the world. Maybe this is some sort of a timing issue? I have no idea.
I attached an image that shows what I have in my extensions directory. Everything seems normal there.