Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: alanl on April 25, 2009, 11:51:11 PM
-
With both these releases I get this message:
----IO APIC resources could be not be allocated---
This is a Gigabyte mb(GA-5) with SIS.
The 1.3 version works great!
-
Maybe try some apic related boot kernel options, such as "noapic"
-
I used ....tinycore noapic & noIO APIC....but got the same result. I downloaded rc1 and it
works fine on my main computer but I get the same error message on the gigabyte.
Right now i`m using the gigabyte to post this with the 1.3 version. It works great so
something must have changed on the 2 version.
-
1.) Make sure that APIC is enabled in the BIOS, if you can find it there.
2.) Just add 'lapic' to the end of your Grub boot line, not 'lapic=yes' (might not make a difference). If your PC can do APIC, this will force it on.
From
http://bbs.archlinux.org/viewtopic.php?id=63641
-
I have the same problem with 2.0
CPU: vendor_id 'SiS SiS SiS' unknown, using generic init.
CPU: Your system may be unstable.
IO APIC resources could be not be allocated.
kernel panic - not syncing: Attempted to kill init!
1.4.3 works.
My computer is an eBox-2300 with a Vortex86 (SoC: System-on-Chip)
noapic boot option does not solve the problem.
-
I also have an eBox-2300. And I had same problem.
In tinycore 2.9.
This message is still displayed.
>CPU: vendor_id 'SiS SiS SiS' unknown, using generic init.
>CPU: Your system may be unstable.
>IO APIC resources could be not be allocated.
But, boot seems to succeed ;)
-
Those are informational messages from the kernel, and are not a problem.
There never was a problem booting.
The problem was with the libraries used by the init scripts.
The libraries were fixed in 2.9.