X-Slacko-4.4 with Xfce

[rg66]

X-slacko-2.2.1 PAE delta removed

[rg66]

X-slacko-2.2.1n Non-PAE delta removed

[Marv]

X-slacko-2.2.1n Non-PAE delta is available for download. The puppy SFS has been changed to puppy_xslacko_2.2.1n to differentiate between the two versions. I'm hoping it won't cause problems, so far it seems to work ok.

non-PAE delta downloaded and applied to 2.2 non-PAE iso.
Resulting iso checks ok and installed frugally with and without my 2.2 savefile. No problems with the 'n'. Also installed with my 3.14.20 kernel and initrd swap (from LxPupTahr.. have to swap the initrd also to get boot..). Of course had to modify the DISTRO_SPECS in that initrd and THAT initrd did balk at the 'n'. Played about a bit to see if it was a string length limitation-it wasn't- and just dropped the 'n' in that installation for now. Thereafter smooth sailing. Using and posting from the stock kernel version now on the old Pentium M laptop. Open to suggestions as to any specific tests.

note: The busybox ACPI mods I use in the 3.14.20 kerneled 2.2 also work correctly with the stock kernel on this laptop.

[rg66]

@ Marv

Not sure if you remembered to edit init in initrd.gz for 3.14.20 to deal with the 'n'. See this post: http://www.murga-linux.com/puppy/viewto ... 456#802456. Maybe the 'n' wasn't such a good idea.

As far as testing, just want to make sure save to folder is working ok.

[rg66]

I've been using pack-tools to build the puppy_xslacko sfs and have been getting a lot of corrupted ones. I've edited pack-tools and it seems to be fixed. Download the pet and install or dump the script below in /usr/bin and make sure it's executable (remove fake .gz). Alternatively, you can just add the code below underneath #! /bin/bash in /usr/bin/pac-tools.

Code: Select all

sync 
echo 3 > /proc/sys/vm/drop_caches

[rg66]

Script for converting savefile to savefolder.

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

[Marv]

@ Marv

Not sure if you remembered to edit init in initrd.gz for 3.14.20 to deal with the 'n'. See this post: http://www.murga-linux.com/puppy/viewto ... 456#802456. Maybe the 'n' wasn't such a good idea.

As far as testing, just want to make sure save to folder is working ok.

Indeed I did...forget to edit the line in init, adding [a-z]. Done and working with 'n'. I think the 'n' is a good idea. Working on multiple pups, anything that helps one remember which is which is good. I'll do a pristine in my experimental and play with converting/installing to a folder.

Edit:
Stock kernel: Set up a directory /Experimental in my ext2 partition (my bootable Experimental is on a Grub4Dos fat32 boot partition so can't use that). Copied my X-slacko-2.2.1n savefile to the directory on the ext2 partition, converted it to a folder per your post above and rebooted. Tested both with a freshly created savefolder and with my converted savefolder. Works perfectly with the fresh folder. Saving either with snapmergepuppy or on reboot. With my converted folder, finds it as converted and uses it BUT will not update it either using snapmergepuppy or on shutdown. Message on shutdown is roughly "Saving session to folder /Experimental/xslackosave-2.2.1n : failed. On a re-reboot, it reads any changes made with the setup below absolutely correctly. I will check my savefolder for any snapmergepuppys/shutdown.rcs etc that are the problem.

3.14.20 kernel: Exactly as above but using initrd.gz from TahrPup 6.0CE as it has the savefolder mods in it and will boot to the 3.14.20 kernel. That initrd.gz modified (DISTRO_SPECS and the [a-z] patch in init per your post above). NO other changes other than the vmlinuz, and zdrv from 3.14.20. Boots, finds and uses and updates my savefolder in the ext2 drive partition ok, either with Save2flash or on shutdown (reporting Saving session to folder /Experimental/xslackosave-2.1n : done). Also boots, saves, and reboots perfectly using the fresh savefile created above.

In summary, works perfectly. The stock kernel setup doesn't like something with my converted savefile. Won't be the first time. The puzzle is that the converted savefile works with the alternate kernel/initrd.ga/vmlinuz/zdrv. Only relevant to me I suspect.

Edited above to reflect further testing

[rg66]

I've had no probs with a savefolder but I've not converted a savefile yet. I'll have a look tomorrow, it's late and I really need sleep.

[Marv]

All clear on this front now. Cleaned savefile of previous versions of snapmergepuppy, rc.shutdown etc and reconverted. Works fine on both kernel versions. I just have to disable the clunky Save dialog at shutdown for my folks now......The rc.shutdown in the pet here http://www.murga-linux.com/puppy/viewto ... 551#806582 seems to do it for me.

[rg66]

...The rc.shutdown in the pet here http://www.murga-linux.com/puppy/viewto ... 551#806582 seems to do it for me.

Strange, that should be the original rc.shutdown without save folder added.

[Marv]

...The rc.shutdown in the pet here http://www.murga-linux.com/puppy/viewto ... 551#806582 seems to do it for me.

Strange, that should be the original rc.shutdown without save folder added.

I don't run savefolders yet on the machines I farm out so that reversion worked for them and was a quick fix.. Do you have an elegant way to turn off the shutdown dialog on the new rc.shutdown? I took a quick look and there may be an env parameter that can be exported but doing other things first.

[rg66]

I don't run savefolders yet on the machines I farm out so that reversion worked for them and was a quick fix.. Do you have an elegant way to turn off the shutdown dialog on the new rc.shutdown? I took a quick look and there may be an env parameter that can be exported but doing other things first.

Ah, ok. "Turn off the shutdown dialog" as in running in RAM and don't want to be asked to save?

[Marv]

I don't run savefolders yet on the machines I farm out so that reversion worked for them and was a quick fix.. Do you have an elegant way to turn off the shutdown dialog on the new rc.shutdown? I took a quick look and there may be an env parameter that can be exported but doing other things first.

Ah, ok. "Turn off the shutdown dialog" as in running in RAM and don't want to be asked to save?

No, in this instance I always want to save with no dialog. Placing the attached file in /etc exports the ASKTOSAVE parameter with a value of 'false' and does the trick. Just was wondering if there was a GUI to do that I missed.

[rg66]

No, in this instance I always want to save with no dialog. Placing the attached file in /etc exports the ASKTOSAVE parameter with a value of 'false' and does the trick. Just was wondering if there was a GUI to do that I missed.

Maybe, how are you running? USB, frugal etc...... I'm running on HD frugal and never get a dialog to save.

If your running 2.2.1 USB frugal then it sounds like your getting the save at shutdown dialog from Control panel > System > Puppy Event Manager > Save Session tab. It should only do this when set to 0 (it says never but still asks at shutdown), default should be 30.

2.2 uses pupsaveconfig which is similar but has never and ask at shutdown, both work but pupsaveconfig doesn't work with save to folder.

[Marv]

No, in this instance I always want to save with no dialog. Placing the attached file in /etc exports the ASKTOSAVE parameter with a value of 'false' and does the trick. Just was wondering if there was a GUI to do that I missed.

Maybe, how are you running? USB, frugal etc...... I'm running on HD frugal and never get a dialog to save.

If your running 2.2.1 USB frugal then it sounds like your getting the save at shutdown dialog from Control panel > System > Puppy Event Manager > Save Session tab. It should only do this when set to 0 (it says never but still asks at shutdown), default should be 30.

2.2 uses pupsaveconfig which is similar but has never and ask at shutdown, both work but pupsaveconfig doesn't work with save to folder.

Running frugal from CFcard in ide adapter, pmedia=ATAFLASH. Gives PUPMODE=13. Puppy Event Manager Save Session tab always set at 30, the default. 2.2 or 2.2.1n reverted to the 2.2 rc.shutdown do indeed shut down without dialog. A fresh frugal install of 2.2.1n with parameters as above gives the dialog at shutdown unless I export ASKTOSAVE='false'. Then it behaves exactly as 2.2 on shutdown. I haven't seen it saving at 30 mins yet but that's a random catch. No real problem with the export, just wondered if it was integrated anywhere yet.

[rg66]

More weirdness, check /etc/eventmanager, line 6, RAMSAVEINTERVAL=??? Maybe it's not getting written there. Or try gyro's ydrive for slacko-5.7 http://www.murga-linux.com/puppy/viewto ... 368#809368, maybe I missed something.

[starhawk]

Hey, just got a new laptop -- friend on my other forum out-and-out gave me a Dell E4310 (I'm one lucky sumbitch lol) -- the only thing is, the volume buttons (up/down/mute) don't work. Is there a driver for that somewhere...?

[Marv]

More weirdness, check /etc/eventmanager, line 6, RAMSAVEINTERVAL=??? Maybe it's not getting written there. Or try gyro's ydrive for slacko-5.7 http://www.murga-linux.com/puppy/viewto ... 368#809368, maybe I missed something.

No change in behavior with that ydrive in place.

RAMSAVEINTERVAL in /etc/eventmanager is being written correctly by puppy event manager, just not being used in the new rc.shutdown. I added the following code at line 100 (after . /etc/eventmanager # 140417, SFR ) and things now work exactly as expected. ie setting the save interval to 0 results in a save dialog on shutdown and any other value shuts down and saves with no dialog. I think this just wasn't implemented in the new rc.shutdown. Oh, I did catch a save at 30 minutes so that is working normally.

Edit: ' ' not necessary around true,false. Could also do it in one line but left expanded for clarity.

Code: Select all

if [ $RAMSAVEINTERVAL = 0 ] ; then  #141118, Marv
  ASKTOSAVE=true
else
  ASKTOSAVE=false
fi

[rg66]

Hey, just got a new laptop -- friend on my other forum out-and-out gave me a Dell E4310 (I'm one lucky sumbitch lol) -- the only thing is, the volume buttons (up/down/mute) don't work. Is there a driver for that somewhere...?

After searching the ppm and google, I can't find any pkg for fn keys. They should be controlled by acpi, do other fn keys work such as lcd brightness?

[starhawk]

Yes, those work. These aren't Fn keys tho. Three buttons, separate from the keyboard, on the right side of the chassis over the DVD drive. Electronically speaking, they're on a daughtercard that has a little teeny FFC cable going to it. The hardware WiFi switch is on the same card, although I haven't tested it yet.

Here, have a photo (found on google, re-upped elsewhere) --