Tiny Core Base > Release Candidate Testing
tinycore_v2.6rc2
Machete:
Booting straight from the .iso, in VirtualBox, same configuration as with 2.5, and I still get the "ACPI: Unable to load the System Description Tables" message. System comes right up, though, and seems to be fully functional, unlike RC1, that took nearly 5 minutes just to get past the ACPI message.
Is there any additional information you would like about the configuration, dmesg, etc that would be of assistance? 2.6 is the first release (RC or otherwise) to produce an error on this box, I'd like to help fix that if I can.
robc:
Not sure if this is from fltk or flwm, but whenever a new window opens with appbrowser my mouse cursor and window focus is moved to that new window. I've noticed this before in previous versions. This also happens with the control panel, but not wbar, so probably with fltk?
This is more of an annoyance then a bug, especially when loading extensions with many deps such as compiletc from appbrowser. Would it be possible for the new windows to not take the user's focus so the user can do other work while waiting?
robc:
Here is a bug with appbrowser. Instead of saying an extension has already been downloaded it displays a wget error:
--- Quote ---Error: wget: server returned error: HTTP/1.1 416 Requested Range Not Satisfiable on sed.tcz
--- End quote ---
How to reproduce:
1. "Download Only" sed.tcz through appbrowser
2. Try to "Download Only" sed.tcz again
bmarkus:
--- Quote from: Jason W on November 18, 2009, 09:24:57 AM ---To me it sounds like you may have some bad RAM, that is often cited as a cause of system freezing. If you have not already, it might pay to run memtest on that machine just to be safe.
The kernel image has been upx'd in this RC.
--- End quote ---
After 8 hours running Memtest-86 v3.5 (Pass: 10) no error found. It will run for longer time of course....
gerald_clark:
CPU overheating is also a common reason for computer lockup.
This is especially a problem with laptops that have small fans that
may not be properly managed by the kernel.
Check your BIOS to see if you can control the fan, or do a overtemp shutdown.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version