Finally I managed to install Puppy Linux on my Asus EeePc 900. It works quite well, but I still have a big problem. It seems impossible to power off the PC, neither via menu neither going to prompt and typing "poweroff".

In both cases screen goes black and then I receive following messages:

Finally I managed to install Puppy Linux on my Asus EeePc 900. It works quite well, but I still have a big problem. It seems impossible to power off the PC, neither via menu neither going to prompt and typing "poweroff".

In both cases screen goes black and then I receive following messages:

What you describe is the classic shutdown problem, with full installs, if the partition the full install is on, is mounted, when you shutdown._________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

My Puppy is last version 5.28, Full installation on SSD internal drive.

I think Bigpup is right, because I made a little experiment. If I poweroff just after booting, without doing anything, it works fine. If I click and open my sda1 system partition with file explorer, after trying to shutdown I experience the problem I described.

Just make sure you have sda1 not mounted when you shutdown.
The sda1 drive icon on the desktop will indicate if mounted or not.
If mounted, use the drive icon to unmount. Right clicking on it and choose unmount sda1.

Also, at shutdown, do not have a Rox file manager window open showing any content of sda1.

Here is the confusing part. The drive partition sda1 has to be mounted, because the system just booted from it and programs are accessed/stored on sda1 as you run them. The problem comes into play when it gets further mounted (in active use) through the drive icons on the desktop or Rox file manager.

This only seems to affect full installs.
A little bug you just need to know about._________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

Sometimes a filesystem will refuse to umount (unmount) if a process has a directory on that filesystem simply as its current working directory without there even being any files open on it.

Emelfm2 has this annoying habit of holding on to a filesystem on occasions even after navigating away and has to be closed down before umount will work.

If after closing down all applications and normal shutdown still doesnt work then there are some nuclear options that may still be a better option than pulling the plug (whilst still trying to resolve any possible device or file system corruption issue preventing normal shutdown/reboot scripts working).

the command

umount -ar

will attempt to umount as much active filesystems as possible.

the busybox multi call binary, installed in most if not all puppy linux systems, has a couple of applets for shutting down/rebooting a system and will bypass rc.shutdown script etc. which might be useful as a temporary workaround for malfunctioning shutdown scripts.

At the command prompt:

busybox poweroff

will attempt to clear the systems buffers and poweroff the system.

busybox poweroff -f

(Forced poweroff, even more drastic)

busybox poweroff -n -f poweroff

Forced poweroff without attempting to clear write buffers.

Nuclear. More or less equivalent to pulling the plug. Not very kind to filesystems. I once used this command to poweroff my system when a copy operation on a usb drive failed and the copy operation stalled and could not be killed off. Somehow I still prefer this option to pulling the plug, though.

You should be able to create a shutdown script that is executed that will unmount your filesystem. Use the CLI commands for mounting and unmounting your drive and you should be able to insert that into the shutdown script. I'm not exactly sure where the actual script is off the top of my head, but it should be fairly simple to edit it._________________TotalElectronics.us

An a line specific to umount the removable drive or drives could be added near the start of this script but from my reading the shutdown script eventually does a "umount -ar" anyway. That should have umounted everything cleanly unless perhaps there is is some kind of problem or conflict that is preventing a clean umount.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum