Saluki

[greengeek]

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.

Thanks Shinobar. After installing the pet, my machine goes through the steps you listed:

Cleaning up some temprary files. OK?
Cleaning up some temprary files... Done.
Unmount stray filesystems?
Unmounting stray filesystems... Done.
Swapoff?
Swapoff... Done.
Kill bad PID's? ('s' for skip) .(I entered "s")
Remount SAVE_LAYER?
Remounting SAVE_LAYER ...Done.
Umount ntfs?
All done. Goobye?

Then the machine did shut off successfully, and did not reboot automatically. (Excellent!). Yes it is a slow way to shut down, but it is much quicker than waiting for the faulty shutdown/reboot loop. Also, it is better than having to do the hard reset, which is bad for the hard drive. At least this way I can use Saluki ok until the full fix.

However, the pet did not change the symptom I mentioned here:
http://murga-linux.com/puppy/viewtopic. ... start=2865
(I didnt really think that symptom was related to the faulty shutdown, but I was hopeful that it might be )

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

I've fixed retrovol in the repo.

The updated pet works fine.

However I must be missing something because compiling the source you posted I get

Code: Select all

/usr/lib/gcc/i486-t2-linux-gnu/4.3.4/../../../../i486-t2-linux-gnu/bin/ld: cannot find -lgobject-2.0

although libgobject-2.0.so .la and headers are all in place

[jemimah]

As usual, jemimah, you did it. Replacing evtouch with evdev in xorg.conf does the trick.

The touchscreen does need more calibration, so I've installed the pet xinput_calibrator. Installs fine, but:

xinput_calibrator: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by xinput_calibrator)

I looked through this thread and saw that a Bible program also needed this lib. I haven't yet found it--any place in particular I should look?

Thanks again for the evdev/evtouch help,
Jake

Did you install xinput-calibrator from the saluki repo. I think you got it from somewhere else.

If you get that error there's no fixing it by adding a lib. Updating glibc requires a recompile of the whole system,

If you have any requests for the saluki repo just let me know.

[jemimah]

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.

I've fixed retrovol in the repo.

The updated pet works fine.

However I must be missing something because compiling the source you posted I get

Code: Select all

/usr/lib/gcc/i486-t2-linux-gnu/4.3.4/../../../../i486-t2-linux-gnu/bin/ld: cannot find -lgobject-2.0

although libgobject-2.0.so .la and headers are all in place

I think this might be the result of a failed upgrade or a mismatched devx. Make sure the libgobject.so file is a valid link.

[shelezyaka]

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.

I've fixed retrovol in the repo.

The updated pet works fine.

However I must be missing something because compiling the source you posted I get

Code: Select all

/usr/lib/gcc/i486-t2-linux-gnu/4.3.4/../../../../i486-t2-linux-gnu/bin/ld: cannot find -lgobject-2.0

although libgobject-2.0.so .la and headers are all in place

Try this binary. Put it in /usr/local/bin/ directory and in /root/Startup make a link to it. The controller will appear in the tray.

[jemimah]

After working with the preview all of last week I have Xfce4.10 mostly working now. I need a few more days to work out all the kinks but I should have it ready by the weekend.

[greengeek]

I see the same thing when booting Lucid 528-05 from an sdhc on my Acer Aspire one netbook.

Hi Brown Mouse, I would be very keen to know if you see the same symptom if you did exactly the same install with Saluki, and also with Racy NOP 5.2.2 (which doesn't seem to suffer the same effect)

Any chance you might have the time to trial such a thing? It might be possible that Saluki and Lucid 528.005 share some similar code that Racy NOP does not share. I would be keen to pin down the problem because this sort of thing discourages newcomers on the first attempt.

I will see if I can trial Lucid on my Acer too.

[shinobar]

Updated: pupsaveconfig-2.2.2.pet (2012-04-30)
Download from http://shino.pos.to/linux/puppy/.
# v2.2.2 29apr12: deeper layer subdirectory (zekebaby), remove legacy, rc.shutdown: avoid re-login, VERBOSE message, wmpoweroff and wmreboot: startxface4 (Saluki compatible)
http://www.murga-linux.com/puppy/viewto ... 085#624085

@greengeek, Sage and whom concern the shutdown problem: Try this pet.
The pupsaveconfig-2.2.2 contains improved code to avoid re-login at shutdown.

@jemimah, Karl, and whom interested in the code on the shutdown issue:
The point is not to kill myself nor parent. I suspected the '.fuser -k', and made a function 'killfuser', which checks out the PID. I guess the killzombies has no problem.
http://www.murga-linux.com/puppy/viewto ... 094#624094

@jemimah
You need not insert the code 'alsactrl store' in the rc.shutdown. It is done in the 10alsa and should be there.

[jakfish]

jemimah, yes, when downloading the touchscreen calibrator from luki repo, it installs and runs fine. However, I can't pull off the actual calibration. It never finishes; eventually, I get a "misclick"

So I'm stuck with a rough touchscreen, meaning that I can open or move icons and other large things, but no finger scrolling or other finer work.

Another thing I noticed: the calibration tool did not end up in Menu/System after installation.

Re: XFCE. First time I've used it, and I'm wondering if there's any way to delete icon text under desktop icons. On a small screen, the icons themselves are good enough explanations.

I see the shut-down complaints, but saluki's shut-down on this machine is the fastest I've seen in Linux, go figure.

Frisbee played nice with the wifi.

More as I go along.

Googling tells me that Linux kernels are indeed getting rid of evtouch and replacing it with evdev. Dunno how I feel about that since I'm having far more trouble with touchscreen here than in dpup exprimo.

Best,
Jake

[mavrothal]

Let me first clarify that what's next is not a criticism of any kind but rather an inquiry.
I find Saluki the most visually appealing puppy and the one the with the most "surprise free" repo.

I have noticed that starting around luki 017 the builds are becoming increasingly slower. For a Saluki target, modern machine the differences are almost unnoticed, but I'm mode'ing puppies for a really low specs machine (for the fun of it even if it is not a "target hardware") and there the differences are more than obvious. This is true either with the base only or (more so) with the base and adrive.
Given that from 016 onwards there are mostly "Various fixes and enhancements", and the basic UI and apps are mostly the same, I was wondering why is that.
Is it just because of workarounds on bugs and extra fail-safes? New (not immediately obvious) features? More demanding enhancements? More dependencies? Stale code? Other? Am I just plain wrong?

Obviously I'm not asking for Saluki to role back or start supporting older hardware. I'm just curious (ok... maybe just a tad concerned too ).

[battleshooter]

After working with the preview all of last week I have Xfce4.10 mostly working now. I need a few more days to work out all the kinks but I should have it ready by the weekend.

Totally looking forward to XFCE4

[greengeek]

Updated: pupsaveconfig-2.2.2.pet
@greengeek, Sage and whom concern the shutdown problem: Try this pet.
The pupsaveconfig-2.2.2 contains improved code to avoid re-login at shutdown.

Arigato Shinobar San. That seems to work well. Thank you to all who worked on this.

[jemimah]

@jemimah
You need not insert the code 'alsactrl store' in the rc.shutdown. It is done in the 10alsa and should be there.

Actually I tested without it and the problem remains.

[jemimah]

jemimah, yes, when downloading the touchscreen calibrator from luki repo, it installs and runs fine. However, I can't pull off the actual calibration. It never finishes; eventually, I get a "misclick"

So I'm stuck with a rough touchscreen, meaning that I can open or move icons and other large things, but no finger scrolling or other finer work.

Another thing I noticed: the calibration tool did not end up in Menu/System after installation.

Re: XFCE. First time I've used it, and I'm wondering if there's any way to delete icon text under desktop icons. On a small screen, the icons themselves are good enough explanations.

I see the shut-down complaints, but saluki's shut-down on this machine is the fastest I've seen in Linux, go figure.

Frisbee played nice with the wifi.

More as I go along.

Googling tells me that Linux kernels are indeed getting rid of evtouch and replacing it with evdev. Dunno how I feel about that since I'm having far more trouble with touchscreen here than in dpup exprimo.

Best,
Jake

Maybe try these instructions for tweaking it manually.
http://setupguides.blogspot.com/2010/10 ... -1010.html

[jemimah]

Let me first clarify that what's next is not a criticism of any kind but rather an inquiry.
I find Saluki the most visually appealing puppy and the one the with the most "surprise free" repo.

I have noticed that starting around luki 017 the builds are becoming increasingly slower. For a Saluki target, modern machine the differences are almost unnoticed, but I'm mode'ing puppies for a really low specs machine (for the fun of it even if it is not a "target hardware") and there the differences are more than obvious. This is true either with the base only or (more so) with the base and adrive.
Given that from 016 onwards there are mostly "Various fixes and enhancements", and the basic UI and apps are mostly the same, I was wondering why is that.
Is it just because of workarounds on bugs and extra fail-safes? New (not immediately obvious) features? More demanding enhancements? More dependencies? Stale code? Other? Am I just plain wrong?

Obviously I'm not asking for Saluki to role back or start supporting older hardware. I'm just curious (ok... maybe just a tad concerned too ).

Slow in what way?

I have increased the delayedrun delay a couple of times because startup items were not always loading on my slow test machine. Other than that no major changes recently except the ISO size has increased by a few MB.

[shinobar]

@jemimah
You need not insert the code 'alsactrl store' in the rc.shutdown. It is done in the 10alsa and should be there.

Actually I tested without it and the problem remains.

Was needed until Saluki-19. No need for Saluki-20 and 21.

[jakfish]

That help sheet from ubuntu and touchscreens did lend some assistance, thanks.

You have to install an xinput pet, then jiggle the calibration handle from there.

In my dpup exprimo setup, in xorg, I replicated the same settings in saluki and find the same drop-off in touchscreen accuracy. So this is not a saluki or specific kernel problem.

By the way, is it possible to lose the icon text below desktop icons? XFCE seems to want at least one character of text. And if so, is there any way make the text bubble transparent?

Jake

[jemimah]

I believe the trick for transparent labels is to add something like this to the /root/.gtkrc-2.0

Code: Select all

style “xfdesktop-icon-view

[mavrothal]

Slow in what way?

OK. I did run some comparisons on 015 vs 021 (identical hardware, USB stick, kernel and features)
015 is ~10% faster from cold boot to connected desktop when only the base is running (57" to 63") or 8% with the adrive (85" to 92"). Apps open from a split second to a second slower in 021, screen rotation takes 3-4" more to settle.
These are with the pfix=nocopy to minimize cache writes. Loading to RAM the differences remain but the times become longer.

021 is also using ~5MB more RAM (base only).
Actually the use of RAM looks rather heavy. With the adrive and "nocopy" is about ~220MB immediately after boot (and ~170MB with the base only). The official Fedora-17/Gnome build for this machine needs ~200MB and other recent puppies (Racy, Slacko) 130-140MB.

Anyway, I do not think is anything to sweat about.We are talking about a 500MHz/256MB machine here, so in your low-end 1.5GHz/512RAM machine differences are practically zero.
But as I said I'm just curious (since you are not publishing woof/mods/changes/hacks )

[Karl Godt]

Now I suspect the code 'fuser -k' and the equivalent code. Hopefully i will offer its fix in a couple of days.

Yup , the fuser line looks pretty unuseable :

If i open a terminal inside a mountpoint like /mnt/sda1
and

Code: Select all

/usr/bin/fuser -m /mnt/sda1

i get something like

/mnt/sda1: 18259c 18260c

With busybox fuser it should look like

Code: Select all

busybox fuser -m /mnt/sda1

18259 18260

which is much more suitable for

xFUSER=`fuser -m $ONESTRAYMNT 2>/dev/null`
[ "$xFUSER" != "" ] && fuser -k -m $ONESTRAYMNT 2>/dev/null

could be like

Code: Select all

xFUSER=`busybox fuser -m $ONESTRAYMNT`
[ "$xFUSER" ] && kill -9 $xFUSER

I LIKE BUSYBOX BASTA !

But this is a WOOF thingy (again) ..