Tiny Core Base > Release Candidate Testing
Core v16.0beta1
Rich:
Hi CNK
--- Quote from: CNK on March 24, 2025, 08:06:29 PM --- ... but probably an illegal instruction. ...
--- End quote ---
An illegal instruction usually causes the system to halt.
--- Quote --- ... Replacing the TC15 vmlinuz file with the TC16 one causes the above behaviour. ...
--- End quote ---
That kernel can't load any of the drivers from that HDD.
There was a recent thread about insufficient RAM with newer kernels:
https://forum.tinycorelinux.net/index.php/topic,27458.0.html
CNK:
--- Quote from: Rich on March 24, 2025, 08:52:15 PM ---
--- Quote from: CNK on March 24, 2025, 08:06:29 PM --- ... but probably an illegal instruction. ...
--- End quote ---
An illegal instruction usually causes the system to halt.
--- End quote ---
I'm not sure in this case because it's before the kernel has properly started up (before the dmesg messages start). The behaviour might be different at that stage. It's probably before or at the beginning of the start_kernel stage as described here.
--- Quote ---
--- Quote --- ... Replacing the TC15 vmlinuz file with the TC16 one causes the above behaviour. ...
--- End quote ---
That kernel can't load any of the drivers from that HDD.
--- End quote ---
Nah, it was booting to the TC16 rootfs.gz/modules.gz unpacked to a HDD, and the newer laptop runs off there fine. From earlier misadventures recreating my set-up after my HDD disaster I know that the kernel doesn't actually mount the root= partition (or fail to) until a good way later in the boot process than where the sudden reboot happens, so I just mentioned the vmlinuz file becuase loading things from the root filesystem isn't really relevant at that stage.
--- Quote ---There was a recent thread about insufficient RAM with newer kernels:
https://forum.tinycorelinux.net/index.php/topic,27458.0.html
--- End quote ---
TC15 does boot in 16MB RAM with my HDD install configuration, it's not the same as running in the usual tmpfs. I'll see if I can catch the last boot message on video...
Rich:
Hi CNK
You said that you unpacked rootfs.gz and modules.gz to the HDD.
The TC16 vmlinuz will accept the rootfs. But if needs any drivers
(kernel modules) for the 486, it won't load them because the
module version won't match the kernel version.
--- Quote from: CNK on March 24, 2025, 11:17:13 PM --- ... TC15 does boot in 16MB RAM with my HDD install configuration, ...
--- End quote ---
Maybe TC16 needs more RAM.
CNK:
Turns out the last messages that flash up are just normal before the kernel starts:
Specifically they come from misc.c in the kernel sources. Converting the hex in kernel_total_size/needed_size it says it only needs 12.9MB for the kernel. Once it jumps to that main kernel code the PC reboots before any other messages are shown. Well before loading modules (which are correct for kernel 6.12.11-tinycore anyway, I just didn't mention switching them as well as vmlinuz the first time).
I might try on a Pentium 1 PC with more RAM to see if there's trouble booting there as well.
Rich:
Hi CNK
Does your BIOS reserve any RAM, such as for video for example?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version