Tiny Core Base > Release Candidate Testing
tinycore_v2.8rc1
roberts:
--- Quote from: Machete on January 05, 2010, 09:43:04 AM ---
--- Quote from: roberts on January 04, 2010, 04:49:48 PM ---
--- Code: ---Robert, just out of curiosity, what did you discover was wrong with the previous attempt to use the upx'ed kernel ?
--- End code ---
At the time, I did not have much in the way of equipment and virtual machines to test it, so I dropped it.
Since then the entire Team has been testing on various devices, isolinux, cdroms, virtual machines and could not get a failure. So perhaps the issue is directly related to specific hardware or BIOS. Therefore, as a Team decision, we decided to use the smaller kernel while offering the un-upxed version in the distrubtion file area.
--- End quote ---
Have they tried it in a plain VirtualBox "Live" session, just creating a virtual machine with all the defaults, except no hard drive? Every time I've tried it with these UPX'd kernels, just booting off the raw .iso, I get the same message from ACPI: "Unable to load the System Description Tables". Seems like the UPX'd kernels were giving some people running on real systems a headache, too.
If we're going for size and compatibility, I'd say we seem to be better off with a non-UPX'd kernel, rather than a compressed one.
--- End quote ---
I should defer this to one who has tested it. But I recall an update to the latest version of VirtualBox is required.
roberts:
--- Quote from: bmarkus on January 05, 2010, 03:29:57 AM ---
--- Quote from: roberts on January 04, 2010, 04:19:42 PM ---
* After much Team testing and input, the upx'ed kernel returns, prior kernel is in distribution files.
--- End quote ---
I was one of the victims in tha last cycle of of the upx'ed kernel on my ACER ASPIRE 5720Z notebook experiencing booting problems and random feezes. Now booting works fine after 8-10 tries, but still I see random freezes frequently when using 2.8rc1
As I remember I was not the only one. For sure we need the standard kernel and there will be otheres, not reporting it just simply throw away TC/MC after testing.
I kindly ask not to use upx'ed kernel. Gain is musch less than trouble caused.
--- End quote ---
Duly noted. It was a team decision to try it again and will ultimately be a Team decision before final 2.8
May I ask how is Tiny Core Installed on such device? Is not having easy access to the original kernel not satisfactory?
For the moment I will be making an incompatible hardware list. So far, one item listed.
If there are other, speak now.
maro:
I'm also one of those users that use TC on VirtualBox. Even running the latest version (VB 3.1.2, under XP) produces the previously reported error messages at the very start of the boot process:
ACPI: Unable to load System Description Tables
IO APIC resources could not be allocated.
These messages did not appear with TC 2.7. The respective "dmesg" output also shows some differences (which can be made available). As much as I can tell those differences are all related to memory layout and (virtual) hardware detection.
During the (so far rather light) use of 2.8rc1 I have only come across the following difference in behaviour to 2.7, which seems related to those error messages: The VM needs to be manually closed (i.e. "switched off") after the shutdown of TC. The same was previously not required, but IIRC was also seen with the first trial with the "UPX kernel".
All this is (so far) in my view not a real show stopper, since it's easy to live with this regression. But I guess only more testing will tell ...
bmarkus:
--- Quote from: roberts on January 05, 2010, 09:46:39 PM ---
Duly noted. It was a team decision to try it again and will ultimately be a Team decision before final 2.8
May I ask how is Tiny Core Installed on such device? Is not having easy access to the original kernel not satisfactory?
For the moment I will be making an incompatible hardware list. So far, one item listed.
If there are other, speak now.
--- End quote ---
USB install with UNETBOOTIN. For me it is not a problem to replace the kernel with older, recompile, repack or whatever needed. If I'm affected only I can manage. Question is, what is about others having the same problem, if there are any.
Hopefully I will have access to another notebook with the same type where I can test it to exclude unique issue with my machine.
Also would be good to find others in the community using ACER ASPIRE 57xx or similar machines.
alu:
i am also unable to boot mc 2.7 and tc 2.7 on an aleutia E1 with 128 mb ram and a SiS processor, getting the message:
IO APIC resources could not be allocated.
i did not test it with the new rc.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version