Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: pbe on January 11, 2011, 09:26:10 AM
-
for a home automation solution I try to get run TinyCoreLinux on PDX057-T based on Vortex86DX.
But there are some kernel issues, while booting:
1.
I get following messages while booting:
CPU: vendor_id 'Vortex86 SoC' unknown, using generic init.
CPU: Your system may be unstable.
2.
There are also 4 address space collisions
pci 0000:00:0a.0: address space collision: [mem 0x000e2000-0x000e2fff] already in use
pci 0000:00:0a.0: can't reserve [mem 0x000e2000-0x000e2fff]
pci 0000:00:0a.1: address space collision: [mem 0x000e3000-0x000e30ff] already in use
pci 0000:00:0a.1: can't reserve [mem 0x000e3000-0x000e30ff]
pci 0000:00:0b.0: address space collision: [mem 0x000e0000-0x000e0fff] already in use
pci 0000:00:0b.0: can't reserve [mem 0x000e0000-0x000e0fff]
pci 0000:00:0b.1: address space collision: [mem 0x000e1000-0x000e10ff] already in use
pci 0000:00:0b.1: can't reserve [mem 0x000e1000-0x000e10ff]
Nevertheless TinyCore and my software homeVisu are running on PDX057. :)
But the error messages and warnings while kernel booting are annoying!
Are there any way to solve the errors and warnings?
Maybe the performances of TinyCore can optimise for Vortex86DX?
-
Vortex86DX is probably one of the lowest machines TCL will run on.
That chip does not have anything to optimze for.
It is basically a 486. Any optimizations to the kernel will probably make it
not run at all.
I have an eBox 2300 with Vortex86 running TCL.
-
Yes, TCL is running on VorTex86 - a great work. :)
Only the error messages and warnings while kernel booting are annoying.
My question was, if it is possible to solve these messages.
Maybe a kernel bootcode helps, or do I need a customer kernel for VorTex86DX?
-
you can use the kernel parameter memmap to mark memory as reserved