(old)Puppy Linux Discussion Forum

Hello All,

This is minor, but I believe I read in one of the blogs that BK cares
about it.

When I use wmpoweroff it shuts down to the point of giving me a
Power down. message and then leaves it for me to finish the job.

My windows xp pro ( sp2 ) actually shuts down the comp.

Is there a way to find out what win is doing?

I have switched to castle desktop - I like it better.

GeoW

That happens here too on my not-so-new PCs (more than three years old), also with many previous Puppy versions; not 1.08 which powers off perfectly. It's one thing I'm actually most curious about.

This also happens with some other Linux distros, the good side being the possible betting about complete shutoff on an untested PC...

Ok, not really a problem; however, when one shows Puppy to friends on their machine, it may somewhat spoil the picture.

Shutdown problem yielded 246 matches in Search. Surely everybody knows by now to set acpi=force?!

Sage,

acpi=force solves the shutdown issue -so thank you for that.

As to the rest - not so sage!

"Shutdown problem yielded 246 matches in Search."

1. I believe it was clear from my post that I didn't even know whether
this was the way Puppy was intended to work or not - why would I
search "shutdown problem"?

2. That is 8 pages of thread starts - 3 of the threads on the first page
have over a hundred replies each - one has over 300. I have spent
many hours reading the forum. I haven't come across the fix you
recommended, or a clear explanation of the acpi parameter.

"Surely everybody knows by now to set acpi=force?!"

I successfully got Puppy 3.01 running early December 2007. No
previous Linux experience, about a year on the internet. I am
learning as quickly as I am able.

Again, thank you for the fix,

GeoW

Yep, this works. It should appear as an option in the boot menu: surely there are more Puppy users than just GeoW and me who settle with an incomplete shutdown, accept it as a bit of "salt in life", and would never think to search the forum for a fix.

Believe me, there have been many discussions about this 'feature'. It seems to be Slack-/Puppy- and chipset- dependent. I set my Search to 6mnths. I mentioned it within the last few weeks, as I'd raised it with Dougal, who had considered writing it into the code permanently, but was unsure whether it might have some adverse consequences for some systems.
Always works.

A known problem with the eeePC is that sound_intel_hda (the device driver) had to be rmmod'ed for shutdown to be completed. It's erratic, however, and is known to negate the effectiveness of the "acpi=force" parameter.

@Barry: As to testing wireless scripts, you have wireless-capable laptops, but would you have some use for a wireless hub? (I read about your daughter's new Internet connection.) Linksys should be an inexpensive wireless hub, and readers can pitch in via Paypal should you need one for testing.

Well, you have a choice about shut down: either type acpi=force at the beginning, or use the power switch at the end. What most people want is to have to do neither!

Gerry

BarryK wrote:
Yes, I was thinkng that when click on an image in Rox, gview should be used. I suppose it does come down to choice. We probably need people to vote on this.

Barry, either works for me however, I view photos more often than I edit them.

Hi Barry,

thanks for adding me in... Dougal just wrote me and I am looking forward to developing networking.

Regarding your question:

When a newbie starts up Puppy and wants to connect to a WLAN, is it straightforward or is there some possible confusion in the steps?

I would say: to me, it was logical after reading into the code. (The code is the strong part here. Thank you again for this one.)
- The button "use this profile" definitely should save it also (feeling of 'loosing' data)
- scanning and displaying of available networks should take place automatically, because if network is not available via `iwlist $INTERFCE scan` user will not be able to connect to it anyway (and this is what he/she probably wants)
- selecting a network in the dropdown menu should load it. (This is the usual behaveiour)

Does the choice of different tools itself cause confusion?

I think Interface setup should be separated from (wireless) network setup. Today when I want to run the network wizard I have to go through the interface setup every time. Just put a check in the wireless wizard if Interface has already been setup - with an option to re-run it.

Urban

Networking discussion is moving here:

Forum index » Advanced Topics » Cutting edge
Networking - Responding Barry's questions

http://murga-linux.com/puppy/viewtopic.php?t=27486

wmpoweroff was not completely shutting down my comp

Sage said, on this thread acpi=force was the fix.

It works ( on pup 2.12, 3.01, & 3.97 ), so it is now on every
kernel line in my menu.lst. Shutdown always works.

However, since I started using it, sometimes on bootup
my comp will lock up. It says:

Uncompressing Linux... Ok, booting the kernel.

and it stops there - with a flashing cursor on the next line.

I have not found a key combination that will break out of this.

I need to hold in the power button for a while, get a complete
shutdown, and try again. Usually, the second try works.

Unfortunately, I haven't been able to reproduce this dependably;
it remains random, but I never saw this before using acpi=force.

The other, even stranger behavior, I have seen is a twisted mouse.

Sometimes, after one of the boot lockups and recovery, my mouse
comes up twised - if I push the mouse away, instead of going up
the screen the cursor goes to the right. To move up i move the
mouse to the left. This will go away, but not necessarily after only
one reboot.

I don't know if these are technically Dingo Alpha 7 problems as they
will occur in any version, but they do also occur in DA7.

I have no clue about either of these.

GeoW

Artefacts tend to occur with most systems/OSes. Sometimes they are very difficult to track down, especially if they are irreproducible by other folks - as the BIG man constantly reminds us. If removing acpi=force solves the problem, why not remove it? Then perhaps the machine won't shutdown?!
In the trade, most odd goings on are fixed by swapping HW rather than rigorous diagnosis. Could try changing the mouse in this case? Another reason to avoid proprietary junk - be sure to build your own, then changing components is a doddle.

Addendum: Yes, there is one particular brand of mouse and one version of Puppy that creates havoc. I have experienced it myself a long while ago. There was a discussion somewhere here about it, but not recently. The advice is always the same - change the HW that is playing sillyB s and see if that changes anything.
For the record, there have been other distro mice combinations that have given me grief, but that has also been the case with keyboards (rarely, except USB), sound cards, on-board video cards, cameras, webcams, printers..... I'm sure you get the picture.