Thankyou, and yes I do too but my editing was not familiar with this. I'll read through for comprehension, comparison, and make a backup of original file. ThankyouRupp wrote: I just posted this http://pastebin.ca/1682424 for someone in irc. Thats the pupflux menu. I know what you wanna do but I prefer to edit by hand anyway. To me its easier and it actually helped me learn more.
PupFlux, PupFluxLite & now PupFlux421
I am finding that 4.3.1 is having issues with some of my 'puters in that regard. I've found that typing from terminal "wmpoweroff" frequently will shut it down. In other words, I think it is the Puppy version that the more recent Pupflux is based on relative to the hard ware...walter90 wrote:I might have missed it but my PupFlux won't shut down the normal way. It just sits there with a black screen. Could be my laptop but i don't know. My Puppy 4.2.1 works without a single hitch.
If I go to "restart" in the flux menu I can type "poweroff" and it shuts down. What can I do to fix it?
I'm open to suggestions from the masses on that one...
Nope, not just you, and not just Pupflux. For example, I got a P4 laptop from someone recently, ran the latest MacPup on it (based on 4.3.1) and it has the same issue: it will shut everything down, but not turn the computer totally off.Rupp wrote:
I tried to make my own PupFLux 4.31 right after it came out and I had the same problem so I gave up. I thought it was just me having the problem.
Rupp
Mine doesn't say "system halted". It just is black. Will it do any harm to press the power switch in that case?dejan555 wrote:Ah that, yeah try booting with acpi=off
Or just push the power button when it says "System halted"
And yes, my MacPup Foxy does something similar so it must be Puppy 4.3 at the root of the problem.
not sure if it's safe if it shows black screen.
try "wmpoweroff" command from console or exit X with ctrl-alt-backspace then type poweroff
try "wmpoweroff" command from console or exit X with ctrl-alt-backspace then type poweroff
puppy.b0x.me stuff mirrored [url=https://drive.google.com/open?id=0B_Mb589v0iCXNnhSZWRwd3R2UWs]HERE[/url] or [url=http://archive.org/details/Puppy_Linux_puppy.b0x.me_mirror]HERE[/url]
The illustrious CatDude just sent me this pm about mirrors for Pupflux and Pupfluxlite:
Hello steve
I hope you don't mind, but i took the liberty creating a directory steve_s in the members section at asia,
and put a copy of pupflux421.iso into it.
The directory shows at both
http://puppylinux.asia/members/steve_s/
http://puppylinux.ca/members/steve_s/
I am sure that you already know the Username & Password.
...
P.S
I have also moved the location of your pupfluxlite.iso
so you may wish to edit this post
to point at the new location:
http://puppylinux.asia/members/steve_s/PupFluxlite/pupfluxlite.iso
http://puppylinux.ca/members/steve_s/PupFluxlite/pupfluxlite.iso
.
Thanks, CatDude! I'll edit that post later but wanted to get this posted asap...
Hello steve
I hope you don't mind, but i took the liberty creating a directory steve_s in the members section at asia,
and put a copy of pupflux421.iso into it.
The directory shows at both
http://puppylinux.asia/members/steve_s/
http://puppylinux.ca/members/steve_s/
I am sure that you already know the Username & Password.
...
P.S
I have also moved the location of your pupfluxlite.iso
so you may wish to edit this post
to point at the new location:
http://puppylinux.asia/members/steve_s/PupFluxlite/pupfluxlite.iso
http://puppylinux.ca/members/steve_s/PupFluxlite/pupfluxlite.iso
.
Thanks, CatDude! I'll edit that post later but wanted to get this posted asap...
- prehistoric
- Posts: 1744
- Joined: Tue 23 Oct 2007, 17:34
acpi=force?
Have either of you tried adding the kernel boot parameter "acpi=force" to either isolinux.cfg, syslinux.cfg or the grub menu.lst kernel line, as appropriate for your method of booting? You can probably test this by pressing F2 at boot to get a chance to enter "puppy acpi=force" when booting from the CD. If it works, you can use isomaster to edit the appropriate file and create a new iso image you can burn.Shep wrote:I'm not using Pupflux, but have that same problem with other puppies.walter90 wrote:I might have missed it but my PupFlux won't shut down the normal way.
Re: acpi=force?
I have tried all combinations acpi=force/on/off (simply because Iprehistoric wrote:Have either of you tried adding the kernel boot parameter "acpi=force" to either isolinux.cfg, syslinux.cfg or the grub menu.lst kernel line, as appropriate for your method of booting? You can probably test this by pressing F2 at boot to get a chance to enter "puppy acpi=force" when booting from the CD. If it works, you can use isomaster to edit the appropriate file and create a new iso image you can burn.Shep wrote:I'm not using Pupflux, but have that same problem with other puppies.walter90 wrote:I might have missed it but my PupFlux won't shut down the normal way.
have no idea what these are about ) and none made any
difference. I happen to be using using Dpup477 on a PIII.
Everything seems to shut down except the PSU and leds.
guys, afaik the shutdown problems are due to a code-change in wmpoweroff, wmreboot,...
not on puppy right now but will try to post a workaround later.
aragon
not on puppy right now but will try to post a workaround later.
aragon
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
so here we are again. test this
1. open /usr/bin/wmpoweroff in a text editor.
2. edit line 30 ff
to this
3. Save the file
4. Test poweroff
If this works, apply the patch also to wmreboot and wmexit.
aragon
1. open /usr/bin/wmpoweroff in a text editor.
2. edit line 30 ff
Code: Select all
#w003
CURRENTWM="`cat /etc/windowmanager`"
kill -9 `pidof $CURRENTWM`
Code: Select all
#w003
#CURRENTWM="`cat /etc/windowmanager`"
#kill -9 `pidof $CURRENTWM`
killall X
sleep 1
exec killall -9 X
4. Test poweroff
If this works, apply the patch also to wmreboot and wmexit.
aragon
PUPPY SEARCH: http://wellminded.com/puppy/pupsearch.html
Thanks, Aragon! I'll give this a run....aragon wrote:so here we are again. test this
1. open /usr/bin/wmpoweroff in a text editor.
2. edit line 30 ffto thisCode: Select all
#w003 CURRENTWM="`cat /etc/windowmanager`" kill -9 `pidof $CURRENTWM`
3. Save the fileCode: Select all
#w003 #CURRENTWM="`cat /etc/windowmanager`" #kill -9 `pidof $CURRENTWM` killall X sleep 1 exec killall -9 X
4. Test poweroff
If this works, apply the patch also to wmreboot and wmexit.
aragon
Those 5 lines were already present, though the first twoaragon wrote:so here we are again. test thisCode: Select all
#CURRENTWM="`cat /etc/windowmanager`" #kill -9 `pidof $CURRENTWM` killall X sleep 1 exec killall -9 X
were not commented out. So I commented them out,
but it made no difference. Still didn't poweroff.
I'm using dpup477 on a PIII
Thanks for trying.