Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: attid on May 09, 2011, 02:04:24 PM
-
Hello
how i can install TC like normal system ?
i have a small computer (128RAM 128HDD-Flash) and TC very good work here, when started, but it load 30 min
1 syslinux or grub show menu
2. i see black screen with cursor on top screen ~30min. i think that at that time unpacked rootfs
3. i see messages from kernel and then start X
i want try unpack TC and use with out unpack
-
30 min - seriously? The unpacking should not take longer than a couple seconds, even on 586-class computers. Perhaps there's something waiting for a timeout, boot with "debug" to see the kernel messages.
-
What CPU? What boot medium and bus?
-
i add debug options
now i try with syslinux? after options i see text
loading bzImage . . . . . . .
loading tinycore.gz . . .. . . . . ready
and then black screen with cursor.
when it will boot where i can see debug message ?
-
and normal boot will not help me =( i get boot dir from instaled puppy, and try boot. but i get black screen on 30min too.
but i get TC with out autologin and modules.
What CPU?
AMD Geode LX 800 chipset CS5536
What boot medium and bus?
i try boot from integreted 512MB DOM
from usb flash
default system has kernel 2.4
-
here dmesg http://pastebin.com/8VCvXHqS
-
i add debug options
now i try with syslinux? after options i see text
loading bzImage . . . . . . .
loading tinycore.gz . . .. . . . . ready
and then black screen with cursor.
when it will boot where i can see debug message ?
Should be seen right there. Are you sure the option got there right? Is it shown in "showbootcodes" after boot?
-
yes am sure
$showbootcodes
initrd=/boot/tinycore.gz debug BOOT_IMAGE=/boot/bzImage
-
I once had a (somewhat) similar wyse S30 thin client running with tinycore 2.x (also Geode, CS5536 chipset), there are special ATA, clock and sound driver modules for these devices, which may not be integrated into tinycore (I didn't use the builtin flash but PXE because it wasn't writable). PXE booting was in normal speed, but e.g. CONFIG_PATA_CS5536 is not set in tc kernel, it might be timeout related?
-
what can i try also ?
-
Hi attid
In addition to debug add the boot code printk.time=1 and pastebin the resulting dmesg. This
may help to identify which part of the boot process is slowing things down.
-
done. i attach file
-
Alright, it seems to be a big (32GB) Kingston DataTraveler - one with an emulated CD drive (as usual on Kingston usb keys). I now remember that I played around with kernel options in tc 2.x to get those emulated drives to work, just to have the full feature. It might be that I also experienced this timeout, but I can't remember exactly - do you have another usb key to test? Just a plain one without this special Kingston stuff?
-
dmesg.txt TC installed to integreted flash.
dmesg1.txt unpacked TC installed to integreted flash with kernel from puppy
-
Well, at least we can see that unpacking the initramfs takes 1.5s on that hardware. It's something after the kernel that's taking so long.
-
What happens when leaving any USB devices (incl. related bootcodes) out of the equation?
-
Hi attid
Since you can boot from the integrated disk, let's try booting with just what's needed to get a display.
Add the boot code nousb and unplug all USB devices for good measure. In the BIOS, disable any
integrated devices not required for booting (network, sound, etc.). The intent is to try to get the system
to boot at a normal speed. If we achieve that, then we can start adding devices back in to try to identify
the source of the problem.