Tiny Core Base > Release Candidate Testing
tinycore_v2.8rc1
Machete:
VirtualBox 3.1.2r56127 (win64, win32, linuxMint 5 x86 - & Debian 5.0 x64 hosts)
I've just been booting with the raw .iso, which produces the ACPI errors.
I rebuilt the .iso using the non-UPX'd bzImage, and it works fine.
Is there any more information about my setup that would be useful? Debug logs, dmesg output, the VirtualBox .xml file, etc?
tclfan:
--- Quote from: bmarkus on January 05, 2010, 03:29:57 AM ---I kindly ask not to use upx'ed kernel. Gain is musch less than trouble caused.
--- End quote ---
I am an end user, not a contributor, so I do not have much saying in decision making process here. However I would like to agree with Bmarkus that the compressed kernel appears not worth of all the compatibility issues... If this community experiences quite a few issues linked to compressed kernel on such a small spectrum of hardware, this extrapolates to me that it is not expected to be behaving reliably on wide range of hardware. Instead of sure boot on most any machine we will be facing a 'maybe it will work' situation when we stick this CD in a new machine...
What is so compelling that we are gaining with this compressed kernel except a little space saved?
bmarkus:
--- Quote from: bmarkus on January 06, 2010, 01:52:49 AM ---
Hopefully I will have access to another notebook with the same type where I can test it to exclude unique issue with my machine.
--- End quote ---
Unfortunately couldn't test as machine was moved to country side :(
roberts:
After feedback from this thread and Team discussion, it has been decided to drop dropbearmulti from base. It is not needed or used to bring up the system. By dropping it, as was pointed out, eases the use of openssh, a more fully featured version.
Navigation
[0] Message Index
[*] Previous page
Go to full version