08-09-2024, 11:48 AM
It goes deeper.
The problem seems to exist in the main installation too. I can now get the system to partially boot, but even /bin/dash suffers from the same fate. Replacing that with the statically linked busybox (linking /bin/sh to /bin/busybox instead of /bin/dash) lets me get a bit further into the boot sequence, but still things are very, very, broken. For a start, I can't load any kernel modules because of this "Value too large for defined data type" problem.
I don't get why it's only on this hardware that it's showing the problem. In a VM, or in a similarly specc'd desktop computer it's perfectly fine - just not on this Toshiba laptop.
The problem seems to exist in the main installation too. I can now get the system to partially boot, but even /bin/dash suffers from the same fate. Replacing that with the statically linked busybox (linking /bin/sh to /bin/busybox instead of /bin/dash) lets me get a bit further into the boot sequence, but still things are very, very, broken. For a start, I can't load any kernel modules because of this "Value too large for defined data type" problem.
I don't get why it's only on this hardware that it's showing the problem. In a VM, or in a similarly specc'd desktop computer it's perfectly fine - just not on this Toshiba laptop.