Saluki

A home for all kinds of Puppy related projects
Message
Author
User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Good news/bad news.

#2836 Post by shinobar »

shinobar wrote:BYW, the FULL install of the Saluki-21 is working so far.
Good news/bad news. :lol:
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.

EDIT:
Power on ... got console ... typed 'xwin' ... got desktop ... posted from the midori ... reboot PC ... this time the PC reboots normally :roll:
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

Re: "saving to a file", or "saving to a partition"

#2837 Post by jemimah »

shinobar wrote:
greengeek wrote:what I didn't realise is that the question about "saving to a file", or "saving to a partition"
You have used the legacy interface at the pupsaveconfig, i guess. The GUI of the pupsaveconfig never asks and does not support the "saving to a partition". I think it is buggy and troublesome.

How to do NOT:
http://www.murga-linux.com/puppy/viewtopic.php?t=62476
Perhaps the Legacy button should be removed at this point?

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

Re: Installers

#2838 Post by jemimah »

shinobar wrote: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. :roll:

BYW, the FULL install of the Saluki-21 is working so far.
Yours doesn't look like this?
Attachments
Screenshot.jpg
(40.37 KiB) Downloaded 579 times

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

Re: Good news/bad news.

#2839 Post by jemimah »

shinobar wrote:
shinobar wrote:BYW, the FULL install of the Saluki-21 is working so far.
Good news/bad news. :lol:
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.

EDIT:
Power on ... got console ... typed 'xwin' ... got desktop ... posted from the midori ... reboot PC ... this time the PC reboots normally :roll:
My thought is to add

Code: Select all

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

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

Re: Savefile update 020 to 021

#2840 Post by jemimah »

oliverjames wrote: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.

Maybe a pet-builder would be useful.

Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

#2841 Post by Sage »

drblock2

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...

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: Good news/bad news.

#2842 Post by shinobar »

jemimah wrote:My thought is to add

Code: Select all

export LANG=C
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. :lol:


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 [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#2843 Post by jemimah »

Yes I change the desktop file for grub4dos so it shows up in the system menu - but not in the control panel.

Package managers show up in both the menu and the control panel because windows users will look for Add/Remove programs.

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#2844 Post by jemimah »

The only reason it would restart X that I can think of, is if it's killing the shell (or logging off) on tty1. If that shell dies, mingetty will respawn it, and rerun /etc/profile.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

exec vwin

#2845 Post by shinobar »

jemimah wrote:The only reason it would restart X that I can think of, is if it's killing the shell (or logging off) on tty1. If that shell dies, mingetty will respawn it, and rerun /etc/profile.
Hum... Is it why Barry moved 'exec xwin' from /etc/profile to /root/.profile... :roll:
/root/.profile in recent woof wrote:#120221 moved this code here from /etc/profile, also take 'exec' prefix off call to xwin.
(snip)
#want to go straight into X on bootup only...
if [ ! -f /tmp/bootcnt.txt ];then
touch /tmp/bootcnt.txt
#exec xwin
#xwin & #110804 110807
xwin
fi
Well... /tmp/bootcnt.txt can be ...
Last edited by shinobar on Sat 28 Apr 2012, 14:32, edited 3 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#2846 Post by jemimah »

I don't think it makes any difference in this case. /root/.profile should be executed right after /etc/profile.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

respawn

#2847 Post by shinobar »

jemimah wrote: 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. 8)
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
Karl Godt
Posts: 4199
Joined: Sun 20 Jun 2010, 13:52
Location: Kiel,Germany

#2848 Post by Karl Godt »

Well... /tmp/bootcnt.txt can be ...
deleted in rc.shutdown .. in full installs .. or frugal pupmode 12 on HDD
also unmounted in rc.shutdown for frugals having /tmp mounted as tmpfs ..

Barry has done some code adjustments to rc.shutdown recently .

Is Saluki still based on racy woof 5.2(.x) ?

(One note about thunar : Thunar uses a trash dir , so i was having problems deleting files larger than the remaining free space in the pupsave-file)

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

shutdown ... but reboot

#2849 Post by shinobar »

Same as before:
/root/.profile in recent woof wrote:#120221 moved this code here from /etc/profile, also take 'exec' prefix off call to xwin.
(snip)
#want to go straight into X on bootup only...
if [ ! -f /tmp/bootcnt.txt ];then
touch /tmp/bootcnt.txt
#exec xwin
#xwin & #110804 110807
xwin
fi
Anothe Barry's comment:
rc.shutdown wrote:#110928 fixed, reboots when choose shutdown. very old bug, dates back to 2009.
(snip)
#120409 experimenting with minit, i discovered "rm -rf /tmp/*" is killing mingetty. initrd.gz wipes it, have added code to wipe for full hd install at bootup..
#rm -rf /tmp/*.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

#2850 Post by Sage »

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!

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#2851 Post by jemimah »

Karl Godt wrote:
Well... /tmp/bootcnt.txt can be ...
deleted in rc.shutdown .. in full installs .. or frugal pupmode 12 on HDD
also unmounted in rc.shutdown for frugals having /tmp mounted as tmpfs ..

Barry has done some code adjustments to rc.shutdown recently .

Is Saluki still based on racy woof 5.2(.x) ?

(One note about thunar : Thunar uses a trash dir , so i was having problems deleting files larger than the remaining free space in the pupsave-file)
Yes still based on 5.2. But rc.shutdown from pupsaveconfig is newer. I can roll back to the old pupsaveconfig or we can try to fix the newer rc.shutdown.

I had the occasional "session not saved" problem with the older pupsaveconfig - so it'd be nice if the new version could be made to work.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

rc.sysinit

#2852 Post by shinobar »

jemimah wrote:I can roll back to the old pupsaveconfig or we can try to fix the newer rc.shutdown.
Problem is at the rc.sysinit.
/etc/rc.sysinit in recent woof wrote:if [ ! -d /initrd ];then #w468
busybox mount -o remount,rw /
#120409 no longer deleting /tmp/* in rc.shutdown... (note, init script in initrd.gz wipes it)
rm -rf /tmp/*
rm -rf /tmp/.[0-9a-zA-Z]*

echo 'PUPMODE=2' > /etc/rc.d/PUPSTATE
if [ "$ORIGLANG1" != "en" ];then #120217
echo "OUTPUT_CHARSET=UTF-8
export OUTPUT_CHARSET" >> /etc/rc.d/PUPSTATE
fi
fi
. /etc/rc.d/PUPSTATE #variables created at bootup by init script in initrd.
No need to change the rc.shutdown, but the deletimg /tmp/* is required in the rc.sysinit.
Last edited by shinobar on Sat 28 Apr 2012, 15:18, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

Re: rc.sysinit

#2853 Post by jemimah »

shinobar wrote:
jemimah wrote:I can roll back to the old pupsaveconfig or we can try to fix the newer rc.shutdown.
Problem is at the rc.sysinit.
/etc/rc.sysinit in recent woof wrote:if [ ! -d /initrd ];then #w468
busybox mount -o remount,rw /
#120409 no longer deleting /tmp/* in rc.shutdown... (note, init script in initrd.gz wipes it)
rm -rf /tmp/*
rm -rf /tmp/.[0-9a-zA-Z]*
echo 'PUPMODE=2' > /etc/rc.d/PUPSTATE
if [ "$ORIGLANG1" != "en" ];then #120217
echo "OUTPUT_CHARSET=UTF-8
export OUTPUT_CHARSET" >> /etc/rc.d/PUPSTATE
fi
fi
. /etc/rc.d/PUPSTATE #variables created at bootup by init script in initrd.
I can't sync with woof right now. Rolling back pupsaveconfig is a safer fix. Isn't the goal of pupsaveconfig to work with older versions of woof? If not, it would be good to put a note in the thread so devs to get the right version for their puplet.

User avatar
shinobar
Posts: 2672
Joined: Thu 28 May 2009, 09:26
Location: Japan
Contact:

Re: rc.sysinit

#2854 Post by shinobar »

jemimah wrote:Isn't the goal of pupsaveconfig to work with older versions of woof?
Yes, pupsaveconfig works with old wooof but also with the old woof bug.

If the finding of the moving 'rf -f /tmp*' from shutdown to the init is real solution, we are better to move. (but i am not quite sure what is the real cause.)
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#2855 Post by jemimah »

That one change is fine but I'm likely to introduce a lot of new problems by only partially syncing. I'm not convinced the rm -rf thing is the issue though. Having it in rc.shutdown worked fine in the past and should continue to work.

If I could reproduce the issue I could probably debug it.

Post Reply