Kernel Panic - Not Syncing Error

[Juanito]

Would you mind to reveal more precisely what you mean by "the way" ... was it a certain compiler option/value ... or some pre-processing directive in glibc ... or ...

Code: [Select]

echo "CFLAGS += -march=i486 -mtune=i686 -pipe" > configparms

../glibc-2.9/configure --prefix=/usr i486-pc-linux-gnu --disable-profile --enable-add-ons --enable-kernel=2.6.16
"i486-pc-linux-gnu" was missed previously

[jamtat]

I'm attempting to test tinycore on some older machines in a computer lab in a retirement communitywhere I volunteer. I'm running into the kernel panic issue described in this thread. I downloaded the iso I'm using within the last week--it's called tinycore-current.iso. Once I read about this issue in this forum I began looking for the rc 4 release but have so far not managed to find any download so labelled.

So, where can I find 2.9 rc 4? Or for that matter any other release candidate with the kernel panic patch applied? The release candidates directory appears to be empty. Input will be appreciated.

Thanks,
James

[Juanito]

You need the current release - either microcore-2.9 or tinycore-2.9

[jamtat]

Thanks for the reply, Juanito. Given what you're saying, then, do I understand correctly that, since I downloaded within the last week the iso labeled tinycore-current.iso (found by following the link labeled "Current Release" from the tincore web site), I already have 2.9 rc 4 or later? That would not be very good news: I'm having the problem discussed in this thread, despite using a supposedly patched version.

If I am using the most current version and still have the kernel panic issue described in this thread, what are my options for testing tinycore on these older machines? Should I try an older release? If so, which?

Also, just out of curiosity: why is the release candidates directory empty?

James

[gerald_clark]

2.9 was released the evening of March 2nd.
If you downloaded 'current' before that, you got 2.8.
Download 2.9.

[jamtat]

Thanks for your input, gerald_clark. Just one point of clarification, though. There are two files in the "Current Release" directory that seem relevant, but I am uncertain which corresponds best to your directive. The two files are labeled tinycore-current.iso and tinycore_2.9.iso. Which of those two should I get? I assume both are 2.9?

James

[jamtat]

Not wanting towait any longer for an answer I went ahead and downloaded anew tinycore-current.iso and burned that to CD. The old computer booted fine with that one, no kernel panics occurred.

Thanks,
James

[Kingdomcome]

"tinycore-current.iso" is simply a symlink to the latest release which is now "tinycore_2.9.iso"  The symlink would have been updated at the time of the release on the evening of March 2nd.

[anjon]

Just to say that I have installed Tc 2.10 on an old Pc (it boots from the hard disk using grub).  I get the kernel panic just after the APIC message. However the same Pc boots fine from the Tc 2.10 CD.  Puppy and a number of other puppy based cds boot fine from the cd, I haven't tried putting any of them on the hard disk to see if they produce the panic. 

[magic_sam]

Hi,

First post here

I have some problems with the latest stable TC on an old Compaq Deskpro @ 166MHz / 160Mb RAM, which I'd like to turn into a small print server...

It boots fine from the live CD, but once installed I have the following issues:

with debug=on I can see that there is a problem with the RAMDISK (incomplete write, write error) and kernel panic - not syncing: VFS: unable to mount root fs on unknown block (8,3).

I can go past this error with root=/dev/hda2 but then I have another issue: "unable to open an initial console" kernel panic not syncing: no init found

What am I doing wrong ?

Bye and thanks for your help !

Magic Sam

EDIT: I have tried **A LOT** of boot options, to no avail

[tinypoodle]

What is your exact boot line?

Is that in default mode?

[magic_sam]

Hi tinypoodle

Thanks for helping me !

My exact boot line is:

kernel /boot/bzImage quiet
initrd /boot/tinycore.gz

As explained in the installation tutorial

Magic Sam

[curaga]

Check the md5sum of the initrd, it could have been corrupted (against the one on the cd, and http://ftp.nluug.nl/pub/metalab/distributions/tinycorelinux/3.x/release/distribution_files/tinycore.gz.md5.txt if it's the latest one). Could also be the HD is getting faulty.

[tinypoodle]

You could change 'quiet' to 'debug' to try to get more detailed output.

If I understand right, root fs should not be any storage partition, at least not when running TC in default mode.

Edit:
Try adding boot parameters

Code: [Select]

norestore
base


[magic_sam]

Try adding boot parameters

Code: [Select]

norestore
base


It didn't change anything

EDIT: @ curaga: you were right about md5sum The one from the official FTP matches the one on the CD, but the one installed on the hard drive is totally different ! What does it means and how do I solve this ?

Thanks a lot ! Magic Sam