Posted: Sun 21 Feb 2010, 12:47
Hi, nooby.
"kernel panic" may refer to many things, mostly related to hardware compatibility, memory chips or quality of the copy of the files on the disc.
It can also mean that the kernel cannot find the proper next file to load. This file can be a file such as initrd or the puppy sfs or an internal driver the kernel thinks it needs for your hardware.
The fact that one kernel panic causes problems for two puppies makes me believe that your problem is on the disk -- either the disk itself needs checking or the files on it need checking. Probably the two files overlap somehow on the disk sectors.
I would suggest doing the general things as follows:
Boot into one of your working puppies -- or much better, boot this Puppy from its boot CD.
Make sure you have back-ups of all your important files, sfs, etc.
If not, make back-ups before you do the rest (below).
Go to the drive(s) where your sfs files are. For ex.,
cd /mnt/sda1 OR cd /mnt/home
Then, in console, use e2fsck
e2fsck --help
to get general idea of use
Check that all your copies of these files -- linux kernel files and puppy files -- are good. Again, defragment the files if necessary, but maybe making a fresh copy will be faster -- and you will be sure that the copies are good..
If you choose NOT to copy fresh copies of the files, use a command such as
e2fsck -p dpup[proper number].sfs
e2fsck -p dpupsave[your identifier here].2fs
When your files are repaired, check that they are in the proper place (top level of disk, or directory or sub-directory), where they are supposed to be. If not, MOVE them where they are supposed to be.
As to the internal drivers of the kernel, any Puppy kernel usually has a quite complete series of drivers built-in, so unless your hardware is "very-very" uncommon, you should be able to boot into the desktop fluidly.
Which is why I tend to say that the files that you mention have somehow been corrupted, perhaps by shutting down the computer manually in an emergency?
The other possibility would be that you have bad memory chips. This seldom happens, though. You would run a program named "memtest" to check that. There is also, usually, a way to get the BIOS to do this for you at boot.
But start with checking your files on disk with e2fsck first. This is more common.
A final thought: are you using the same savefile for all your puppies? This can be a big problem if the version of the puppies is not the same. I know for a fact that pulp puppy and dpup do not have the same "internals" and they are not of the same kernel version, so the savefile for one will most likely not be good for the other.
I hope this helps. Use care and caution. Remember the above may work or not work. Good luck.
"kernel panic" may refer to many things, mostly related to hardware compatibility, memory chips or quality of the copy of the files on the disc.
It can also mean that the kernel cannot find the proper next file to load. This file can be a file such as initrd or the puppy sfs or an internal driver the kernel thinks it needs for your hardware.
The fact that one kernel panic causes problems for two puppies makes me believe that your problem is on the disk -- either the disk itself needs checking or the files on it need checking. Probably the two files overlap somehow on the disk sectors.
I would suggest doing the general things as follows:
Boot into one of your working puppies -- or much better, boot this Puppy from its boot CD.
Make sure you have back-ups of all your important files, sfs, etc.
If not, make back-ups before you do the rest (below).
Go to the drive(s) where your sfs files are. For ex.,
cd /mnt/sda1 OR cd /mnt/home
Then, in console, use e2fsck
e2fsck --help
to get general idea of use
Check that all your copies of these files -- linux kernel files and puppy files -- are good. Again, defragment the files if necessary, but maybe making a fresh copy will be faster -- and you will be sure that the copies are good..
If you choose NOT to copy fresh copies of the files, use a command such as
e2fsck -p dpup[proper number].sfs
e2fsck -p dpupsave[your identifier here].2fs
When your files are repaired, check that they are in the proper place (top level of disk, or directory or sub-directory), where they are supposed to be. If not, MOVE them where they are supposed to be.
As to the internal drivers of the kernel, any Puppy kernel usually has a quite complete series of drivers built-in, so unless your hardware is "very-very" uncommon, you should be able to boot into the desktop fluidly.
Which is why I tend to say that the files that you mention have somehow been corrupted, perhaps by shutting down the computer manually in an emergency?
The other possibility would be that you have bad memory chips. This seldom happens, though. You would run a program named "memtest" to check that. There is also, usually, a way to get the BIOS to do this for you at boot.
But start with checking your files on disk with e2fsck first. This is more common.
A final thought: are you using the same savefile for all your puppies? This can be a big problem if the version of the puppies is not the same. I know for a fact that pulp puppy and dpup do not have the same "internals" and they are not of the same kernel version, so the savefile for one will most likely not be good for the other.
I hope this helps. Use care and caution. Remember the above may work or not work. Good luck.