Saluki

A home for all kinds of Puppy related projects
Message
Author
User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#2866 Post by greengeek »

I would also like to mention another problem I am having with Saluki, as it might remotely be related to these shutdown issues (but probably not). Again, I have this problem with Saluki, but not with NOP 5.2.2 which is based on the same racy.

DISCLAIMER: this will sound a bit spooky-tunes. You will think I am going mad. Maybe I am. Anyway, here is my problem:

When I try to boot from the usb stick I have loaded Saluki onto (regardless of whether I selected "save to file" or "save to partition") the system will not boot on the first attempt. It will hang forever showing:

SYSLINUX 4.05 EDD 0x4f131b2f Copyright (C) 1994-2011 H Peter Anvin et al.

If I force a poweroff by holding the power button for 10 seconds, then power on again within 20 seconds, Saluki will boot up correctly. If I leave it longer than 20 seconds, the next power on will go back to the SYSLINUX prompt and hang there forever. (actually - it is not a prompt, it is just like the machine stopped in mid sentence)

I also notice that if I remove and reinsert the usb stick during the initial 20 seconds after a poweroff, it will not reboot - just goes to SYSLINUX message again. This suggests to me that perhaps my machine maintains some portion of usb power for approx 20 seconds after poweroff? And that this affects whether or not Saluki boots correctly.

Or maybe the netbook power management system has something that still exists in memory or BIOS for 20 seconds after a power off? I just don't know. Anyway, it is repeatable and happens every time, and I have tried reinstalling about 10 times on two (identical) usb sticks, and now a third, different, higher quality stick, without being able to get rid of the problem. NOP 5.2.2 does not show this behaviour.
Last edited by greengeek on Sun 29 Apr 2012, 02:17, edited 2 times in total.

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

#2867 Post by Karl Godt »

greengeek wrote:Just in case it helps to narrow down the problem I thought I would mention the following:

If I install Gray's Racy 5.2.2 NOP in the same way as I have been installing Saluki, I do not have any shutdown problems at all.

NOP 5.2.2 seems to use a different routine for specifying the locale - I can choose en_Aus on the first stage - it does not require me to go to a second screen to select en-Aus, Also, it does not offer the "Legacy" prompt ro do the install to partition. I have now tried both the "save to file" and "save to partition" with NOP 5.2.2 and they both work fine.
Just to be precise : I think you refer to en_AU because you are located in NZ (en_NZ) OR en_US ?

Could you please post the output of the

Code: Select all

locale

Code: Select all

locale -a

Code: Select all

locale -m
commands ?

Brown Mouse
Posts: 564
Joined: Tue 09 Jun 2009, 21:06

#2868 Post by Brown Mouse »

greengeek wrote:
When I try to boot from the usb stick I have loaded Saluki onto (regardless of whether I selected "save to file" or "save to partition") the system will not boot on the first attempt. It will hang forever showing:

SYSLINUX 4.05 EDD 0x4f131b2f Copyright (C) 1994-2011 H Peter Anvin et al.
I see the same thing when booting Lucid 528-05 from an sdhc on my Acer Aspire one netbook.

User avatar
Geoffrey
Posts: 2355
Joined: Sun 30 May 2010, 08:42
Location: Queensland

#2869 Post by Geoffrey »

Karl Godt wrote:(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, I've had that problem with a usb install also, if a file is deleted in /mnt/home then it creates /mnt/home/.Trash-0 which can not be emptied if there isn't sufficient free space,
this results in having to reformat the drive, I now don't delete files in /mnt/home :roll:
It might be an idea to be able to select a percentage of free space for the trash like that other OS.

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

#2870 Post by Karl Godt »

Geoffrey wrote:
Karl Godt wrote:(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, I've had that problem with a usb install also, if a file is deleted in /mnt/home then it creates /mnt/home/.Trash-0 which can not be emptied if there isn't sufficient free space,
this results in having to reformat the drive, I now don't delete files in /mnt/home :roll:
It might be an idea to be able to select a percentage of free space for the trash like that other OS.
I finally opened a terminal in these trash directories and did a

Code: Select all

rm *
rm .*
cd ..
rmdir *
rmdir .*
to solve this manually

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#2871 Post by greengeek »

Karl Godt wrote: Could you please post the output of the

Code: Select all

locale

Code: Select all

locale -a

Code: Select all

locale -m
commands ?
Hi Karl, I have now edited my previous posts to clarify that I was selecting Australian English (ok I am in NZ but I figured that Puppy is an Aussie creation so was hoping I would have less problems by selecting their locale... :-) )

I have attached pics of the locale outputs (sorry I don't know how to save data from a terminal yet..
Attachments
locale_.jpg
(29.9 KiB) Downloaded 1344 times
locale _a_.jpg
(7.21 KiB) Downloaded 1280 times
locale _m_.jpg
(25.66 KiB) Downloaded 1245 times

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

#2872 Post by Karl Godt »

Yep, greengeek looks pretty OK i think ...

I have absolutely no idea about the different en_EN differences, just had heard there are different scottish dialects in australia ..

and that the neccessary and necessary programms programs ..

If you are running on USB with save to entire partition, could you post the output of the

Code: Select all

mount
command ?

(you could use the mouse left clicking holding the button and move the cursor over the output of the console, release the left button, and middle click to paste it into an empty sheet of an editor and do the same to copy from editor to the inputbox of the browser)

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#2873 Post by greengeek »

jemimah wrote:Is it fixed in 21?
Version 21 gives me a slightly different result. It does not reboot into X, but just reverts to a command prompt after the saving process. However, I still have to do a hard shutdown to get out of this state.

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#2874 Post by greengeek »

Karl Godt wrote:If you are running on USB with save to entire partition, could you post the output of the

Code: Select all

mount
command ?
OK, I have taken a shot of the mount command in the "fresh boot" state (first boot after hard reset) and also the "loop boot" state (when the shutdown procedure has auto rebooted in error).
(Sorry I couldn't do the middleclick trick till I get a mouse attached)
Attachments
mount fresh boot_.jpg
(54.08 KiB) Downloaded 1272 times
mount loop boot_.jpg
(44.13 KiB) Downloaded 1176 times

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

debugging tool

#2875 Post by shinobar »

greengeek wrote:Version 21 gives me a slightly different result. It does not reboot into X, but just reverts to a command prompt after the saving process. However, I still have to do a hard shutdown to get out of this state.
Yeah, I could reproduce your problem under the locale 'en_US' (left as the default). I think the locale does not affect.
I think your problem is the saving to the partition specific. Or, saving to the partition on the flash, that is PUPMODE=7. Maybe recent woof bug.
I suspect the shutdown problem occurs every PUPMODE, but with different appearance.

Attached the rc.shutdown for debugging for whom the shutdown problem concern. Install the PET. You are warned because it will replace the existing /etc/rc.d/rc.shutdown, but proceed. Shutdown or reboot. The console gives prompt with '?'. Press [Enter]-key to proceed.
As for the PUPMODE=7, greengeek's case,press [S]-key at only one place where you are offered to skip.
at shutdown wrote:Sakuji is now shutting down...
Saving ... ... Done.
Cleaning up some temporary files. OK?
Cleaning up some temporary files... Done.
Unmount stray filesystems?
Unmounting stray filesystems... Done.
Swapoff?
Swapoff... Done.
Kill bad PID's? ('s' for skip) s
Remount SAVE_LAYER?
Remounting SAVE_LAYER ...Done.
Umount ntfs?
All done. Goobye?
Attachments
firstrun-debug-shutdown-2.2.1.pet
For debugging. DO NOT use for usual use.
(19 KiB) Downloaded 327 times
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

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

respawn

#2876 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.
Short exercise:
Go down to the console, type:

Code: Select all

kill -KILL $$
Its killing myself. logging out and auto login.

Code: Select all

rm -fr /tmp/*
kill -KILL $$
Coming back the desktop because the flag '/tmp/bootcnt.txt' was cleared.
Reasonable.

Test with the debugging tool:
Well, I reproduced the greengeek's case (USB flash install, save the session to the partition). Used the firstrun-debug-shutdown, and foud that the rc.shutdown kills its parent 'reboot'(or 'poweroff') and itself at the last stage. I don't know why, but maybe woof bug. It occurs PUPMODE=7 on saluki-21 but maybe all recent Puppies. I don't know about PUPMODE=6 (save the session in the internal HDD partition). I am not sure if it is related with PUPMODE=2 (Sage's case).
I also suspect that similar case can occur under PUPMODE=5 and/or under other cases, somewhere in the script rc.shutdown.

As for the position of deleting /tmp/*, as greengeek reported. it relates coming up the desktop or not when this happens.
Last edited by shinobar on Wed 23 May 2012, 04:16, edited 1 time in total.
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

#2877 Post by Sage »

Anyone interested in comparing a copy of rc.shutdown with rc.shutdown.pupdev ? Who instigated the latter? Is it self-generating? Although I do not follow the above detail concerning code, I did find what works and what does not work, at least for a FULL - seems that it must contain the audit trail for the coding fault?

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

rc.shutdown.pupdev

#2878 Post by shinobar »

Sage wrote:Anyone interested in comparing a copy of rc.shutdown with rc.shutdown.pupdev ? Who instigated the latter?
The rc.shutdown.pupdev is a document text. It does nothing as a script. Nothing do results hard-shutdown in some meaning.
I am very interesting if you report the result of the firstrun-debug-shutdown-2.2.1.pet. We can see, by the test, where it fails.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]

User avatar
shelezyaka
Posts: 52
Joined: Tue 14 Feb 2012, 13:57
Location: Ukrainian

#2879 Post by shelezyaka »

Karl Godt wrote:
Geoffrey wrote:
Karl Godt wrote:(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, I've had that problem with a usb install also, if a file is deleted in /mnt/home then it creates /mnt/home/.Trash-0 which can not be emptied if there isn't sufficient free space,
this results in having to reformat the drive, I now don't delete files in /mnt/home :roll:
It might be an idea to be able to select a percentage of free space for the trash like that other OS.
I finally opened a terminal in these trash directories and did a

Code: Select all

rm *
rm .*
cd ..
rmdir *
rmdir .*
to solve this manually
In order not to clutter up the trash "rubbish", use the delete missing trash. The right mouse button (in the paragraph the cursor is positioned). Recover deleted in this case is impossible.
Attachments
SCR1.png
(60.19 KiB) Downloaded 623 times

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

#2880 Post by Sage »

The rc.shutdown.pupdev is a document text. It does nothing as a script. Nothing do results hard-shutdown in some meaning.
I am very interesting if you report the result of the firstrun-debug-shutdown-2.2.1.pet. We can see, by the test, where it fails.
As I explained, I don't do coding. I swapped rc.shutdown for rc.shutdown.pupdev and the shutdown failure/desktop looping stopped. If you tell me where to find firstrun-debug-shutdown-2.2.1.pet I will look for it, but presume I would have to invert the swap because shutdown works with the -.-.pupdev.

Yes, I double checked. It may be just a text file but swapping rc.shutdown with ditto.pupdev and back again reproducibly causes and rectifies the shutdown problem. No idea why, but it does. You're the expert, shino....

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

#2881 Post by Karl Godt »

First impression is that the difference is one mount less in the "return to X-Desktop" mount output .

This could indicate, that the part to unmount stray partitions once did run, and detecting a zombie process killed the parent of the zombie ...

So this might occur randomly, with one Puppy 511 and one racy-5.x i have jwm zombies .. probably by the jwm -restart|-reload command(s) that killing would normally not affect X, pup_event_frontend_d, delayedrun, xinitrc and that likes anymore because they should have been killed already by /usr/bin/wmreboot||/usr/bin/wmpoweroff ...

since the removal of /tmp directory occurs just before umount ing the stray partitions ..

and yes, i have confused Pupmode 6 and 7 ..

it might be, that somehow gettext or eval_gettext could have left a zombie process, maybe because of a typo ..

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#2882 Post by mavrothal »

It would appear that retrovol-saluki is broken in 020+. Specifically the icon does not show in the tray, though it works fine (eg responds to right-click etc).
Maybe related to the recent icon dir changes?
Any symlink that could solve this?
BTW where is the source? Barry's source for 0.10 and 0.12 does not compile (without "magic") in 021.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

User avatar
Marv
Posts: 1264
Joined: Wed 04 May 2005, 13:47
Location: SW Wisconsin

Retrovol

#2883 Post by Marv »

It would appear that retrovol-saluki is broken in 020+. Specifically the icon does not show in the tray, though it works fine (eg responds to right-click etc).
Maybe related to the recent icon dir changes?
Any symlink that could solve this?
I had the same problem starting roughly around 020. Removing the Saluki Retrovol and installing retrovol-Lucid-0.5 ( I believe from the repository) got me back the icon and all works fine.
Pups currently in kennel :D Older LxPupSc and X-slacko-4.4 for my users; LxPupSc, LxPupSc64 and upupEF for me. All good pups indeed, and all running savefiles for look'n'feel only. Browsers, etc. solely from SFS.

jakfish
Posts: 762
Joined: Fri 18 Jul 2008, 19:09

#2884 Post by jakfish »

I'm trying out luki 021 on a Lenovo S10-3t netbook/tablet.

Looks like a great success (incredibly fast shut down, for starters), but before I get to all the good things, I'm having trouble with xorg.conf and the Lenovo touch screen.

I have a working xorg in dpup exprimo which allows initial calibration and touch screen driver setup (which is needed before using calibration tool):

Section "ServerLayout"
InputDevice "Synaptics Mouse" "AlwaysCore" #serverlayoutsynaptics
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "touchscreen" "SendCoreEvents"
EndSection

Section "InputDevice"
Identifier "touchscreen"
Driver "evtouch"
Option "Device" "/dev/input/event10"
Option "DeviceName" "touchscreen"
Option "MinX" "80"
Option "MinY" "80"
Option "MaxX" "4095"
Option "MaxY" "4095"
Option "ReportingMode" "Raw"
#Option "MaxTapTime" "220"
#Option "MaxTapMove" "220"
#Option "moving_action" "down"
#Option "moving_button" "1"
#Option "maybetapped_action" "click"
#Option "maybetapped_button" "3"
# Option "longtouched_action" "click"
# Option "longtouched_button" "3"
# Option "touched_action" "click"
# Option "touched_button" "1"
Option "Emulate3Buttons"
Option "Emulate3Timeout" "50"
Option "SendCoreEvents" "On"
EndSection

I've put the above in xorg.conf and I don't believe xorg is reading it upon reboot or X restart.

I do the modprobe hid-multitouch, modprobe evdev in rc.local, and while those commands give me a touchscreen, I'm unable to get calibration or any other of the touch commands that an edited xorg should give me.

Jake

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

#2885 Post by jemimah »

Karl Godt wrote:First impression is that the difference is one mount less in the "return to X-Desktop" mount output .

This could indicate, that the part to unmount stray partitions once did run, and detecting a zombie process killed the parent of the zombie ...

So this might occur randomly, with one Puppy 511 and one racy-5.x i have jwm zombies .. probably by the jwm -restart|-reload command(s) that killing would normally not affect X, pup_event_frontend_d, delayedrun, xinitrc and that likes anymore because they should have been killed already by /usr/bin/wmreboot||/usr/bin/wmpoweroff ...

since the removal of /tmp directory occurs just before umount ing the stray partitions ..

and yes, i have confused Pupmode 6 and 7 ..

it might be, that somehow gettext or eval_gettext could have left a zombie process, maybe because of a typo ..
This is good detective work.

The question is, why are we getting these reports now. It must be something that changed recently or it could be a coincidence I guess.

Here is the relevant section of the diff:

Code: Select all

 killzombies() {
  #ZOMBIES="`ps -H -A | grep '<defunct>' | sed -e 's/  /|/g' | grep -v '|||' | cut -f 1 -d ' ' | tr '\n' ' '`"
- ZOMBIES="`ps -H -A | grep '<defunct>' | sed 's/^[[:blank:]]*//g' | grep -v '|||' | cut -f 1 -d ' ' | tr '\n' ' '`" #120103 karl godt: because i was getting a bunch of "killall no such process must be either pid or name" on the screen by the killzombies function.
+ #ZOMBIES="`ps -H -A | grep '<defunct>' | sed 's/^[[:blank:]]*//g' | grep -v '|||' | cut -f 1 -d ' ' | tr '\n' ' '`" #120103 karl godt: because i was getting a bunch of "killall no such process must be either pid or name" on the screen by the killzombies function.
+ ZOMBIES="`ps -H -A | grep '<defunct>' | sed 's/^[[:blank:]]*//g' | cut -f 1 -d ' ' | sort -gr | tr '\n' ' '`" #120129 karl godt: improved, see http://www.murga-linux.com/puppy/viewtopic.php?t=73122
  for ONEZOMBIE in $ZOMBIES
  do
   echo "Killing parentless zombie process $ONEZOMBIE"
   kill $ONEZOMBIE
  done
 }
Should I roll the zombie killing code back?

Post Reply