Good news/bad news.
Fresh install, installed nvidia driver from the sfs, a samml pet, post the report here with midori.
Second or third boot, shutdown failure/looping back to desktop every time. Need to hardware reset.

Reboot PC ... got 'shutting down' message ... comes back the desktop. The LAN was disconnected ... tried frisbie, but the NIC driver not found ... Go down to the console, typed 'poweroff' ... comes back desktop ... Hard reset by the power button.

I was a bit confused in doing FULL install the Saluki for testing.
The Gparted and the Puppy universal installer are found in the menu under 'system', but the grub4dos is not there.
The grub4dos is under the Control Panel > 'system', but the Puppy universal installer is not there.

Good news/bad news.
Fresh install, installed nvidia driver from the sfs, a samml pet, post the report here with midori.
Second or third boot, shutdown failure/looping back to desktop every time. Need to hardware reset.

Reboot PC ... got 'shutting down' message ... comes back the desktop. The LAN was disconnected ... tried frisbie, but the NIC driver not found ... Go down to the console, typed 'poweroff' ... comes back desktop ... Hard reset by the power button.

I have been updating the save file by simply copying it to the folder containing the new Saluki system files.
Generally this has passed without problems. On the latest 021 version however this process worked on one machine (Aspire TimelineX i5) but not on another (Eeebox 1502).

Updating the Eeebox by converting the old savefile gave rise to extremely sluggish performance.

I tried another method, creating a new savefile and then copying certain config files across from the old, .mozilla for example.

Now the Eeebox runs perfectly.

Using the "lazy" option of letting the system upgrade the savefile doesn't seem to have had an impact on the Aspire laptop so I'm curious as to the recommended safe method.

Best regards,

Oliverjames

Upgrading the save file has always been like this. Most of the time it works - sometimes EPIC FAIL for no apparent reason.

Booting with pfix=purge may or may not fix a bad save file.

You can build a personal sfs with all the pets you normally install using the sfs builder. But this will not be able to overwrite any configuration settings that exist in the adrive or the pupsfs since extra sfses are mounted on the bottom of the union. But you could fix that by converting your personal sfs to a pet instead.

Today, at 1:14 pm
Subject description: Shutdown delay Reply with quote
Lucid Puppy 5.2.8-005 has a serious shutdown delay problem on my AMD Athlon 2400 (single processor), frugal installation. Fortunately, I was able to track down the source of the problem.
...
I have no idea whether this problem is related to the other shutdown problems discussed earlier in the forum. In any case, it does not occur in Wary 5.3 or Slack 5.3.2.7, which shut down normally on my machine. I seem to remember a similar delay with Puppy 4.3.1, but I never did find a solution back then.

As for rc.shutdown, attempt to open it crashed the entire edifice. Note that apart from rc.shutdown, also have ditto.orig, ditto.pot and ditto.pupdev present.
Will attempt to delete these with a liveSlackoCD and report back tomorrow.
Seems that shutdown issues are emerging all over the woodwork...

To the top of rc.shutdown. This should make the problem go away if it's related to localization somehow.

Maybe no. I was under 'en_US' locale at the test.
I suspect the nvidia driver, changing some libralies when the desktop is running. But not sure.

Sorry for the grub4dos in the menu. I was testing my new package of the grub4dos. But still i think the menu and the Control panel are confusing._________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html

if it's killing the shell (or logging off) on tty1. If that shell dies, mingetty will respawn it, and rerun /etc/profile.

I am not sure when Barry changed the /etc/inittab, but it was somewhere between Puppy-4.x to 5.x.
Seeing his comment, he was aware of the X coming back problem in last summer, i guess.
If the mingetty will respawn the shell, the flag /tmp/bootcnt.txt can be deleted before. _________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html

Managed to find a few moments this afternoon. Using a liveCD, I was able to rename the four options for rc.shutdown in my FULL. Reverting rc.shutdown to ditto.orig had no effect - looping back to desktop continued. Hit the jackpot with ditto.pupdev, though. at least three shutdowns worked as advertised. Where and why did rc.shutdown.pupdev come from?
Well done to the eagle-eyed drblock2!

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