Slacko 5.3.1 on USB flash drive won't power down EeePC

[Fallingwater]

I have Slacko 5.3.1 installed on a USB thumbdrive. When I try to shutdown or reboot it saves to partition, then restarts the GUI. I'm forced to then shut it down by keeping the power button pressed.

If I open the terminal and just give it the "halt" command it says "system halted" and the computer freezes - it doesn't actually power off.

The computer is an Asus EeePC 1005HA.

Any way to fix this?

[musher0]

Hello, Fallingwater.

Sorry to hear about your shutdown troubles. On some machines, this will happen, according to some posts.

I'm no expert, but you could try this:

go back to initial black console by typing ctrl+alt+backspace;
now type:

Code: Select all

busybox poweroff # if you want to close your computer down OR
busybox reboot # if you want to reboot

Good luck.

[musher0]

Hello, people.

I experienced the problem firsthand with the latest wary (5.3) running entirely from CD. It stuck on shutdown and I lost all the changes I had done during the session. Even the

Code: Select all

busybox reboot 

command failed...

Hm... If you want people to stay with Puppy, this not the way! (Only half a joke.)

BFN.

[bigpup]

Here is where the problem is talked about in Barry's blog.
http://bkhome.org/blog/?viewDetailed=02505
I would think this has been fixed in Slacko 5.3.3, but not sure.

[Karl Godt]

I am running Saluki 19 on the same machine asus eee 1005 HAG/HGO

# dmidecode


Manufacturer: ASUSTeK Computer INC.
Product Name: 1005HAG
Version: x.x
Serial Number: 9BOAAS454583
UUID: 00AC5A5D-BD45-4681-3353-E0CB4E1A0EFA
Wake-up Type: Power Switch
SKU Number: To Be Filled By O.E.M.
Family: To Be Filled By O.E.M.


and i had no such shutdown problems with any Puppy until now .

There is code for killing so called Zombie Processes for killing the parent of the zombies and it is theoretically possible that this would kill rc.shutdown , reboot/poweroff and [a|min]getty .

If i had the chance to observe such killings it seems to me the process gets just restarted with a new PID number few greater than before .

To observe this : open /etc/rc.d/rc.shutdown as text file and put a gate-sign before 'clear' or 'exec 1>/dev/null 2>&1' lines . These should normally make shutdown less verbose .

These apparently never killed init/getty to be respawned (look in /etc/inittab) on my systems .

halt itself is used normally to suspend finally in standby mode . reboot and poweroff are the ones used by puppy in regular .
For more information : ggogle "man 8 shutdown" ;the shutdown binary is not included in Puppy by default .

[musher0]

Thanks to the both of you for useful information.

@bigpup
BK's comment was posted at the end of September 2011 and the problem is still there in latest wary (end of March 2012). Six months and no improvements? Speaks volumes in my mind. It's lucky that Puppy has other advantages, 'cause if word got out, we'd be the laughing stock of the Linux community. I see the headlines in the specialized press:

"Latest Puppy won't let you out!" or "Trapped in latest Puppy"

Very bad image problem. Not good, not good at all. And nobody here wants eight years of progress in this distro to go down the drain because of a silly (but important) little problem.

There was a few weeks ago a real possibility that I participate in the translation process (fr, fr_CA) and the real reason I did not react is this: I did not want my name to be associated with a distro that cannot close properly. There. I said it.


@karlgodt
do you mean that having the real shutdown executable present in Puppy would be the solution? Thanks in advance.

BFN.

[L18L]

Here is where the problem is talked about in Barry's blog.
http://bkhome.org/blog/?viewDetailed=02505
I would think this has been fixed in Slacko 5.3.3, but not sure.

Could you post a link for download slacko 5.3.3 please?

There was a few weeks ago a real possibility that I participate in the translation process (fr, fr_CA) and the real reason I did not react is this: I did not want my name to be associated with a distro that cannot close properly. There. I said it.

[lang=fr_DE]C´est domage. Mais je comprends.[/lang]

[bigpup]

Could you post a link for download slacko 5.3.3 please?

Slacko 5.3.3
http://www.murga-linux.com/puppy/viewtopic.php?t=76279

It is in beta testing, so the actual iso will be called 5.3.2.7

[musher0]

Finally got the "wary" to behave properly, on a new CD without any change to the rc.shutdown code.

The only explanation I could come up with is that, the first time, I think I somehow skipped the panel that comes up when you first exit the pup, to specify whether you want to save to CD or disk.

BFN.

[bignono1]

Go /etc/rc.d/rc.sysinit , go to line 294 ,make sure it is like this:
[ ! -d /proc/acpi ] && modprobe apm power_off=1 #v406
If not so , edit , save and reboot.
Make a backup of your rc.sysinit file in case things go wrong .

[L18L]

Could you post a link for download slacko 5.3.3 please?

Slacko 5.3.3
http://www.murga-linux.com/puppy/viewtopic.php?t=76279

It is in beta testing, so the actual iso will be called 5.3.2.7

Thanks for the link.
Yes, this is "back to beta2"

I have tested shutdown and reboot (from menu)
Shutdown: OK
Reboot: screen is all black except bottom panel

Restart X brings up desktop icons and wallpaper.
But this should be there automatically.
http://www.murga-linux.com/puppy/viewto ... &start=255

[Karl Godt]

@karlgodt
do you mean that having the real shutdown executable present in Puppy would be the solution? Thanks in advance.

Dont know . its 2years since i have used a shutdown binary .

I am fond of busybox .

I would also probably alter the code in /sbin/poweroff and /sbin/reboot with a line like

[ "$?" != 0 ] && do_something

after the line that runs /etc/rc.d/rc.shutdown .

also some lines like

read -p "Continue ? " C_KEY
[ "$C_KEY" ] || C_KEY=y
[ "$C_KEY" != 'y' ] && do_something_here

to debug in rc.shutdown .

There had been complaints that network mounts had not been unmounted too before bringing down the network . If a sfs is mounted on a remote partition, the sfs has to be unmounted first before the remote drive can be unmounted .

Puppy is also not good in supporting file and directory names with spaces .

Maybe i can send a patch like

mountline=`echo "$mounts" grep -w "^$drive"`
mountpoint_with_spaces=`echo "$mountline" |sed 's|.* on ||;s| type .* (.*)||'

which would work as long as the mountpoint does not contain " type " in its directory name, like

/dev/sdx on "file://path/to/my type of mount" type nfs (rw,attrib_1,..)

[musher0]

Hello, Karl et al.

Can this problem have to do with the age of the mother-chip?

I noticed that same problem in Upup-Precise, where the shutdown options in the jwm menu work fine on a newer computer, but do not do anything on an older one.

BFN.

[Karl Godt]

On my "Dell optiplex 745" i have to boot kernels >=2.6.39 with the kernel parameter "reboot=f" to get reboots .
Without that parameter the computer just goes into "ACPI S5 Soft-Off Standby halt" mode
if reboot/wmreboot chosen, poweroff works normal .
I have looked inside the kernel code and they have added some code for dell computers,
which seems to do the opposite -- but probably busybox reboot is not that modern acpi capable for the current versions .


Other posts to read :

busybox.conf fixes shutdown : http://bkhome.org/blog/?viewDetailed=02241

Shutdown/reboot bug fixed : http://bkhome.org/blog/?viewDetailed=02505

[bigpup]

Hello, Karl et al.

Can this problem have to do with the age of the mother-chip?

I noticed that same problem in Upup-Precise, where the shutdown options in the jwm menu work fine on a newer computer, but do not do anything on an older one.

BFN.

This is one possibility. Slacko is designed for newer hardware. Around 5 years old or newer. Also the newer Linux kernels, (which Slacko uses) are dropping support for old hardware. It is a little fuzzy as to what that really means.
This statement does hold true.
Not all versions of Puppy work on all computers.