Hello from an old 'Newbie' to Linux. All help appreciated.
I can boot Puppy Linux from CD to my old XP OS PC (with a little trouble getting wireless internet to work).
When I try to boot to my very slow Vista OS Dell laptop, after the first boot (which was OK except for the wireless internet), I now get nothing but 'Kernel Panic' messages.
I've tried a verbose boot and all seems OK down to 'searching for Puppy files ....done, after which I get 'loading personal file / pupsave-test-2fs (sda1) EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended.
It carries on to: Performing a 'switch-root' to layered filesystem...then comes the 'kernel panic - not syncing: attempted to kill init!
I've seen this message referred to on some of the forums, but the advice given seems to assume a deeper knowledge of the operating language than I have.
Can anyone suggest what I should try in plain english please?
I should add that the laptop boots up OK into Vista (that's relatively speaking, of course ;-})
Thanks, Bob.

If nothing important is on the pupsave
delete it and make a new one
sounds like its corrupted...

do you have the pupsave on CD?
or where?

Thanks Linus. I can find no trace of the pup files on the laptop.
However, if I do a pfix=ram on bootup, all seems OK, then I save the files on closedown. Next boot, puppy asks me to choose which file to use (it can now see two), if I select the latest file, I get the kernel panic again. Isn't this fun?

Hi, I am very new to Linux. Steadfastly determined to progress. I need to acumulate a lot more knowledge before I am safe to be let loose properly. I still use windows to operate my office programs but am already using open office on windows. All my internet is done via puppy CD but I have the same problem with the boot. Gives me same kernal panic message unless I use pfix=ram. When I transfered the ISO I used a DVD. I didnt close the session but so far I dont think that any session on puppy has been saved to the DVD. I have to reinstall everything set up on the previous session. Can you tell me what I'm doing wrong as reloading everything everytime is a bit laborious. Thanks GB

@ginger.buddah;

Go make your own thread! Don't 'hijack' other peoples' threads. Once you make your own thread, you will receive help.

@Bob, the Original Poster;

Hello!

If some of the following terminology is foreign or confusing, use Google and search for the term in question. If the term cannot be found, then resort to posting your question here. Please do not hesitate to ask if you have any particular doubts or thoughts.

First, boot up a Linux Live CD/DVD/USB, and open a command line interface, also known as a 'Terminal', 'command prompt', 'shell', or 'console'.

Next, switch to the 'root' user. Also termed the 'Super User' or the 'system administrator'. On Ubuntu, this is done with the "sudo su" command. On most other systems it can be done by simply typing "su -".

After that, use the "fdisk -l" command to find out the label of the partition in question. Note the /dev/sdX label. (Ex. /dev/sda).
Moving forward, we will use the "mount" command to figure out whether or not the noted partition is 'mounted'. If you can see the partition in question from the output of the command, we will first need to unmount it to perform potential repairs. If indeed you see that it is 'mounted', then use the "umount /partition label here" command to unmount it.

Finally, perform the command "fsck.ext2 -pf /partition label here" {(Example: fsck.ext2 -pf /dev/sda5)} to force the file system check (-f) and automatically repair the system (-p).

Please note that this operation can take a long time. It is essential to let the command finish, so any potential problems may be fixed. If this does not work, or you receive an error, please describe exactly what happened, and the exact error output the command gave you, if any. There is a warning that is associated with all operations like this; make sure you get the syntax and labels right, or you will lose data.

I hope this resolves your problem.