Puppy Linux Discussion Forum

[tunyawat]

For those who want to see how does it look like, try pressing the reset button on your machine. When the blue screen comes up, Press Enter to Ignore the problem. After that the desktop will reappear as if the problem was fixed, but it didn't. Wait for 1 minute and reboot your machine by pressing the reset button again. That's it.

I'm not sure whether there is a way to recover to the previous state before it is broken. May be using the Puppy CD, but I've never tried out.

I've found that if the Puppy is rebooted systematically after the blue screen comes up, it will be fine.

To encounter this problem, I wrote a small script to make Puppy reboot itself. I replace this script on the section where the blue screen comes up. Therefore, instead of showing the user the blue screen, Puppy will reboot and fix itself from the problem.

[MU]

if the computer resets without proper shutdown, the last changes cannot be written to the filesystem. This makes it inconsistent.

Try to run from CD, and enter in the bootscreen:
puppy pfix=fsck

This will force a filesystem check.

Or use this method:
boot puppy without savefile (puppy pfix=ram).
You also can create a second dummy savefile:
pup_save-dummy.2fs (for Puppy 4.2).
Then you will get a menu at startup, to choose your savefile.
Select here:
0 - RAM
So you boot without any savefile.
Then mount the partition where your savefile is located (like sda1 in pmount).
Then type in a consolewindow:

e2fsck -p /mnt/sda1/pup_save.2fs

The "-p" option will try to repair automatically.
If that fails, run:
e2fsck /mnt/sda1/pup_save.2fs

Then keep the "y" key pressed, to confirm all questions.

After the check finished, Puppy should be able start up as usual with that savefile.
Some files or settings might be lost, but usually it should work ok now.

Mark

[lp.descamps]

Hi,

is this only for frugal install?

what about the full install? i beleive there is not such file in full install, right?

thanks

[tunyawat]

no, you can't use MU's method in full installation.

However, the problem occurs in both frugal and full installation. The best way is to write a script to restart your computer as I did.

[MU]

you can boot from CD with the option
puppy pfix=ram

Then it should not use the harddisk.
Then check the harddisk with
e3fsck -p /dev/sda1

If it is formatted with ext2, then use instead e2fsck.
If it is not sda1, use the corresponding partition.

Mark