Tiny Core Base > CorePlus

Kernel Panic on boot.

<< < (2/3) > >>

curaga:
Well, the unpack error is pretty clear. You're also right that seven laptops rules out faulty hw as in broken; but it seems to be limited by design instead.

Perhaps the bios cannot setup enough memory even though linux can, and so the bootloader fails with bigger initrds. Just conjecture, but it's clear there's some kind of limit in that model.

bkm:
Yeah, I kind of thought the same thing, but I couldn't imagine a situation where the system would fail when booting the same kernel. There is obviously something going on, I just can't imagine where it hiccups. Maybe something off in how the BIOS allocates buffer space for the cd-rom.

The weird part is that I eventually got a system running (frugal Install from tc live) just fine with some special packages I wanted. Once I figured out how to get my stuff configured just right, I went ahead and loaded up all the packages I could find in the coreplus listing just to see if there was some theoretical limit to how much the laptop could process on boot. It booted just fine from the hard drive.

I'm not sure what that leaves, but I am ok with being stumped. Some things are not worth getting a headache. So, it was a learning experience.

BKM

bmarkus:
Can you try 6.0alpha1?

bkm:
Sure, why not. I will download the images and try them on one of these laptops today. I will let you know what happens.

BKM

bkm:
Bela,

Here is what I got. The CorePlus 6.0alpha1 boots with the following messages:

.Loading     /boot/vmlinuz......
.Loading    /boot/core.gz.........ready.
early console in decompress_kernel
.
.Decompressing Linux...     Parsing ELF...    No relocation needed...    done.
.Booting the Kernel .
.Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(2,0)
.Kernel Offset:  0x0  from 0x0100000  (relocation range 0xc0000000-oxd47cffff)

The messages are the same for all 13 menu selections (including the command line only option)
I could possibly edit the boot string using the <tab> key if you have something you want to try.
This was the same on all three IBM ThinkPad 600x candidates with 320m RAM.

Next...
I booted the TinyCore 6.0alpha with no errors. I tried it with all 4 menu options and they all booted fine on all three candidates.

The only thing I can 'see' that is different is that the Core+ tells you the media will not be removable and TC tells you that it can be removed. However, if you try to remove the CD after the TC boot, the drive will not open. If you try to remove the CD after the kernel panic on the Core+ boot, it opens with no problem. I also noticed this with both the 4.x and the 5.x versions as well. There is certainly no apparent reason for the Core+ to generate a kernel panic when it is only trying to boot the command line only option!

Hope that helps,

BKM

Navigation

[0] Message Index

[#] Next page

[*] Previous page