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:

Error: wget: server returned error: HTTP/1.1 416 Requested Range Not Satisfiable on sed.tcz

How to reproduce:
1. "Download Only" sed.tcz through appbrowser
2. Try to "Download Only" sed.tcz again

[bmarkus]

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.

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.

[bmarkus]

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.

What? Why all other OS's including TC 2.5 and 2.4, 2.3, .... are running fine for a week or more time continously on max CPU speed and below 55 C except MANDRIVA 2010 and TC 2.6rcx? Definitely it is not a heat problem, as freeze happens immediately where CPU and all the system is cold. If you run 2.5, 2.6, 2.5, 2.6, ... one after the other 2.5 runs while 2.6 freeze. Also, when MANDRIVA 2010 heated the system I recognized it by fingers touching the housing and not by the errors running it.

[bigpcman]

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.

What? Why all other OS's including TC 2.5 and 2.4, 2.3, .... are running fine for a week or more time continously on max CPU speed and below 55 C except MANDRIVA 2010 and TC 2.6rcx? Definitely it is not a heat problem, as freeze happens immediately where CPU and all the system is cold. If you run 2.5, 2.6, 2.5, 2.6, ... one after the other 2.5 runs while 2.6 freeze. Also, when MANDRIVA 2010 heated the system I recognized it by fingers touching the housing and not by the errors running it.

Most freezes as you well know better than I occur due to code being corrupted as a result of self modification (stack overflows) or improper execution (memory leaks). I doubt you will find a memory hardware failure. More likely will be a driver that is acting up. Perhaps you could disable hardware peripherals in the bios as a test.

[fisher]

Tinycore 2.6rc2  Base norestore boot  code gives error  ACPI: Unable to load the System Description Tables".   USB doesn't seem to be recognized at any time under 2.6rc2.   Touch pad works after xsetup.  USB mouse never got working.  My laptop seems choppy and sluggish.  With my normal boot code the extensions don't load.  They should be the 4096 type.  I updated them last night.

Running tinycore2.5 presents no problem.  I have a MSI U100 with compiled wireless driver.

[Jason W]

Has anyone that is having issues tried using 2.5 with the 2.6 kernel?  That would help narrow down if it is the kernel image itself as we have tried the opposite.

[fisher]

Has anyone that is having issues tried using 2.5 with the 2.6 kernel?  That would help narrow down if it is the kernel image itself as we have tried the opposite.

I tested the 2.6rc2 bzImage with 2.5.  I still get  AE_NO_ACPI_ unable to load the System Description tables error.  Also a PNP bios dev node error while booting.

Extensions in tce seem to load.  I can.t get wireless to work.( rtl8187se  works with 2.5) 

USB mouse moves very erratically.   Touch pad works. 

cpufreq gives cpu unknown or wrong cpu.  Conky shows 0 degrees for cpu.

[Jason W]

Thanks.  If 2.5 and it's kernel pose no problem, then it seems like the kernel image.

If you haven't already, testing the 2.5 kernel on the 2.6 RC like bmarkus did would help nail down the culprit.

[roberts]

Just curious, what boot loader and which version are being used for those experiencing issues with 2.6?
Does updating your boot loader help?

[Machete]

Just curious, what boot loader and which version are being used for those experiencing issues with 2.6?
Does updating your boot loader help?

I'm just booting straight off the plain .iso. No other bootloaders, no hard drive, and 512MB ram.

[bmarkus]

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.

After 8 hours running Memtest-86 v3.5 (Pass: 10) no error found. It will run for longer time of course....

After running it for 18 hours I stopped memtest. No errors found.

[bmarkus]

Has anyone that is having issues tried using 2.5 with the 2.6 kernel?  That would help narrow down if it is the kernel image itself as we have tried the opposite.

2.5 with 2.6 kernel is freezing too. So it is up to the new kernel.

Updated BIOS, no change.